Failover status information

The API provides status information that applications can use to determine the failover status and the status of replicated client data on the secondary server.

The replication status indicates whether the most recent backup was replicated to the secondary server. If the time stamp of the most recent backup operation on the API matches the time stamp of the backup on the secondary server, the replication status is current. If the two time stamps do not match, the replication status is not current and the replicated data might be out-of-date.

The following replication status information is returned on the query filespace response on the dsmGetNextQObj function call in the qryRespFSData structure:

Table 1. Replication status information reported by the API
Status information	Type	Definition
Start of last replication	lastReplStartDate	The last time replication was started.
End of last replication	lastReplCmpltDate	The last time replication was completed, even if there was a failure.
Last backup store date (Server)	lastBackOpDateFromServer	The last store time stamp that was saved on the server.
Last backup store date (Local)	lastBackOpDateFromLocal	The last store time stamp that was saved on the client.

The failover status is reported by the bIsFailOverMode field in the dsmInitExOut_t structure.

See API type definitions source files for the structure and type definitions of the API.

The DSM_RC_SIGNON_FAILOVER_MODE return code indicates that the client and API failed over to the secondary server, and is running in failover mode.

Example of signon during a failover

The following sample output is an example of signing on the server during a failover:

signon
Doing signon for node khoyt, owner , with password khoytpass
ANS2106I Connection to primary IBM Spectrum Protect server 123.45.6.78 failed

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

ANS2108I Connected to secondary server TARGET.
Handle on return = 1 

************************************************************
After dsmInitEx:
Server TARGET ver/rel/lev 7/1/0/0
userNameAuthorities      : Owner
Replication Server name  : TARGET		 
Home Server name         : MINE		
Connected to replication server		
************************************************************

Example of query session command

The following sample output is an example of the query session command that shows the secondary (replication) server information:

query session
dsmQuerySessInfo Values:
  Server Information:
    Server name   : TARGET
    Server Host   : 123.45.6.79
    Server port   : 1500
    Server date   : 2013/5/21  14:13:32
    Server type   : Windows
    Server version: 7.1.0.0
    Server Archive Retention Protection : NO
  Replication Server Infomation	
    Home Server name        : MINE
    Replication Server name : TARGET
       Host                 : 123.45.6.79					
       Port                 : 1501					
    Fail over status        : Connected to replication server	
  Client Information:     
    Client node type          : Unix     
    Client filespace delimiter: /     
    Client hl & ll delimiter  : /     
    Client compression        : Client determined (3u)     
    Client archive delete     : Client can delete archived objects     
    Client backup delete      : Client CANNOT delete backup objects     
    Maximum objects in multiple object transactions: 4096     
    Lan free Enabled          : NO     
    Deduplication             : Server Only   
  General session info:     
    Node           : KHOYT     
    Access Node    :      
    Owner          :      
    API Config file:    
  Policy Information:     
    Domain name                   : STANDARD     
    Policyset name                : STANDARD     
    Policy activation date        : 0/0/0  0:0:0     
    Default management class      : STANDARD     
    Backup retention grace period : 30 days     
    Archive retention grace period: 365 days

Example of query filespace command

The following sample output is an example of the query filespace command that shows the replication status of a file space on the secondary server:

filespace query
Filespace pattern to query:*
Are the above responses correct (y/n/q)? 

Filespace Name  Type            Occupancy  Capacity   Start         End      
--------------- --------------- ---------- ---------- ------------- -------------
/fs             API:Sample             100        300   0/0/0 0:0:0   0/0/0 0:0:0

     Start of last Replication :  2013/5/21 21:3:2					
     End of last Replication   :  2013/5/21 21:3:3			 		
                                  Server                    Local
     Last backup store date    :  2013/5/21 21:18:25        2013/5/21 21:18:25
     Last archive store date   :  0/0/0 0:0:0               0/0/0 0:0:0	
     Last HSM store date       :  0/0/0 0:0:0               0/0/0 0:0:0	
     FSINFO : Sample API FS Info