|
General Troubleshooting Advice The 'volsnap' error will provide details about which drive is impacted and the underlying issue. For example:
The most common Volsnap error reported by customers is: Event ID: 25 Description: The shadow copies of volume X: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.As the error indicates, the shadow copy was deleted when the shadow copy could not grow. Since Veeam Agent for Microsoft Windows was reading from that shadow copy, the backup immediately fails with, "The system cannot find the file specified. Asynchronous read operation failed." The underlying cause, as explained in the error, is that the disk's IO load was too high. The solution is to reduce the disk IO load, implement faster storage, or . Customers most commonly select redirection of shadow copies, as it requires no infrastructure changes.
The next most common Volsnap error reported by customers is: Event ID: 36 Description: The shadow copies of volume X: were aborted because the shadow copy storage could not grow due to a user imposed limit.Like Event ID:25 above, the shadow copy could not grow and instead was deleted. This again causes the Veeam Agent for Microsoft Windows backup job to fail with the error, "The system cannot find the file specified. Asynchronous read operation failed." In this case, the resolution is to . Additional examples of Volsnap errors can be found in the section of this article. (责任编辑：) |