Restoring or retrieving data during a failover

When the client fails over to the secondary server, you can restore or retrieve replicated data from the secondary server.

Before you begin

Before you begin to restore or retrieve data during a failover:
  • Ensure that the client is configured for automated client failover.
  • Ensure that you are connected to a Tivoli® Storage Manager V7.1 server that replicates client nodes. For more information about failover requirements, see Requirements for automated client failover.
Restriction: In failover mode, you cannot back up or archive data to the secondary server.

Procedure

To restore or retrieve data during a failover, complete the following steps:

  1. Verify the replication status of the client data on the secondary server. The replication status indicates whether the most recent backup was replicated to the secondary server.
  2. Restore or retrieve your data as you would normally do from the client GUI or from the command-line interface.
    Tip: Restartable restore operations function as expected when you are connected to the secondary server. However, restore operations that are interrupted when the primary server goes down cannot be restarted after the client fails over. You must run the whole restore operation again after the client fails over to the secondary server.

Results

If the replicated data on the secondary server is not current, you are prompted to continue or to stop the restore or retrieve operation.

For example, to restore the build.sh directory at the command-line interface, you issue the following command:AIX operating systemsHP-UX operating systemsLinux operating systemsMac OS X operating systemsOracle Solaris operating systems
dsmc res /build.sh
Windows operating systems
dsmc res C:\build.sh
The following output is displayed:
IBM Tivoli Storage Manager
Command Line Backup-Archive Client Interface
  Client Version 7, Release 1, Level 0.0
  Client date/time: 05/21/2013 14:33:54
(c) Copyright by IBM Corporation and other(s) 1990, 2013. All Rights Reserved.

Node Name: KHOYT
ANS2106I Connection to primary TSM server 192.0.2.1 failed

ANS2107I Attempting to connect to secondary server TARGET at 
192.0.2.9 : 1501

Node Name: KHOYT
Session established with server TARGET: Windows
  Server Version 7, Release 1, Level 0.0
  Server date/time: 05/21/2013 14:33:54  Last access: 05/21/2013 14:13:32

  Session established in failover mode to secondary server
ANS2108I Connected to secondary server TARGET.
Restore function invoked.

ANS2120W The last store operation date reported by the server TARGET of 
05/16/2013 22:38:23 does not match the last store operation date of 
05/21/2013 21:32:20 stored by the client. 
Continue (Yes (Y)/No (N)) 
If you respond with N, the following message is displayed:
ANS1074W The operation was stopped by the user.
If you respond with Y, restore processing continues as normal, but the data that you restore might not be the most current.