-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Matthias Meyer wrote: > Johan Ehnberg wrote: > > 1) So you would recommend: > mv /var/lib/backuppc/cpool /var/lib/backuppc/cpool.sav > mkdir /var/lib/backuppc/cpool > I would believe that the hardlinks > from /var/lib/backuppc/pc/<host>/<backup-number> than will point to > cpool.sav instead cpool? > The disadvantage is that up to now every file have to be created in the new > cpool. No one of the existing files (in cpool.sav) can be reused. > By deleting of old backups during the next month, the cpool.sav should be > empty and can be deleted than. > > 2) I would believe that every backuped file will be checked against cpool. > Is it not identical than a new file will be created in cpool. > During the deletion of old backups also old, (maybee corrupt) files in cpool > will be deleted. So possible corrupt files in cpool will disappear > automaticly during the next month. > > Which strategy would you prefer?
Personally, I'd firstly move from ext2 to ext3 to try and prevent this from happening again. Then, I would delete all the directorties (in fact, all non-files) from under the pool/cpool that don't belong. Then, set the VerifyProb=1 and run a full backup of each host. Of course, part of me is saying "start fresh"... In fact, I don't think anyone can really suggest the correct course of action, but the lowest risk (if you don't need to restore any old data) is to start fresh. All other options carry some risk, and to be honest, I don't understand those risks, and probably you don't either (which is why you are asking). If you have the available space, then start fresh, otherwise, you need to start to consider the value of your data, and what happens if your backup is storing corrupt data. What happens if you delete all existing backups, and then take a set of full backups? How important is the ability to restore data from last week compared to your space requirements? Is now a good time to replace your data disks with bigger disks? Hope that somewhat helps..... and I also sympathise with you. Best of luck :) Regards, Adam -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklzRrwACgkQGyoxogrTyiUk8QCdFsvfVIJv/6Tjna1Mlzzs0/3l WBoAmgOb8vjwHGtmwqJsukyj2v3T1KbS =OVGC -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
