When you terminate the relationship between the source and the target, there would be no SDDF session.
You stated that SRC-TGT were in Copied state. This means that you have point-in-time copy of the data when last establish(activiate) was run against the SRC-TGT device pair.
Device Group is only a logical entity to manage the device pair to perform the operations.
Once you terminate the relationship, the data would be still there on the BCV device, but since no SDDF session would be present, you can create a relationship with the new source to the present BCV.
To answer you query -- YES. you can associate the BCV to the new device group and use it to for a Clone session once you terminate the relationship
Yes, clone device group is only to manage the session. it does not stop you from reusing your already disassociated BCV again and data is not wiped from source and target when you remove it from the clone device group.
and yes you can associate the bcv to the new source once it is disassociated
Avinash V
91 Posts
1073
0
Posted January 21st, 2013 04:00
When you terminate the relationship between the source and the target, there would be no SDDF session.
You stated that SRC-TGT were in Copied state. This means that you have point-in-time copy of the data when last establish(activiate) was run against the SRC-TGT device pair.
Device Group is only a logical entity to manage the device pair to perform the operations.
Once you terminate the relationship, the data would be still there on the BCV device, but since no SDDF session would be present, you can create a relationship with the new source to the present BCV.
To answer you query -- YES. you can associate the BCV to the new device group and use it to for a Clone session once you terminate the relationship