Direkt zum Inhalt

Error - Failed to read the snapshot - Aronis Backup and Recovery 10 Adv server

Thread needs solution

Hi

We have configured backup and recovery management console to backup 3 machines. Two of these are running MS Server 2008 STD.

One of the servers the back up failed. The acronis log:

-------------------------------------------------------------
Log Entry Details
-------------------------------------------------------------
Type: Error
Date and time: 27/10/2009 10:36:28
Backup plan: Backup 24/10/2009 15:10:33
Task: Daily backup
Managed entity type: Machine
Managed entity: *******
Machine: *******
Code: 11,863,304(0xB50508)
Module: 181
Owner: administrator
Message:
Task 'Daily backup' failed: 'Failed to run the backup and recovery engine.
Additional info:
--------------------
Error code: 2
Module: 218
LineInfo: 600f7166ce397ef2
Fields: $module : C:\Program Files (x86)\Acronis\BackupAndRecovery\mms.exe
Message: Failed to run the backup and recovery engine.
--------------------'.

The MS Event viewer gave this application error

Error code: 502
Operation with partition '0-0' was terminated.
Details:
Read error (0x70003)
Tag = 0xDF81DA2C74EC501C
Failed to read the snapshot. (0x10C45A)
Tag = 0x14181C22EF45AD38
Not enough storage is available to process this command (0xFFF0)
code = 80070008)
Tag = 0xBD28FDBD64EDB8B9

The Server has RAID 1 split into 2 partitions c: is 50GB in size with 17GB free and D: is 100GB with 75GB free

Can anyone advise?

Cheers

Slinky.

0 Users found this helpful

Hello Slinky,

Thank you for using [[http://www.acronis.com/enterprise/ | Acronis Corporate Products]]

Unfortunately, the provided information doesn't allow to find the exact reason of the encountered issue. Could you please provide us with a couple of diagnostic files?

1) Could you please provide us with the log file of the failed operation in .XML format? 

- Launch the program;

- Connect Management Console to the Agent;

- Choose the log entry that contains errors;

- Click on the diskette icon Save all to file;

- Specify the location you want to save the file to;

- Attach the log file to your next post. 

2) Please download Acronis Report utility available here and run it, create a report and attach to your post.

This will provide us with detailed information on the hard drive partition structure.

This information will help to find the reason of the issue and to provide you with a possible solution. 

We are looking to hear back from you.

Thank you.

Hello
i've got the same Problem with one of our servers. The Logfile and the Report are attached.

Thank you

Anhang Größe
12022-86311.txt 134.36 KB

Hello
We are having the same problem with one of our servers. We are running build 10.0.11345. The Logfile and the Report are attached. Please contact me with a way to fix...

Anhang Größe
16811-86956.txt 229.14 KB

Same problem showing up on Acronis Backup and Recovery 10 workstation.

Anhang Größe
17174-87022.txt 552.63 KB

Hello all,

Thank you for the provided information, I will be happy to help.

The issue is related to the lack of memory resources available for your systems. You can check this statement in the following way:

Please reboot the computer if it is possible and execute a backup operation again. Most probably, you will be able to perform several backup operations without any errors. Some time later the issue will be reproduced.

You can try to overcome the encountered issue by disabling Multi-volume snapshot and disabling Create snapshots using VSS in the default backup options. This will allow to reduce memory requirements and can solve the issue.

If this doesn't help, you can temporally suspend some unnecessary services (not Acronis services) running on your system during the backup procedure. 

Please do not hesitate to ask additional questions if the provided information is not clear or you need a further assistance. 

Thank you.

Dear Customers,

The issue discussed in this topic has been fixed. The fix is available in new update of Acronis Backup & Recovery products.

Problem was related to SnapAPI driver improperly reading the VSS snapshot. New version of Snap API contains fix for that and it is incorporated in update 3 released recently.

Thanks,

Andrey.