HP ProLiant DL380G5-WSS 3.7.0 HP StorageWorks HP Scalable NAS File Serving Sof - Page 402
How the configuration files are used, Samba configuration files. You will need to con two files
View all HP ProLiant DL380G5-WSS manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 402 highlights
• Samba configuration files. You will need to configure two files: /etc/samba/ smb.default and smb.conf.. The /etc/samba/ smb.default file is used on servers that are not currently hosting a virtual Samba server and contains Samba configuration parameters that are not specific to a Samba share. smb.conf. is the configuration file for a particular virtual Samba server. • HP Scalable NAS virtual host. The virtual host acts as a virtual Samba server and can be failed over to a backup node if necessary. Clients access the Samba share via the virtual Samba server. • HP Scalable NAS CUSTOM monitor. The monitor periodically checks the availability of the Samba share. • The /opt/hpcfs/methods/smb_meth script. This script defines the behavior of the CUSTOM monitor probe and coordinates failover of the virtual Samba server in the event of a disruption to its host node. How the configuration files are used The Samba smb.conf file determines what is shared and how it is shared. The Samba solution breaks smb.conf into an smb.default file and one or more smb.conf. files. When a client requests share access via a virtual Samba server, the smb.conf file is constructed dynamically from the smb.default and smb.conf. files. If no virtual Samba servers are hosted on a node, the smb_meth script overwrites the smb.conf file with smb.default. If one or more virtual Samba servers are hosted on a node at the time of the client request, the smb_meth script dynamically modifies the smb.conf file to specify the valid virtual Samba server names hosted by the node and to include the appropriate smb.conf. file. Consequently, only the smb.default and smb.conf. files should be modified. The smb.conf file should be managed by the smb_meth script because any changes made directly to the file can be overwritten during a failover. Additionally, changes to the smb.default file will not be reflected on a given node until all of its virtual Samba servers have been failed-off the node (i.e., the smb.conf file is overwritten). All nodes (primary or backup) that could host a virtual Samba server must have identical smb.default and smb.conf. files at all times. This is not automated and must be managed manually by the administrator. 402 Samba configuration