I do the rsync route. The key is to use rsync3. If you dont want to upset
the balance of your distro you can keep your existing rsync install and just
build rsync3 and drop it in /usr/bin/rsync3 or something.
I have a 1.54Mb link to a remote office and I have one backuppc server
handling backups and another configured identically except it does not have
backuppc running. I sync using rsync3 across the network.
This works exceptionally well now that rsync3 is out. When I was using
rsync2 it was pretty slow.
On Thu, Nov 20, 2008 at 6:04 AM, Rob Owens <[EMAIL PROTECTED]>wrote:
> Andrew Libby wrote:
> > Greetings,
> >
> > I've been running BackupPC for a few months. I'm now
> > thinking of disaster recover strategy. My initial thought
> > is to replicate (via rsync) the BackupPC configs and data to
> > another server. This server would not actively run BackupPC
> > jobs, but I would like to be able to restore from it in the
> > even to of a catastrophe.
> >
> > Is this a reasonable approach? Are others doing something
> > like this, or something else even to meet the same objectives?
> >
> Seems reasonable, as long as you test it. Rsync'ing the pool can take a
> long time (I've done it). You should consider whether you want your
> second server to be on-site or off-site.
>
> Here's what I do:
>
> I have one on-site BackupPC server, and one off-site BackupPC server.
> They are each configured to backup the same hosts -- I don't rsync one
> server to the other, I just let them both run. Each server uses
> software RAID 1 (mirrored drives). If a drive fails, I have an
> immediate failover via RAID. If a server burns up in a fire, I have two
> choices to restore: 1) perform my restore over the internet, which will
> be pretty slow, or 2) ship one of the hard drives from the remote server
> to me so I can install it in a new server and perform my restore locally.
>
> -Rob
> ********************************************************
>
> The information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and/or privileged
> material. If you are not the addressee, any disclosure, reproduction,
> copying, distribution, or other dissemination or use of this transmission
> in
> error please notify the sender immediately and then delete this e-mail.
> E-mail transmission cannot be guaranteed to be secure or error free as
> information could be intercepted, corrupted lost, destroyed, arrive late or
> incomplete, or contain viruses.
> The sender therefore does not accept liability for any errors or omissions
> in the contents of this message which arise as a result of e-mail
> transmission. If verification is required please request a hard copy
> version.
>
> ********************************************************
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> 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/
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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/
