>> I have the following scenario that I am trying to simulate.
>> 
>> I have a volume replicated between clusters A and B, primary on cluster 
A.
>> The volume is attached to and mounted on a VM instance VM1 on cluster 
A.
>> I take a snapshot of VM1.
>> I now imagine that VM1 on cluster A becomes unreachable, so I want to 
>> bring up VM1 on cluster B, and attach to it the replicated volume.
>> I have to make the volume primary on cluster B.
>> As long as the volume is primary on cluster A, I cannot make it primary 
on 
>> cluster B.
>> 
>> I want to force the transition of the volume on cluster B from 
secondary 
>> to primary, without having to perform operations on cluster A.
>> 
>> What is the proper sequence of operations / commands to accomplish 
this?
>As in your expected experiment, you will need to cut the communication 
path 
>between the two sites.

>The easiest way to do so is to run "drbdadm disconnect <resource>" on one 

>of the sites; given your requirements, on cluster B.

This changes the state of the volume on cluster B to "OutDated" and I am 
unable
to change the volume to primary. I seem to still be missing something.

I tried to do --force to make the volume primary, but then I was unable to
import it to (OpenStack) cinder and attach it to an instance, since the id 
was
not recognized.

- Kalman



_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user

Reply via email to