Re: [BackupPC-users] HowTo backup __TOPDIR__?

2009-08-06 Thread Matthias Meyer
Thomas Birnthaler wrote: What is the best way to syncronize __TOPDIR__ to another location? As I found in many messages, rsync isn't possible because of expensive memory usage for the hardlinks. Since version 3.0.0 (protocol 3 on both ends) rsync uses an incremental mode to generate and

Re: [BackupPC-users] HowTo backup __TOPDIR__?

2009-08-06 Thread Pedro M. S. Oliveira
while reading linux journal look at what i found... maybe it will do what you want You can use the dd and nc commands for exact disk mirroring from one server to another. The following commands send data from Server1 to Server2: Server2# nc -l 12345 | dd of=/dev/sdb Server1# dd if=/dev/sda |

Re: [BackupPC-users] HowTo backup __TOPDIR__?

2009-08-06 Thread Les Mikesell
Matthias Meyer wrote: Since version 3.0.0 (protocol 3 on both ends) rsync uses an incremental mode to generate and compare the file lists on both sides. So memory usage decreased a lot, because just a small part of the list is in memory all the time. But the massive hardlink usage of

[BackupPC-users] HowTo backup __TOPDIR__?

2009-08-05 Thread Matthias Meyer
If I want to have desaster resistent backups I need to have the backups at least on two locations. What is the best way to syncronize __TOPDIR__ to another location? As I found in many messages, rsync isn't possible because of expensive memory usage for the hardlinks. In my opinion dd or cp -a

Re: [BackupPC-users] HowTo backup __TOPDIR__?

2009-08-05 Thread Les Mikesell
Matthias Meyer wrote: If I want to have desaster resistent backups I need to have the backups at least on two locations. What is the best way to syncronize __TOPDIR__ to another location? As I found in many messages, rsync isn't possible because of expensive memory usage for the hardlinks.

Re: [BackupPC-users] HowTo backup __TOPDIR__?

2009-08-05 Thread Thomas Birnthaler
What is the best way to syncronize __TOPDIR__ to another location? As I found in many messages, rsync isn't possible because of expensive memory usage for the hardlinks. Since version 3.0.0 (protocol 3 on both ends) rsync uses an incremental mode to generate and compare the file lists on both