On 2016-01-15 17:15, Gandalf Corvotempesta wrote: > 2016-01-15 14:41 GMT+01:00 Nicola Scattolin <[email protected]>: >> now i'm copying my old pools on the new drive but i got a lot of I/O >> errors on old drive, there is a way to force backuppc to check if the >> files are still ok? Because i know that if a file is alredy been copy by >> backuppc it will not copy it again, but i don't want to lose files when >> backuppc think a file is already in the pool, but it's corrupted. > > I think BPC is smart enough to detect differences. > AFAIK , BPC check file checksum between backupped file and "fresh" file. > If different, file would be transfered.
When using checksum caching, the detection of corrupt files on the backuppc server is only the set percentage probability. Corrupt files may go unnoticed for quite a while. Setting checksum probability to 1 for a complete round of full backups will check every file to be extra sure. The script I mentioned use goes through tar, so checksums are not carried over. I had some issues (duplicated files that would cause an error on each transfer) that backuppcc was unable to solve in the corrupt pool even after the pool was moved to a good drive. They went away when pre-seeding the new pool. /johan ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ 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/
