Pages: 1
RSS
Corrupted Backup files?, Restoration (sometimes) stops with corrupted file error
 
This is a problem I have been having on and off when restoring TB backup files (.tbk) on another PC.

I do my work/home synchronizing with this "method" and have been doing this for some years. I create my .TBK file and then just restore it on the other PC. transfer is done using a USB flash drive.

However I sometimes get a message when restoring that my .TBK file is corrupted and restoration stops. I have used 4 different USB Flash drives (512MB, 1GB, 2GB and 4GB) and this problem has occurred in all 4 cases.

Also I always use safe USB removal and in the last year I use an app called USB Safely Remove.

This is not a critical problem per se but it can be frustrating sometimes (i.e. when restoring on a Friday evening before a weekend at home.. I've had to go back to work for another backup at times)    :(

So I thought I'd mention it here and see if anyone else has had a similar problem  :)

PS: last but not least.... Happy New Year everyone!   :D
Edited: Costas Giannakenas - 02 January 2009 18:18:13
 
are You restoring TBK in same version it was created in?
 
a more simple and error-proof method is to simply zip or rar your mail folder on the first PC and then extract it on the other PC overwriting existing files (theBat should be closed on both PC's when you do that).

With rar you can customize this, for example archive only files modified in the last X days so that files that haven't changed since the last sync will be skipped and a smaller backup will be created. Also rar compression is much better, you can add a recovery record etc.

I always backup my mail and sync TB installations between PC's with WinRar, never had a problem.
Edited: bigg one - 03 January 2009 00:59:04
 
Marek Yes it is the same version.... always 3.99.29

bigg one I haven't tried doing what you suggest - well not for the purpose of synchronizing anyway.

I will follow your advice and yes... RAR is great  :D
 
I am reviving this thread as I am now using the latest (v4.2.9.1.) version but I see that the problem with synchronizing (via .TBK backup files) still persists.

I have to use bigg one's advice to get the job done every time as the .TBK files are always aborting with a corrupt file message :(

This is VERY frustrating and I would have thought that RITLabs would have sorted this bug out by now. It's not that it's a far-fetched function to want to backup/restore one's message base.... It's an everyday task for lots of users.

What puzzles me is why the backup files should be "corrupted" at all ????

Any ideas? Advice?

PS: I am using the same version on both PCs
Pages: 1