If you use Data Protection for Exchange with
the Tivoli® Storage
Manager configuration, Data Protection for Exchange can
automatically fail over to the secondary server for
data recovery when there is an outage on the Tivoli Storage
Manager server.
The Tivoli Storage
Manager server
that Data Protection for Exchange connects
to for backup services is called the primary server.
If the primary server is
set up for node replication, the client node data on the primary server can
be replicated to another Tivoli Storage
Manager server,
which is the secondary server.
Depending on your configuration, the following nodes must be set
up for replication on the
primary server:
- Data Protection node
- Backup-archive client node (also called the DSM agent node)
- Remote DSM agent node (for offloaded backups to the primary server)
- DAG node (for backups of databases in
an Exchange Server Database Availability Group (DAG))
During normal operations, connection information for the secondary server is
automatically sent to Data Protection for Exchange from
the primary server.
The secondary server information
is saved to the client options file (dsm.opt).
No manual intervention is required by you to add the information for
the secondary server.
Each time the backup-archive client logs on to the server for backup
services, it attempts to contact the primary server.
If the primary server is
unavailable, the backup-archive client automatically fails over to
the secondary server.
In failover mode, you can restore data that was replicated to the secondary server.
When the primary server is
online again, the backup-archive client automatically fails back to
the primary server the
next time the backup-archive client connects to the server.
You can confirm that
Data Protection for Exchange has
failed over by looking for entries about the
secondary server in
the following log files:
- Tivoli\tsm\TDPExchange\dsierror.log
- Tivoli\tsm\baclient\dsmerror.log
Requirements: To ensure that automated
client failover can occur,
Data Protection for Exchange must
meet the following requirements:
- Data Protection for Exchange must
be at the V7.1 level.
- The primary server, secondary server,
and backup-archive client must be at the V7.1 level.
- The primary and secondary servers must be set up for node replication.
- The following nodes must be configured for replication with the replstate=enabled option
in each node definition on the server:
- Data Protection node
- Backup-archive client node
- Remote DSM agent node for offloaded backups
- DAG node, if applicable
- Before the connection information for the secondary server can
be sent to Data Protection for Exchange,
the following processes must occur:
- You must back up data at least one time to the primary server.
- The following nodes must be replicated at least one time to the secondary server:
- Data Protection node
- DAG node, if applicable
Restriction: The following restrictions apply to
Data Protection for Exchange during
failover:
- Any operation that requires data to be stored on the Tivoli Storage
Manager server,
such as backup operations, are not available. You can use only data
recovery functions, such as restore or query operations.
- Schedules are not replicated to the secondary server.
Therefore, schedules are not run while the primary server is
unavailable.
- If the primary server goes
down before or during node replication, the most recent backup data
is not successfully replicated to the secondary server.
The replication status of the file space is not current. If you attempt
to restore data in failover mode and the replication status is not
current, the recovered data might not be usable. You must wait until
the primary server comes
back online before you can restore the data.
- For more information about the failover capabilities of Tivoli Storage
Manager components,
see http://www.ibm.com/support/docview.wss?uid=swg21649484.
For more information about automated client failover
with the Tivoli Storage
Manager backup-archive
client, see Automated client failover configuration and use.