disassocaite bcv device in replication manager

Shawn
Let me get this right - are you trying to

a) create a clone of the BCV (BCV being the source)
or
b) create a clone to the BCV (BCV being the target) ?


First thing - you say
"but our daily replication manager tasks has the bcv established to the std prod device"

Do you not want to use the BCV any more in RM? Or do you want to continue using the BCV for daily RM operations?

If you dont want to use the BCV any more in RM, first thing is to exclude from RM use in the RM console.
Then, run a symdev show on the BCV device to see if it returns any DG name.

If it does return a DG name,
attempt to use symmir to disassociate the BCV to the STD on the production host for that STD.
If it does not list a DG,
then create a DG on any host and add the STD and BCV in and disassocicate from there.


Let me know how it goes.
James.

Sorry James, never got a email that this post was responded to, and just noticed that someone responded. We did need to use the BCV devices again, I just needed the disassociated so that I could run other cloning activities from the command line. Since they were associated to STD devices, I was unable to activate/establish the session until they were disassociated. What I do now, is just run the following anytime I need to clone from the BCV devices:

symmir -f /var/tmp/rm_bcv_disassociate -sid 1031 cancel -nop

(the rm_bcv_dissasociate file is just a file that contains a list of the STD devices with their associated BCV device.

Glad you got sorted Shawn

Cheers
James