I've been running BackuPPC nicely at our office for several months now
without incident (knock on wood), now my boss wants to try something
new. We have a client machine that is accessible via our 56k frame
connection (that doesn't have off-peak hours) and indirectly via a
broadband connection. We'd like to back it up. Unfortunately the
easiest way to back it up would be through the 56k connection which
would take forever and a day and introduce unacceptable lag. Thus, the
broadband connection rears up. Here's the situation:
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?
I suppose I could ponder out _some_ SSH forwarding and tunneling means
to get to the remote server directly from the local backupPC box, but
then I lose the local convenience for an emergency restore. I'm not too
concerned about fire/lightning as I am concerned about media failure,
and an outage would be.. Well, let's say exciting.
-------------------------------------------------------
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/
