Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
can anyone give me a tip or two about this?
Mit freundlichen Grüßen / with kind regards
Torsten Schmidt
________________________________
Von: drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] Im Auftrag von Schmidt, Torsten
Gesendet: Mittwoch, 21. Oktober 2009 13:13
An: drbd-user at lists.linbit.com
Betreff: [DRBD-user] Questions regarding offsite disaster/recovery (fromstacked drbd device)
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 <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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20091027/a99e3ab3/attachment.htm>