When the P-VOL and S-VOL are physically attached to the same host, take the S-VOL offline before releasing the pair to avoid confusion and possible error when the host is restarted.Deleting Universal Replicator pairs
When you delete a pair, the Universal Replicator relationship between the P-VOL and S-VOL is released. Only the relationship is affected, the data volumes and their data remain.
When the P-VOL and S-VOL are physically attached to the same host, take the S-VOL offline before releasing the pair to avoid confusion and possible error when the host is restarted.
When you delete a UR pair in the 3DC multi-target configuration using delta resync, the UR delta resync pair's S-VOL is also deleted. When you delete a TC pair in the 3DC multi-target configuration using delta resync, the UR delta resync pair is also deleted.
Prerequisites
This operation can be performed from the primary or secondary system.
Pairs should be in PAIR status to ensure data consistency between volumes. However, a pair can be deleted in any status except Suspending or Deleting.
In a delta-resync configuration with GAD, delete UR pairs, delta-resync UR pairs, and GAD pairs in that order.
Procedure
Open the Remote Replication window.
In Command Suite: On the Resources tab, expand the Storage Systems tree, right-click the target storage system, and click Remote Replication.
In Device Manager - Storage Navigator: In the Storage Systems tree, click Replication > Remote Replication.
Select the UR Pairs tab, and then select the pairs to be deleted.
From the Actions menu, click Remote Replication > Delete Pairs.
In the Delete Pairs dialog box, review the pairs in the Selected Pairs table. To remove a pair from the table, select the pair and click Cancel.
For Delete Mode, select Normal for Universal Replicator.
Please note the following:
Forced deletion in the primary system causes data that was not yet sent to the secondary system to be deleted.
Forced deletion in the secondary system causes data that was not yet restored to be deleted.
If pair status has not changed to SMPL five minutes after you forcibly delete the pair, delete it again.
Make sure not to re-create the pair in the first five minutes after forcibly deleting it using the same journals (mirrors), even if pair status is SMPL and journal status is Initial. In this case pair creation might fail, and the pair might be suspended.
A timeout error can occur at the time of a forced deletion if I/O is sent to another pair in the same journal and the pair’s status is PAIR or COPY.
Click Finish.
In the Confirm window, review the settings and enter a task name in the Task Name box.
Click Apply to save your settings to the system.