Hi list,
i've successfully implemented a three-node setup with an offsite node via drbd
stacked-device as explained in the users-guide
( http://www.drbd.org/users-guide/s-pacemaker-stacked-resources.html )
the offsite drbd-device status is always 'secondary' because it has to stay in
sync with the 'primary' (stacked) device managed by pacemaker crm.
afaik 'secondary' devices cannot be mounted/accessed.
so, how can i access the offsite data, assumed all nodes in my ha-cluster
failed?
how to handle the different states, the offsite-device can be in and how to do
a recovery from it?
i can think these:
- cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown
- cs:WFConnection/Unknown ro:Secondary/Primary ds:Outdated/DUnknown
- cs:WFConnection/Unknown ro:Secondary/Primary ds:Consistent/DUnknown
- cs:WFConnection/Unknown ro:Secondary/Primary ds:Inconsistent/DUnknown
is there a possibility to make the data on the offsite node permanently
available (read only)?
e.g. so i can always 'clone' my production data to my test-environment from
the state:
cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate
Mit freundlichen Grüßen / with kind regards
Torsten Schmidt
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
