Issues when using the ATTIME suspend function

True Copy for Mainframe User Guide for VSP One Block 85

Version
10.5.x
FileSize
2745 KB
Audience
anonymous
Part Number
MK-26VSP1B036-02
ft:lastEdition
2026-06-23
Product
SVOS

The following issues are possible when using the ATTIME suspend function for ShadowImage for Mainframe combined with TrueCopy for Mainframe.

TrueCopy for Mainframe combination and backup consistency

Assign ShadowImage for Mainframe pairs on all secondary volumes of the TrueCopy for Mainframe pairs to be backed up. Note that the ShadowImage for Mainframe pairs that are to be combined with TrueCopy for Mainframe secondary volumes must belong to the same ShadowImage for Mainframe consistency group for each unit that requires backup consistency assurance. If only some of the ShadowImage for Mainframe pairs are combined with the secondary volumes of the TrueCopy for Mainframe pairs in the same ShadowImage for Mainframe consistency group, consistent backups are not possible.

Example where consistency cannot be guaranteed:



Pair state and backup consistency

If you want to combine the primary volume of a TrueCopy for Mainframe pair with a ShadowImage for Mainframe pair, the ShadowImage for Mainframe pair must be in either DUPLEX or PENDING status when you perform the split processing. If you want to combine a secondary volume of a TrueCopy for Mainframe pair with a ShadowImage for Mainframe pair, when you perform split processing, make sure that the TrueCopy for Mainframe pair state is Duplex or SSWS and the ShadowImage for Mainframe pair state is DUPLEX or PENDING. If the pair status is other than these when you perform split processing, you will not be able to perform a consistent backup.

Whether pair operations are possible

If split time is registered in the consistency group of ShadowImage for Mainframe, you cannot create, resynchronize, or split aShadowImage for Mainframe pair. If you want to create, resynchronize, or split a pair, cancel the split time first. Note that even if split time is registered in the consistency group of ShadowImage for Mainframe, you can delete the ShadowImage for Mainframe pairs. If you delete all ShadowImage for Mainframe pairs that belong to the ShadowImage for Mainframe consistency group, the registered split time is canceled.

Write I/O before and after the registered split time

If another write I/O with a timestamp after the registered split time is received during a write I/O operation with a timestamp before the registered split time, the split processing for the ShadowImage for Mainframe pair is initiated. In this case, write I/O with a timestamp before the registered split time might not be written to the secondary volume of ShadowImage for Mainframe. Also, if you split aShadowImage for Mainframe pair during a multi-track write I/O, only a portion of the write I/O might be written to the ShadowImage for Mainframe secondary volume.

If write I/O processing to the primary volume of TrueCopy for Mainframe is stopped before the registered split time is exceeded, write I/Os with a timestamp before the registered split time are written to the secondary volume of ShadowImage for Mainframe. If you want to stop write I/Os with the FREEZE command, terminate the write I/Os that were being processed before the registered split time was exceeded. The wait time specified in the FREEZE command must be less than the host's MIH value. For details about the FREEZE command, see I/O control after failure with CGROUP FREEZE/RUN.

Example of write I/Os not being written with a host timestamp before the registered split time:



The ShadowImage for Mainframe pair is in a state where splitting is not possible

If a ShadowImage for Mainframe pair is in a state where splitting is impossible, split processing cannot be performed even if the registered split time is reached. In this case, you need to cancel the split time, make the ShadowImage for Mainframe pair ready for splitting, and then re-register the split time.

Splitting might not be possible for the following reasons. Use corrective action to make the ShadowImage for Mainframe pair ready for splitting.

  1. The ShadowImage for Mainframe pair is blocked.

    Use the applicable CCI command to restore the volume of the ShadowImage for Mainframe pair.

  2. Soft Fence is configured on a volume of the ShadowImage for Mainframe pair.

    Cancel the Soft Fence setting of the volume of the ShadowImage for Mainframe pair.

  3. The Protect attribute is set on a volume of the ShadowImage for Mainframe pair.

    Use the applicable CCI command to cancel the Protect attribute of the volume of the ShadowImage for Mainframe pair.

  4. A volume of the ShadowImage for Mainframe pair is the migration source volume of Volume Migration, and the Volume Migration processing cannot be interrupted.

    Wait until the Volume Migration migration processing is complete.

  5. Among the pairs that share the primary volume of the ShadowImage for Mainframe pair, there is a pair with the Deleting/TRANS status.

    Wait until the pair deletion of the ShadowImage for Mainframe pair is complete.

  6. Among the pairs that share the primary volume of the ShadowImage for Mainframe pair, there is a pair with the Resync-R/REVRSY status.

    Wait until the resynchronization of the ShadowImage for Mainframe pair is complete.