To date, for me, the most serious issue with BackupPC are never-ending backups, caused by corrupted files.
I'm not sure what causes file corruption though (server crash, broken network connection, interrupted backup, killed backuppc process, something else)? When BackupPC makes a backup, and a previous full contains a corrupted file, it often gets decompressed to a file which grows beyond any limits (i.e., 45 GB, until interrupted). When we however try to decompress it by hand, we can see an error: # BackupPC_zcat < f2008-01-01-full.sql > uncompress BackupPC_zcat: can't uncompress stdin # BackupPC_zcat < f2008-04-01-full.sql > uncompress BackupPC_zcat: can't uncompress stdin It's easiest to spot with big files. The issue is a problem as it breaks backup for a given host until a broken file is removed manually. Is there a workaround to that? -- Tomasz Chmielewski http://wpkg.org ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
