You should forcibly delete a pair only for the following reasons:
- The local storage system cannot be connected to the remote storage system because of a communication error.
In the case of a communication error, delete the pair forcibly in both the local and remote storage systems.
- The pair cannot be deleted or a timeout error occurs even when no hardware failures occur and the processing load is low.
CAUTION:
The following data is discarded when you forcibly delete a pair:
- Data that has not yet been sent to the secondary storage system (differential data) when the pair is deleted forcibly from the primary storage system.
- Data that has not been restored when the pair is deleted forcibly from the secondary storage system.
If a pair is deleted forcibly when the journal contains a pair in the PAIR/COPY status, host I/Os to the pair might time out.
- The volume must be unpaired (Simplex status).
- Confirm the status of the pair to be forcibly deleted by using the raidcom get remote_copy_pair CCI command or the YKQUERY BCM command.
- Delete the pair forcibly by using the raidcom delete remote_copy_pair -forcible CCI command.
- Confirm that the pair is deleted by using the raidcom get remote_copy_pair CCI command or the YKQUERY BCM command.