On the failover of a cluster resource, smdr daemon terminates
Possible Cause:
Cluster failover scripts sends SIGTERM command to smdr to release the cluster resources.
Action:
SMDR needs time to clear the existing connections and release the cluster volumes. Increase the sleep time in the cluster failover script to facilitate the release of the cluster volume.
Backup fails in a mixed node cluster environment
Explanation:
In a mixed node cluster environment, backup fails when node fail-over and fall-back happens between NetWare and Linux servers.
Possible Cause:
Volume names are in lowercase.
Action:
On backing up data in a mixed node cluster environment, the volume name must be passed in uppercase.
Clustered volumes are not backed up during full server backups
Possible Cause:
The application used does not handle SMS clustered resources, causing clustered volumes to be skipped because the TSA was loaded as cluster-enabled.
Cluster pools are not listed on Linux
Possible Cause:
TSAFS is configured to run in non-cluster mode.
Possible Cause:
SLP configuration is incorrect or SMDR failed to register its services to SLP.
Reconnect to TSAFS fails when a cluster resource migrates to another cluster node in a mixed mode cluster.
Possible Cause:
The backup application may require the same user name and password to be available on all nodes in the cluster. During reconnection the same information used for the first node is reused by the application to connect to the other node as well. At times, the user names or their passwords may be different on the two nodes.
Action:
Connect using a user name and password that is common for all cluster nodes.