Hi,

I had similar in mind when creating my solution. Depending on the final
size of your BackupPC directory (here: 1.3TB) you will realize that
rsync isn't really an option. I'll just take ages and keep your BackupPC
server busy for hours while syncing.

I tried a lot, too. In the end I used drbd. My BackupPC directory is now
a drbd device which syncs automatically to my second server. The second
one is not in the same building and connected through a (slow!) WiFi
connection. It really slows down access on the primary but this is no
harm for me here.
You can installl BackuPC on the second one (but not activate it!) and in
emergency just start and you have a restore possibility.

A perfect solution. Only issue is the slow I/O transfer because of the
WiFi connection. If you have a lot of clients and are bound to a quick
backup this might not work. Otherwise it's perfect. ;)

Greetings

Christian


------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/