Example: suspending and resynchronizing a volume pair

The following scenario describes the XRC commands that are used to suspend and resynchronize a volume pair. You might choose to do perform this scenario if a primary volume will receive many overlapping changes in a short time and, to optimize performance, and only want the final results to be copied.

1. Start a session named TUCSON for disaster recovery, using the command:

   XSTART TUCSON SESSIONTYPE(XRC) ERRORLEVEL(SESSION)

   Note: An error on any duplex volume will cause the XRC session and all duplex pairs in the session to be suspended. All volumes must be resynchronized. The state, control, and journal data sets are under a high-level qualifier of SYS1.
2. Add a volume pair to the XRC session, with session-level recovery from the XSTART command.

   XADDPAIR TUCSON VOLUME(PRIM01,SECO01)

   Normal data processing continues.

3. Suspend the volume.

   XSUSPEND TUCSON VOLUME(PRIM01)

   Storage controls that support hardware bitmapping record application updates in their hardware bitmaps. Storage controls that do not support hardware bitmapping record application updates in software bitmaps.

4. Resynchronize the suspended volume.

   XADDPAIR TUCSON VOLUME(PRIM01,SECO01)

   The state, control, and journal data sets are under a high-level qualifier of SYS1.