Direkt zum Inhalt

Read error|Failed to read the snapshot|Not enough storage is available to process this command

Thread needs solution

Hi,

We have recently been getting the following error when running full backup on the Win2008 server.

The server has Acronis Backup & Recovery 10 Update 3 (build 10.0.12497) installed.

The server has 3xRAID1 136gb logical partitions and a 450Gb stand-alone drive for asr storage which should be sufficient for the backup

We have also tried the suggestion from this article but it didn't help.
http://forum.acronis.com/forum/10987

----
Operation with partition '0-0' was terminated.
Details:
Read error.

Error code: 0x70003
Tag: 0xDF81DA2C74EC501D
Failed to read the snapshot.

Error code: 0x10C45A
Tag: 0x14181C22EF45AD46
Not enough storage is available to process this command

Error code: 0xFFF0
code = 2,147,942,408 (0x80070008)
Tag: 0xBD28FDBD64EDB8BC
Additional info:
--------------------
Error code: 502
Module: 1
LineInfo: a164035b3ff39281
Fields:
Message: Operation with partition '0-0' was terminated.
Details:
Read error.

Error code: 0x70003
Tag: 0xDF81DA2C74EC501D
Failed to read the snapshot.

Error code: 0x10C45A
Tag: 0x14181C22EF45AD46
Not enough storage is available to process this command

Error code: 0xFFF0
code = 2,147,942,408 (0x80070008)
Tag: 0xBD28FDBD64EDB8BC
--------------------
Error code: 3
Module: 7
LineInfo: df81da2c74ec501d
Fields:
Message: Read error
--------------------
Error code: 50266
Module: 16
LineInfo: 14181c22ef45ad46
Fields:
Message: Failed to read the snapshot.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8bc
Fields: code : 2147942408
Message: Not enough storage is available to process this command
--------------------

Thanks,

MSA

0 Users found this helpful

Hello msa msa!

Thank you for finding time to report about the issue you've faced. I understand your concern, and will be glad to help you!

The issue you've faced is related to the snapshot creation :

The backup creation starts with the snapshot creation. For detailed description of the snapshot process, see SnapAPI. If there is not enough storage space to create the temporary snapshot file, the backup operation will fail with an error message similar to the following one:

Not enough storage is available to process this command

You can either  reduce the size of the of the snapshot or move it to another folder. Please find the detailed instructions, suitable for your OS and situation, in this KB article. Generally, you will need to edit the snapshot registry keys: in order to reduce the size of the snapshot, you will need to change the relative size parameter, and in order to move it to another folder - change the StoragePath parameter. The article I've specified contains the detailed instructions with the step-by-step screenshots. Feel free to use it, and let us know whether there's something confusing - we will be glad to clarify.

This should resolve the issue faced.

Should it remain, please gather Acronis Info and contact support directly with the information attached. Keep in mind that should there be any procrastination with the reply, you can always specify us the case number. We will do our best to speed up the process.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you!

You are not alone. I face the same problem on server 2008 and have already been through all these troubleshooting steps numerous times.
After all the troubleshooting i found it seems to relate to job creation. If i create a new Full backup job it runs great for four days then fails with the exact same errors noted above and will continue to fail until i delete the job and recreate. Then it runs fine again for four days until once again it fails. The cycle goes on and on. Server reboots did not cure it either. As mentioned i have already tried all the step mentioned in this article.

Hello Jeff,

Welcome to the forum and thank you for your message. I will certainly assist you with resolving this issue.

Please check the following KB article that has a list of all errors relating to snapshot creation, and if the solutions from there fail to resolve the problem, refer to the same article for collecting the necessary logs and contact our Support team with them. I am certain that after an investigation we will be able to resolve this issue.

Please let me know if you have additional questions.

Thank you.