Note the following behaviors and restrictions regarding the consistent changing of all S-VOLs to PSUE status when the secondary system is disconnected.
- S-VOLs must be in PAIR or COPY status in order to change to PSUE status. They cannot be in PSUS or SSUS status.
- All connections to the primary system must be disconnected.
S-VOLs cannot be changed to PSUE status if the MinimumPath field is set to a value other than 1 on the primary system (RCU Option dialog box).
- Changing status to PSUE might take up to 10-minutes if there are many pairs.
- All S-VOLs will be changed to PSUE even if all data paths are recovered in the middle of the process.
- If the data paths are disconnected for a short time (less than one minute), S-VOLs might not change to PSUE status because the storage system does not detect the disconnection.
- After a power outage, all S-VOLs registered in CTG 127 will be changed to PSUE status.
- If write I/O is executed when the P-VOL is in PAIR status and the S-VOL is in PSUE status, the secondary system does not accept updates, and the primary system suspends the P-VOL.
- Remote I/O (RIO), which is issued during the change to PSUE status, is accepted by the secondary system.
- When the status of a pair is changing to PSUE:
- It cannot be resynchronized.
- It cannot be created and registered in CTG 127.
However, a pair can be deleted when status is changing to PSUE.
- In a bidirectional configuration, if all data paths for the primary system of the reverse direction pair are disconnected when pair status is changing to PSUE, the disconnection might not be detected.
- If all the data paths for TrueCopy pairs are disconnected, but the paths used for UR pairs are connected, failure suspend does not occur and S-VOLs cannot be changed to PSUE status.
- If you turn off the power of the primary system when S-VOLs are in PAIR status, all the data paths for the primary system will be disconnected and all the S-VOLs registered in CTG 127 will be changed to PSUE status.