Resolving the problem
Check the cluster resources to make sure that only one scheduler service is active at any given time. Once the active node fails over the scheduler service should automatically be stopped on the active node and started on the failover node.
To troubleshoot, move all the active node cluster resources over to the failover node. Make sure there is only one Tivoli Storage Manager scheduler service running and that the service has successfully stopped on the inactive node. If the service is still running on the inactive node, the Tivoli Storage Manager scheduler service will have to be removed on both cluster nodes using:
dsmcutil remove /name:"TSM Scheduler Service Name"
Once removed, reconfigure the scheduler service properly using the cluster environment configuration guidelines in the v6.4Tivoli Storage Manager Backup-Archive Client User's Guide (Pages 58 - 70) section titled Configuring the backup-archive client in a cluster server environment.
Ensure the following few relevant configurations items are considered:
all cluster scheduler services are named the same scheduler services are being run as an administrator account clusternode is set to yes in the client options file.
If the backup is run via the TSM Scheduler service, make sure it is not running as the Windows "System" account. The System account does not have sufficient authority to access network shares. In the service properties, change the user to an administrator that does have access to the share, and restart the TSM Scheduler service.
Check the cluster resources to make sure that only one scheduler service is active at any given time. Once the active node fails over the scheduler service should automatically be stopped on the active node and started on the failover node.
To troubleshoot, move all the active node cluster resources over to the failover node. Make sure there is only one Tivoli Storage Manager scheduler service running and that the service has successfully stopped on the inactive node. If the service is still running on the inactive node, the Tivoli Storage Manager scheduler service will have to be removed on both cluster nodes using:
dsmcutil remove /name:"TSM Scheduler Service Name"
Once removed, reconfigure the scheduler service properly using the cluster environment configuration guidelines in the v6.4Tivoli Storage Manager Backup-Archive Client User's Guide (Pages 58 - 70) section titled Configuring the backup-archive client in a cluster server environment.
Ensure the following few relevant configurations items are considered:
all cluster scheduler services are named the same scheduler services are being run as an administrator account clusternode is set to yes in the client options file.
If the backup is run via the TSM Scheduler service, make sure it is not running as the Windows "System" account. The System account does not have sufficient authority to access network shares. In the service properties, change the user to an administrator that does have access to the share, and restart the TSM Scheduler service.
