Hi, yes, these would be the recommended steps. Just step 2) and 3) would be somehow different.
Keep in mind you create (yes, with mdadm) a new block device.. So you can write a new (empty!) file system on it, mount it to /var/lib/BackupPC and start using it. But this would mean you loose you old data. I guess this is no good. So you need to push your data to the new device- so I would recommenend to create the RAID1 with a missing disk (this is possible with mdadm). Then do a block-based copy with "dd" and transfer the whole filesystem to the degraded device. Obviously this should be done with the source file system unmounted and unused....and the target device should have at least the size of the source. "dd" inf 2.5TB will be days faster than rsyncing it. Once done, mount the RAID1 7o /var/lib/BackupPC and start BackupPC (perhaps perform a fscck and resize2fs before). Then you can delete your old data and add the disk/ paretition on the local computer to the RAID1 device. mdadm will start syncing and another day (or 2) later the device is in in sync and you have your data on both places. To configure Am 15.12.2015 um 23:36 schrieb [email protected]: > Hi, > thank you for your suggestion. > At moment I have BackupPC host that use local filesystem as pool (let's say > /backuppc folder). > If I understood, necessary steps are: > 1) add iSCSI client on BackupPC, to be able to use iSCSI target on QNAP > 2) create RAID1 (with mdadm??) with local filesystem AND iSCSI > 3) reconfigure backuppc to use folder on raid1 device > correct? > > Thankyou! > > > >> ----Messaggio originale---- >> Da: [email protected] >> Data: 15/12/2015 20.49 >> A: "[email protected]"<[email protected]>, "General list for > user discussion, questions and support"<[email protected]> >> Ogg: Re: Storage replica >> >> Well, this information would have been helpful before ;) >> >> So in this case instead of trying to add DRBD to the QNAP host I would >> suggest you export an iSCSI target to the BackupPC host. Add iSCSI >> client to your BackupPC server and use the iSCSI target as underlying >> device for local RAID1. Thus, you always have an up-to-date secondary >> device available. Additionally use snapshot functionality of QNAP and >> you even have protection against filesystem failures, >> >> >> Greetings >> >> Christian >> >> Am 15.12.2015 um 18:44 schrieb [email protected]: >>> Hi Stephen, >>> sorry, I forgot to mention that my secondary storage is a QNAP device. >>> Actually there is a way to install BackupPC on it: >>> >>> http://wiki.qnap.com/wiki/How_to_install_the_BackupPC_application >>> >>> Anyway, I would prefer keeping configuration as much standard as possible. >>> My choice is limited to QNAP daemon (NFS, rsyncd, samba). >>> Thankyou! >>> >>> >>> >>>> ----Messaggio originale---- >>>> Da: [email protected] >>>> Data: 15/12/2015 14.41 >>>> A: "[email protected]"<[email protected]>, <backuppc- >>> [email protected]> >>>> Ogg: Re: [BackupPC-users] R: Re: R: Re: Storage replica >>>> >>>> (Unless someone mentioned it and I missed it), I'm surprised no one has > yet >>>> offered the standard reply: stand up a 2nd independent BackupPC server. >>>> >>>> Because it's totally separate, you're free to configure it identically to >>>> the first one or if it's simply for DR, set up a different backup > schedule >>>> (ie, weekly or monthly rather than daily) and retention period -- for >>>> example keeping only the last 2 backups rather than a long backup >>>> history... Easy to adjust to fit your available storage and business > needs. >>>> Slightly more work up front, but easy to perform restores without > depending >>>> on another server. >>>> >>>> Hth. >>>> ~Stephen >>>> >>>> On Mon, 14 Dec 2015, [email protected] wrote: >>>> >>>>> Hi, >>>>> thanks to both :) >>>>> DRDB sounds interesting :) >>>>> >>>>> >>>>>> ----Messaggio originale---- >>>>>> Da: [email protected] >>>>>> Data: 14/12/2015 15.45 >>>>>> A: <[email protected]> >>>>>> Ogg: Re: [BackupPC-users] R: Re: Storage replica >>>>>> >>>>>> Hi, >>>>>> >>>>>> sorry, using rsync for this purpose is absolutely not recommended! >>>>>> >>>>>> As always, it depends on what you want to get. If you do not mind having >>>>>> old data as long as you have it, it might be fine with rsync running >>>>>> once a month. You have a pool of 2.5TB- on my pool of 1.4TB I aborted >>>>>> rsync after 2days! So you might need 3days or more for a ful rsync run. >>>>>> I doubt you want it this way! >>>>>> >>>>>> There is no easy ways to have them always in sync. All file level >>>>>> methods are supposed to take ages because of the hardlinks. So you might >>>>>> want to use block based duplication. >>>>>> One possibility is DRBD (which I do here). It is RAID1 through network. >>>>>> If you do not want the remote node slow down local file access you might >>>>>> think of a periodic disconnect and reconnect. Besides of this it appears >>>>>> to be rock stable and reliable. >>>>>> Another possibility are of course distributed file systems. But as you >>>>>> do not need write access on remote as long as primary is alive it might >>>>>> be overkill. >>>>>> Last suggestion is ZFS which I do not know at all. But it appears to >>>>>> have some functionality. Try it. >>>>>> >>>>>> I would say use DRBD ;) And definetly forget about rsync! >>>>>> >>>>>> Greeting >>>>>> >>>>>> Christian >>>>>> >>>>>> >>>>>> > ------------------------------------------------------------------------------ >>>>>> _______________________________________________ >>>>>> BackupPC-users mailing list >>>>>> [email protected] >>>>>> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users >>>>>> Wiki: http://backuppc.wiki.sourceforge.net >>>>>> Project: http://backuppc.sourceforge.net/ >>>>>> >>>>> >>>>> > ------------------------------------------------------------------------------ >>>>> _______________________________________________ >>>>> BackupPC-users mailing list >>>>> [email protected] >>>>> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users >>>>> Wiki: http://backuppc.wiki.sourceforge.net >>>>> Project: http://backuppc.sourceforge.net/ >>>>> >>> > ------------------------------------------------------------------------------ >>> _______________________________________________ >>> BackupPC-users mailing list >>> [email protected] >>> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users >>> Wiki: http://backuppc.wiki.sourceforge.net >>> Project: http://backuppc.sourceforge.net/ >> > > > ------------------------------------------------------------------------------ > _______________________________________________ > BackupPC-users mailing list > [email protected] > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ ------------------------------------------------------------------------------ _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
