On Fri, 2005-08-05 at 17:26, Patrick Friedel wrote:
> Local server -> internet -> remote server -> remote lan -> target server
>
> My immediate thought is to run BackupPC on the remote server that would
> back up over the LAN to a) be extremely local to the remote system in
> case of problems and b) easiest. But backing up the remote server
> causes issues - I don't like that they're both in the same physical
> location, which makes me want to back them up _again_ to the local
> server. (backing up the remote server's backuppc cpool locally, in
> other words.)
>
> Am I on the crack? Would this work, or would I end up with a mess of
> files that would be impossible to restore in any imaginable circumstance?
The easy way to do this at the expense of some disk space is to
do full rsync copies to the remote server that you can reach via
broadband. Then back up that server with backuppc using rsync
over ssh. You get a nearby copy for quick restores and an offsite
compressed copy with some history.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
