|
Re: Restore problem - 2.1.0: msg#00197sysutils.backup.backuppc.general
Adam Grelck writes: > Two days ago I got BackupPC up and running more or less flawlessly on > my dual PPro server with 512MB RAM. Yesterday, one of the harddrives > that I was backing up failed, but I didn't worry too much because I > had a full backup. I rebuilt the PC and went straight to the BackupPC > web interface and promptly scheduled all the files to be restored. > Everything looked fine on the PC, all 7 gigs were restored and the > filenames were correct. > > A couple hours it was done, I decided that I should probably spot > check the files to make sure they were correct and that is when I ran > into the problem - the files' contents were totally mixed up. Text > files sometimes had Excel files within them, etc. I knew that the > files were properly stored on the server because I had browsed the > backup of the PC before it crashed and the files were fine, so I > decided that I would try to restore a smaller chunk. When I did this, > everything worked fine. All the files restored properly. This leads > me to believe that rsync or BackupPC is choking on the older hardware > and botching the restore. > > Has anyone else run into this when restoring their files? Ouch. I've heard one other report of this. I've tried to replicate this but I have not been able to. What is the target system and what version of remote rsync are you running? Rsync restore works by generating a file list and sending that to the client. Each side then sorts the file list. From that point on each side refers to files by an index into the sorted list. So there is the theoretical possibility that if each side sorts the list in a slightly different manner then all the files will get mixed up. Of course, this shouldn't happen, but it appears it has in your case. Certainly I would like to try to debug this, but somehow I need to recreate the setup and problem. If you can replicate it on a smaller data set (eg: not the entire file system) then that would be great. For example, if you just restore /etc does the problem still happen? In the meantime, one work-around is to restore using tar, eg, a command like: /usr/local/BackupPC/bin/BackupPC_tarCreate -h CLIENT -n NNN -s / . | ssh -l root CLIENT tar -C / -x -f - Craig ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ BackupPC-users mailing list BackupPC-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/ |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Faster compression: 00197, Carl Wilhelm Soderstrom |
|---|---|
| Next by Date: | Re: Faster compression: 00197, Wayne Scott |
| Previous by Thread: | Restore problem - 2.1.0i: 00197, Adam Grelck |
| Next by Thread: | Re: tape backup aborted by signal=ALRM: 00197, Craig Barratt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |