NOTE: If the package fails during maintenance (for example, the node crashes), the package will not automatically fail over to an adoptive node. It is the responsibility of the user to start the package up on an adoptive node. See the manual Managing ServiceGuard manual available at http://www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard for more details.

This feature is enabled only when the configuration variable, MAINTENANCE_FLAG, is set to "yes" in the Samba toolkit configuration file.

Special Notes

Please consider the following areas when implementing HP CIFS Server in the Serviceguard HA framework.

•Client Applications

HA CIFS Server cannot guarantee that client applications with open files on a CIFS Server share or applications launched from CIFS Server share, will recover from a switchover. In these instances there may be cases where the application will need to be restarted and the files reopened, as a switchover is a logical shutdown and restart of the CIFS Server.

•File Locks

File locks are not preserved during failover, and applications are not advised about any lost file locks.

•Print Jobs

If a failover occurs when a print job is in process, the job may be printed twice or not at all, depending on the job state at the time of the failover.

•Symbolic Links

Symbolic links in the shared directory trees may point to files outside of any shared directory. If symbolic links point to files that are not on shared file systems, after a failover occurs, the symbolic links may point to different files or to no file. Keeping the targets of all shared symbolic links, synchronized with all nodes at all times, could be difficult in this situation.

Alternatives would either be to set wide links to "no", or to be sure that every file or directory pointed to is on a shared file system.

•Security Files and Encrypted Passwords

Authentication is dependent on several entries in different security files. An important security file is the user password file, smbpasswd. If your CIFS Server is configured with encrypted passwords set to "yes", use an smbpasswd file. By default, this file is located in the path /var/opt/samba/private but a different path may be specified via the smb passwd file parameter.

Another important security file is secrets.tdb. Machine account information is among the important contents of this file. Since this file will be updated periodically (as defined in smb.conf by 'machine password timeout', 604800 seconds by default), HP recommends that you locate secrets.tdb on a shared storage. As with the smbpasswd file, discussed above, the location of this file is defined by the smb.conf parameter smb passwd file. For example, smb passwd file = /var/opt/samba/shared_vol_1/private/smbpasswd will result in the file/var/opt/samba/shared_vol_1/private/secrets.tdb .

To summarize, both the machine account file ( secrets.tdb) and the password file (smbpasswd) should be put on shared storage.

136 Using SAMBA Toolkit in a Serviceguard Cluster