Hi Ben,  Your procedure is correct. For #1, it is more than likely using clone emulation under the covers and if that is the case and it is not using true symmir BCV's, you could accomplish #1 and #2 in the same step by just terminating the clone relationship between the pairs. But either way, you have the correct thought process down, just make sure in #3 you are unmapping and unmasking the devices to Server1 prior to deletion since it will prevent you if you don't.  For #4, you can leave them with the BCV attribute on the volumes or you could remove the BCV attribute online with a volume config change using the "convert dev" command and flip them back to regular STD's for any reporting you might have:  [IMAGE]
Hello all,   I currently have Server2 running on BCV+TDEV's cloned from RDF1+TDEV's used by Server1. I've been instructed to divest of Server1 and its storage now and to keep Server2 running on its BCV+TDEV's temporarily until it is also divested in the near future, whatever "near" means. I imagine it should be pretty easy:  1) Split (is that the right term?) the clones so they run independently from the source devices 2) Dismantle the cloning relationship between Server1's RDF1+TDEV volumes and Server2's BCV+TDEV volumes 3) Delete Server1's RDF1+TDEV volumes 4) Let Server2's BCV+TDEV volumes function independently as though they were STD's, filling the role of a regular TDEV for Server2   Before I implement this, I want to ask whether anyone can confirm for me that the BCV's will still have all of the cloned data even after I end the cloning relationship and delete their source devices, the RDF1+TDEV's. I'm afraid that when I break the replication relationship or when I delete the RDF1+TDEV's, the BCV+TDEV's might realize that they're now being used in the role of STD's instead of BCV's and might somehow freak out and dump all of the data that has been copied over to them from the RDF1+TDEV's.   Can anyone tell me that that won't happen? Thanks!
Any problem using a BCV as an STD?