B&R 11 - Incremental Backup fails - Error occured while reading the file. The handle is invalid.

Anyone? :(

We have the same problem on several servers, and have various open cases with Support regarding this since the release of ABR11. BUT, we made some progress. We discovered that this problem is specific to File level backup jobs, it doesn't happen to volume level backup jobs. We recreated our backup tasks on the most affected servers as volume backups. This is not ideal - they are always larger (incremental with file level backups were often less than 1GB, incremental with volume level backups are always at least 5 GB). Also, you can't select what to backup. You have to selet the whole volume and create exclusions. Also, you can't combine file and volume level in the same archive (makes sense). We had to create a new archive for volume level backups, and that wouldnt' apply retention policies to the old file level archive, so disk fills up and we have to do to "manual retention policies" - deleting the olders TIB files every few days.

With one failed incremental, all later incrementals are not usable. We tried to use Differential backups instead, but they were all failing. Only afte that we switched to the volume level.

The last support representative that we talked to said that this is a know issue with file level backups. Up until then, everyone seemed totally puzzled. I think Acronis doesn't know what is behind it (no suggestions or solutions to our support case), but is now at least aware that this is happening. I see a light at the end of the tunel.

I've posted about this issue also.

http://forum.acronis.com/forum/27602

No resolution from Acronis support, just a lot of wasted time working with them and messing around with this trying to resolve it myself. Definitely has to do with the backups not liking the archive created with the full backup. I can delete the archive (using Windows Explorer...hangs when I try to use Acronis to do it), and I get one full backup but no incremental. I've also tried changing the backup job's destination and leaving the old archive. For example, the job was set up to go to Archive(1). Got one full, but no inc. Then I left that archive there, and just changed the job to go to Archive(2). One successful full but no inc. I change it to go to Archive(3)...same thing.

I, too, have a volume level backup that's been running with (almost) no issues. So I guess I'll change this one to be a volume level backup also. I've been trying to avoid that because of the storage space issue, but I'll just have to figure that out. More than enough of my time has been wasted.

We were very persistent with support on this issue because this renders backups unusable. I finally received a response to the last attempt to get this resolved (see below). Sounds like there is no solution, but at least it is now registered as a legitimate problem and maybe will be addressed later on:

We wish to inform you that the fix for this issue will be available in the future build of the Acronis product.

Please subscribe to the Acronis newsletter to know whenever the build becomes available for download.
http://kb.acronis.com/content/1658

Please let us know if you have any other questions. We will leave the case open until the issue is resolved.

--
Best regards,
Manish.Kumar Gupta | Support Professional

Same issue here ABR11. Differential backup to a local drive... So now my system is vulnerable.

--------------------
Log Entry Details
--------------------
Type: Information
Date and time: 2/13/2012 6:56:06 AM
Backup plan: [None]
Task: [None]
Code: 262,145(0x40001)
Module: 4
Owner: nbagno
Message:
Error occurred while reading the file.
Additional info:
--------------------
Error code: 1
Module: 4
LineInfo: 7ceb2cdc9fb1204a
Fields: function : ReadFile, $module : C:\Program Files (x86)\Acronis\BackupAndRecovery\DiskBundle.dll
Message: Error occurred while reading the file.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8bc
Fields: code : 2147942406
Message: The handle is invalid
--------------------
--------------------

Hi all,

Thank you for your comments, and for bringing this issue to our attention.

The handle is invalid is unfortunately a pretty common error, which appears usually during the file-level or incremental backup. This issue was solved in the new update, so if you receive the error when you're backing up a large amount of data, or running an in.cremental one, please contact me via PM for the instructions on where to obtain a fix.

Please note that in order to send you a fix we need to be sure that you have the exact same issue. Please send me a message with the exact step by step issue description.

Let us know if you have any additional questions, we will be glad to help  you.

Thank you.

We have the same issues. recently deployed Hyper-V in clustered storage environment. We are running File Service in a cluster for all company data. When backing up this data using file backup - incremental backups fail every time. Only first full backup was successful. message received every time is handle is invalid

Where can I obtain the fix you mentioned? We do have support cover with acronis

regards

They have retracted this statement. You will need to wait for an official patch... Good luck.

The Incremential backup works on our structure only times to times (without particular reasons) with an amount of 300k files, meantime differential backup fails everytime with this particular error. (but works fine with less files stragely in another directory) I hope the update will fix that.

Yana wrote:

Hi all,

Thank you for your comments, and for bringing this issue to our attention.

The handle is invalid is unfortunately a pretty common error, which appears usually during the file-level or incremental backup. This issue was solved in the new update, so if you receive the error when you're backing up a large amount of data, or running an in.cremental one, please contact me via PM for the instructions on where to obtain a fix.

Please note that in order to send you a fix we need to be sure that you have the exact same issue. Please send me a message with the exact step by step issue description.

Let us know if you have any additional questions, we will be glad to help  you.

Thank you.

how did you solve it, i am very interested, because I get this error when making incremental of a 200GB full backup (files and not partition). please help me. I have buid 17240 (I think)

greetings

I have buid 17240 (I think)

It's a strange number and doesn't look like any known build. Anyway, this bug was present in 17217 and 17318 builds, and is fixed in 17437 and above (17438 and 17440). So if you have the older build, update, if you have later builds, update to the last available and contact support (because they will have you to update anyway). All above is in assuption that the error you have is exactly as posted here.