When I tried to use a replicated backup archive on a new server, most of the host directories in /var/lib/backuppc/pc/ were deleted as soon backuppc attempted to start backups, followed by an error message that the (non-existent) host directory could not be accessed, or similar wording.
The only changes I made to the default config.pl file were to the ServerHost, EMailAdminUserName, BackupFilesExclude, XferMethod parameter (depending on host), and some changes to the blackout periods. All hosts backed up without error after the respective host directories were recreated. Oddly, on one host 3 of 10 backups survived. What this tells me is that whatever caused the backups to be deleted, it's not a fundamental issue with the format of the backups, since *some* of them survived. The new server uses the latest debian backuppc, version 2.1.1-2, while the replicated archive came from a backup server running backuppc 1.5. I don't see this problem in the debian bug reports, but it's not surprising given the difficulty of replicating backuppc archives in the first place. (It took several days to replicate the archive.) I hope this serves as a fair warning to somebody. At least I'm glad I did not risk on my old backup server by upgrading it. I am now running two backup servers until my new one fills up with 90 days worth of backups, which is obviously not an optimum solution. ------------------------------------------------------- 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/
