Direkt zum Inhalt

The file is corrupted

Thread needs solution

After creating a backup to a NAS device on a home network, Acronis attempts to validate the tib file, which is about 50G. After about an hour into the validation, the execution fails and records the following entries in to the log:
1 Information 11/24/2012 8:07:58 PM Operation ToshibaNightlyBackup started.
2 Information 11/24/2012 8:07:59 PM Analyzing partition '0-0'...
3 Information 11/24/2012 8:07:59 PM Analyzing partition '1-1'...
4 Information 11/24/2012 8:07:59 PM Analyzing partition 'C:'...
5 Information 11/24/2012 8:08:00 PM Analyzing partition '1-3'...
6 Information 11/24/2012 8:08:00 PM Priority changed to Low.
7 Information 11/24/2012 8:08:01 PM Locking partition C:...
8 Information 11/24/2012 8:08:01 PM Create Incremental Backup Archive Password Protected From: My Data Compression: Maximum Exclude: Files matching mask Match criterion: *.tib, *.tmp, *.~
9 Information 11/24/2012 8:08:12 PM Backing up to file: "\\NETGEAR-NAS\backup\Toshiba\ToshibaNightlyBackup.tib"
10 Information 11/24/2012 10:58:31 PM Validate Backup Archive Location: "\\NETGEAR-NAS\backup\Toshiba\ToshibaNightlyBackup.tib"
11 Error 11/24/2012 11:53:09 PM The file is corrupted.
12 Error 11/24/2012 11:53:09 PM Operation has completed with errors.

I can open the tib file, but if I run a separate validation, the validation fails.

There are two other computers on the same LAN that are making backups of 40G-50G to the same NAS, and everything works.

I've searched the forum, but can't find anything to fix the problem. Does anybody have any ideas?
Nomad

0 Users found this helpful

Nomad,
One of my fellow MVP's posted your thread on our internal MVP forum. I have a QNAP NAS and would like to try and replicate your scenario.

I have a few questions:

What version of ATI are you using?

This is an incremental back up. Are the jobs running on the other two machines successfully the same? Same type of backup task?

I'd suggest the following. Make these changes ONE at a time and test each.

-First try without a password on the archive
-Then try using normal compression

Shadowsports,

I'm using ATI Home 2011, Update 3 (build 6942).

The other computers are running the same build and are also running incremental backups. They are also running full compression, but are not using security.

I have removed the password, and there is no difference between with and without a password. I will try with normal compression.

Thanks for your reply. With this additional information, I'm more inclined to think there is a problem with a previous .tib or some kind of file system error. Are you backing up password protected or encrypted files??

Have you validated the first full .tib successfully, then attempts to validate an incremental fail?

To be thorough I'd perform a chkdsk /f on all partitions on the disk you are backing up. I would then create a new task, same incremental scheme. No password or compression. Validate the first full, reboot, then perform an incremental, attempt to validate it. If successful, add password, re test (incremental), then compression (test incremental again).

If you other machines are utilizing the same back up method and similar types of files (your data) and these are completing successfully to the NAS, I see little possibility that it has anything to do with the behavior you are seeing on this one system.

I've dug up my 2011_6942 disk and will perform a validation after backup to my NAS using compression/password on Vista Ultimate.

Follow up. No issues with back up or validation Vista Ult. Incremental scheme 2011_6942 to my QNAP NAS. Used compression and specified password for archive. The only real difference between our tests was I did a full disk image back up, then incremental and you did My Data. Certainly different tests, but as I stated previously, I suspect their is a problem with a previous .tib, the file system on the disk or with encrypted data if this is being used. Chkdsk, Validation of the previous .tib and possibly encryption (if used) is the likely culprit here.