Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I suppose that when you lock the data on the primary node and wait until all data is synchronized then you can disconnect the drbd synchronization and make the secondary node primary, compress the data and back it up. Then make the backup node secondary again and connect it with the primary server. Then all changes from the primary are synchronized to the secondary node. But I have never used drbd that way. Best regards, Maurits van de Lande | Van de Lande BV. | Lissenveld 1 | 4941VK | Raamsdonksveer | the Netherlands |T +31 (0) 162 516000 | F +31 (0) 162 521417 | www.vdl-fittings.com<http://www.vdl-fittings.com> | Van: drbd-user-bounces at lists.linbit.com<mailto:drbd-user-bounces at lists.linbit.com> [mailto:drbd-user-bounces at lists.linbit.com] Namens Brian O Mahony Verzonden: vrijdag 17 februari 2012 14:19 Aan: drbd-user at lists.linbit.com<mailto:drbd-user at lists.linbit.com> Onderwerp: [DRBD-user] Documentation download & another DRBD question Hey folks I am quite new to DRBD, and just had two quick questions, if someone could help it would be great. #1 Is there a downloadable version of the documentation. I don't get very much time to read, so was planning on reading it all offline.... #2 One of the scenarios that I was thinking of using DRBD with is as follows. Please let me know if this would theoretically work, and whether it is ugly, or even just plain wrong. I have a server with about 500GB of data on its own filesystem. Currently, nightly, we lock this data, use tar to copy it it another volume, unlock it, then use gzip on the copy to compress, and then copy this to a second server for backup. The reason for the multi-step process, is we want to keep data lock time a minimum. What I was thinking of doing is using DRBD to mirror this volume to the second server. At backup time, on the second system, we stop the process, or stop the packet shipping or likewise, so there will be no updates, lock the data, run tar/gz, unlock, and restart the synchronization. Is this possible. IE can DRBD deal with a system being unavailable for a few hours, store changes (or do checksums etc) and then replay those changes when the second system comes back online? Anyways thanks in advance for the replies Regards B The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120217/24d35a10/attachment.htm>