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: step...@physics.unc.edu >Data: 15/12/2015 14.41 >A: "absolutely_f...@libero.it"<absolutely_f...@libero.it>, <backuppc- us...@lists.sourceforge.net> >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, absolutely_f...@libero.it wrote: > >> Hi, >> thanks to both :) >> DRDB sounds interesting :) >> >> >>> ----Messaggio originale---- >>> Da: chrisc...@knebb.de >>> Data: 14/12/2015 15.45 >>> A: <backuppc-users@lists.sourceforge.net> >>> 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 >>> BackupPC-users@lists.sourceforge.net >>> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users >>> Wiki: http://backuppc.wiki.sourceforge.net >>> Project: http://backuppc.sourceforge.net/ >>> >> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> BackupPC-users mailing list >> BackupPC-users@lists.sourceforge.net >> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users >> Wiki: http://backuppc.wiki.sourceforge.net >> Project: http://backuppc.sourceforge.net/ >> > ------------------------------------------------------------------------------ _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
