Question & Answer
Question
Tivoli® Storage Manager components and products rely on the Tivoli Storage Manager V7.1 backup-archive client or API to back up data to the primary Tivoli Storage Manager server. When the primary server becomes unavailable, which products and components can automatically fail over to the secondary server, and which ones are not capable of failover?
Answer
The following table summarizes the failover capabilities of Tivoli Storage Manager components and products.
Component or product | Automated failover (Yes/No) | More information |
| Tivoli Storage Manager V7.1 scheduler | No | Schedules are not replicated to the secondary server. Therefore, when the schedule command is used, the client does not automatically fail over to the secondary server. Likewise, when the client acceptor (CAD) is used to complete a scheduled task, the client does not fail over. |
| Tivoli Storage Manager V7.1 web client | Yes | None |
| Tivoli Storage Manager V7.1 administrative client command-line interface (dsmadmc) | No | None |
| Tivoli Storage Manager API V7.1 | Yes | The API makes failover status and file space replication status information available to other applications. |
| Tivoli Storage Manager components that use client-to-client communication | Yes | Components and products that use client-to-client communication include products such as Tivoli Storage Manager for Virtual Environments V7.1 and IBM® Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server V7.1. |
| Tivoli Storage Manager for Virtual Environments Data Protection for VMware V7.1 | Yes | As with the backup-archive client, backup operations are not available during failover mode because the secondary server is read-only. Beginning with the V7.1.1 release, the following functions are supported when the ExpireProtect option is used:
Restriction: The Data Protection for VMware GUI and command-line interface do not automatically fail over. You must use the backup-archive client to restore data. To restore file-level data, you might need to remove the node from replication in the following situations:
|
| Tivoli Storage Manager for Space Management V7.1 | No | To recall migrated data from the secondary server, you must manually edit the dsm.sys file to connect directly to the secondary server. The node on the secondary server must also be removed from replication.
You can recall files from the secondary server but cannot migrate files to the secondary server. |
| Tivoli Storage Manager HSM for Windows V7.1 | No | To recall migrated data from the secondary server, you must manually edit the dsm.opt file to connect directly to the secondary server. The node on the secondary server must also be removed from replication.
You can recall files from the secondary server but cannot migrate files to the secondary server. |
| Tivoli Storage Manager for Storage Area Networks V7.1 | No | The storage agent does not attempt to fail over to the secondary server. Instead, the storage agent fails over from the LAN-free path to the LAN path. As part of the attempt to fail over to the LAN path, the client and API will automatically fail over to the secondary server. |
| Tivoli Storage FlashCopy® Manager for UNIX and Linux V4.1 | No | When Tivoli Storage FlashCopy Manager for UNIX and Linux is configured for Tivoli Storage Manager, automated client failover is controlled by Data Protection for VMware or Tivoli Storage Manager for Enterprise Resource Planning. |
| Tivoli Storage FlashCopy Manager for VMware V4.1 | No | When configured for Tivoli Storage Manager, automated client failover is controlled by Data Protection for VMware or Tivoli Storage Manager for Enterprise Resource Planning. |
| Tivoli Storage FlashCopy Manager for Windows V4.1 | Yes | Automated failover occurs only if you use Tivoli Storage FlashCopy Manager with the Tivoli Storage Manager configuration. Automated failover does not apply to the stand-alone configuration because there is no connection to the Tivoli Storage Manager server.
After failover occurs, the ability to recover backup data depends on the replication status of the file space on the secondary server. To determine the status of replicated client data, run the dsmc query filespace -detail command at the client command line. The Replication field in the command output shows whether the file space is current or not current. The last store date in the Server field shows when client data was last backed up to the server. If the last store date in the Server field does not match the last store date in the Client field, the file space on the secondary server is not current. If the replication status of the file space is current, data can be restored. If the replication status is not current, the restored data might be incomplete or unusable, depending on whether the last replication completed successfully before the primary server went down. If the replication status is not current and you must restore data from the secondary server, use the last store date that is shown for the secondary server as the date for a point-in-time restore. Otherwise, wait until the primary server comes back online before your restore any data. |
| Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server V7.1 | Yes | If you back up data to the primary server and automated client failover occurs, the recovery of data depends on the replication status of the file space on the secondary server.
To determine the status of replicated client data, run the dsmc query filespace -detail command at the client command line. The Replication field in the command output shows whether the file space is current or not current. The last store date in the Server field shows when client data was last backed up to the server. If the last store date in the Server field does not match the last store date in the Client field, the file space on the secondary server is not current. If the replication status of the file space is current, data can be restored. If the replication status is not current, the restored data might be incomplete or unusable, depending on whether the last replication completed successfully before the primary server went down. If the replication status is not current and you must restore data from the secondary server, use the last store date that is shown for the secondary server as the date for a point-in-time restore. Otherwise, wait until the primary server comes back online before your restore any data. |
| Tivoli Storage Manager for Databases: Data Protection for Oracle V7.1 | Yes | Automated client failover occurs but the recovery of data depends on replication status of the file space.
To determine the status of replicated client data, run the dsmc query filespace -detail command at the client command line. The Replication field in the command output shows whether the file space is current or not current. The last store date in the Server field shows when client data was last backed up to the server. If the last store date in the Server field does not match the last store date in the Client field, the file space on the secondary server is not current. If the replication status of the file space is current, data can be restored. If the replication status is not current, the restored data might be incomplete or unusable, depending on whether the last replication completed successfully before the primary server went down. If the replication status is not current, do not restore the data from the secondary server because the data might be incomplete or unusable. For best results, wait until the primary server comes back online before you restore any data. |
| Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server V7.1 | Yes | Automated client failover occurs but the recovery of data depends on the replication status of the file space.
To determine the status of replicated client data, run the dsmc query filespace -detail command at the client command line. The Replication field in the command output shows whether the file space is current or not current. The last store date in the Server field shows when client data was last backed up to the server. If the last store date in the Server field does not match the last store date in the Client field, the file space on the secondary server is not current. If the replication status of the file space is current, data can be restored. If the replication status is not current, the restored data might be incomplete or unusable, depending on whether the last replication completed successfully before the primary server went down. If the replication status is not current and you must restore data from the secondary server, use the last store date that is shown for the secondary server as the date for a point-in-time restore. Otherwise, wait until the primary server comes back online before your restore any data. |
| Tivoli Storage Manager for Mail: Data Protection for IBM Domino® V7.1 | Yes | Automated client failover occurs but the recovery of data depends replication status of the file space on the secondary server.
To determine the status of replicated client data, run the dsmc query filespace -detail command at the client command line. The Replication field in the command output shows whether the file space is current or not current. The last store date in the Server field shows when client data was last backed up to the server. If the last store date in the Server field does not match the last store date in the Client field, the file space on the secondary server is not current. If the replication status of the file space is current, data can be restored. If the replication status is not current, the restored data might be incomplete or unusable, depending on whether the last replication completed successfully before the primary server went down. If the replication status is not current and you must restore data from the secondary server, use the last store date that is shown for the secondary server as the date for a point-in-time restore. Otherwise, wait until the primary server comes back online before your restore any data. |
For more information a out automated client failover, see the following topics in the Tivoli Storage Manager Information Center:
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21649484