XRECOVER–Recovering data on the recovery system

Use the XRECOVER command to bring data on the XRC recovery system to a consistent, recoverable state in the event of a disaster to the primary system.

The first command at the recovery site must be the XRECOVER command. You will receive a "session not active" message if you issue another XRC command before an XSTART or XRECOVER command has completed.

When you issue the XRECOVER command to each individual XRC session, it determines the common consistency time to which all coupled sessions can be recovered. All appropriate updates are then applied to the target XRC session to reach that consistency time.

Issue the XRECOVER command on the recovery system to complete the updating of all journal data to the secondary (target) volumes. The secondary volume serial numbers of volume pairs in the duplex or seqcheck state are changed to match ("clipped to") the primary volume serial number. The secondary volume serial numbers of suspended volume pairs are also clipped, provided that the pairs have completed initial volume synchronization prior to being suspended. For SESSIONTYPE(XRC), the XRC recovery function must continue to have access to the appropriate journal, control, and state data sets that were in use at the time of the failure, or when the XRC session ended. A migration session requires only the state data set.

If the XRC session has either been suspended or ended normally by a command, the XRECOVER command processing applies the journaled data to update secondary volumes that were suspended while XRC was writing the last consistency group when the XRC session was active. XRC attempts to apply all outstanding data to the secondary volumes so that these volumes are consistent with the rest of the session.

If the suspended volumes can be made consistent, XRC then changes the volume status from SUS to RCV and clips the secondary. If the XRC session has continued to apply consistency groups, then the volume will stay in SUS status. XRC relabels the secondary volumes to the primary volume serial numbers, provided that the volume pair had completed initial volume synchronization prior to the recovery action.

You can also issue the XRECOVER command to recover a group of interlocked coupled sessions to the same consistency time.

In order to provide master session consistency, CXRC applies updates to volumes on the sessions that are behind to allow them to advance to the forward session. CXRC will forward-recover volumes that are suspended because of an error and that have the necessary journal data available. It will not forward-recover volumes that are suspended because of an XSUSPEND command.

Finally, the XRECOVER command automatically generates a recovery report. The report includes the last applied timestamp that defines the recovered, consistent state for all volumes. The XRECOVER command also automatically generates an XQUERY MASTER report for coupled sessions.

Note: Do not issue the XRECOVER command to an active XRC session. If a session is active when you issue the XRECOVER command, XRC rejects the command. You must first issue an XSUSPEND or XEND command for the session, and then make all primary volumes offline to the SDM system. The XRECOVER command that follows the XSUSPEND or XEND command relabels each eligible secondary volume with the primary volume serial number.

For additional information about how to use the XRECOVER command, refer to Extended remote copy data recovery operations.

For additional information about how to use the XRECOVER command in a coupled environment, refer to Example: recovering from a disaster using the XRECOVER command.