Switching operations to the secondary site by deleting pairs

True Copy for Mainframe User Guide for VSP One Block 85

Version
10.5.x
File Size
2745 KB
Audience
anonymous
Part Number
MK-26VSP1B036-02
ft:lastEdition
2026-06-23
  1. Check the pair status and fence level of each S-VOL.
  2. Analyze the consistency of the S-VOLs based on pair status and P-VOL fence level setting.
    See Checking S-VOL consistency with the P-VOL.

    For a TCz pair with the fence level set to "never", analyze further to determine whether the S-VOL data consistency is guaranteed. To determine whether the consistency of the S-VOL data is guaranteed, use the sense information that is transferred by host failover software, or compare the contents of the S-VOLs with other files that are confirmed to be consistent (for example, database log files). Restore the S-VOLs using the files that are confirmed to be consistent.

  3. Perform file recovery as needed.
  4. Split all pairs from the secondary storage system (raidcom modify remote_copy_pair or YKSUSPND).
  5. Release all pairs (raidcom delete remote_copy_pair or YKRECVER).
    Note: When the S-VOL is no longer paired, it cannot be distinguished it from a non-TrueCopy for Mainframe volume. Use the appropriate means to change the S-VOL volume labels.

    If necessary, use ICKDSF REFORMAT to change the labels (VOLSERs) of the S-VOLs.

  6. Complete file recovery procedures.
  7. Vary the S-VOLs online.
  8. At the secondary site, start critical host operations with the previous S-VOLs now functioning as the P-VOLs.