Vetch wrote:
> Hi all,
>
> I have a question...
>
> I tried restoring a backup to my system - it kept on failing with aborted
> by signal=PIPE.
> I have a feeling it may have been related to corrupt files within the
> hardlinks, since when I tried restoring using tar, the tar files were not
> readable, and the zip files didn't have as many files in as I would have
> expected...
>
> I didn't seem to be able to resolve that, so I wiped the system (keeping
> the home directory in tact), and rebuilt the server.
Which system? Your BackupPC server or your backup client?
> Now, unfortunately, the software I use to run the file server decided to
> delete my home directories when I restored the configuration...
> Go figure...
> So now, I'm really worried because I think that I will have lost about
> 100GB of data that I believed was backed up...
> Anyway, I'm trying to restore now, but the tar files are still coming up
> as unreadable...
>
> I guess if there are problems with the data, there's probably nothing that
> can be done?
Probably not much :-(
>
> How does backuppc check the consistency of the data once it's been added
> to the pool?
> I know that it only backs up the data once, but how does it make sure that
> the data is in a valid state?
> Is it checksums? If so, then I guess it can't be a corruption error...
> ... but I don't get why I would be finding directories of 3000 files
> showing only 1500 in a full backup...
I didn't believe that backuppc will check data consistency. That is the job
of a filesystem. e2fsck will do that for ext2/3 file systems. You should
run it regulary.
>
> Can anyone help? Any support would be greatly appreciated...
> I've got all the coursework from a Masters and a PhD on there!
>
> Jx
I assume you are running BackupPC on Linux and use ext3 as filesystem.
So I would advise:
1) make a image backup (e.g. partimage) of your /var/lib/backuppc or
wherever your __TOPDIR__ resides.
2) try to open some files (select files which are importend for you) from
the BackupPC GUI (use your backup client, open http:\\<your
server>/backuppc, login, left hand menu, Browse Backups, click on a file
and say open)
3) run e2fsck on the device where /var/lib/backuppc located (unmount the
device first) and expect to lost data if e2fsck find file system errors.
You should run e2fsck as soon as possible. Elsewere filesystem errors can
grows and destroy more data then necessary.
I have had a similiar problem 7 month ago. A lot of file system errors and I
lost most of my backups. Fortunately I didn't lost data on my backup
clients at the same time.
br
Matthias
--
Don't Panic
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
