I once made --remove-older-than part of my automated backup tasks. But the amount of time it took to complete execution went up to at least 30+ hours (I have months of backup history). This coupled with the fact that it is a remote backup, just made the execution time worst.
In the end, I removed it from my backup tasks and just allow rdiff-backup to eat up HDD space. HDD space is cheap, time is not. Yen Kwoon -----Original Message----- From: Jan Söderback [mailto:[EMAIL PROTECTED] Sent: Saturday, October 13, 2007 12:03 PM To: [email protected] Subject: [rdiff-backup-users] Expected remove-older-than execution time? I started a --remove-older-than run on my backup server to remove a large number of increments (hundreds). The command has been running for over 24 hours now. Is this expected? If not, is it safe to cancel the command and run it again with a smaller number of increments? (rdiff-backup version 1.0.5 on CentOS 4.) Also, I finally got around to uppgrading my Debian server to etch, but the rdiff-backup version in etch is 1.1.5. Is it possible to use this version with my backup-server running rdiff-backup 1.0.5? Thanks, Jan No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.15.22/1111 - Release Date: 11/5/2007 4:36 AM _______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
