Aller au contenu principal

VSS Snapshot Error in Hyper-V Cluster event logs

Thread needs solution

I am getting this error when the backup jobs kick off:

A backup application initiated a VSS snapshot on Cluster Shared Volume 'Volume1' ('HV_CLUSTER1') without properly preparing the volume for snapshot. This snapshot may be invalid and the backup may not be usable for restore operations. Please contact your backup application vendor to verify compatibility with Cluster Shared Volumes

Anybody know if this is safe to ignore?

0 Users found this helpful

Hello Jason,

Thank you for your post. I will be happy to assist you.
To begin with, as we can see the error states that the backup may be invalid, so there is no guaranteed safety at the moment.
I would like to discuss the issue with Acronis Development team representatives, but for that I require the following information.

1. Acronis System report, gathered as per Acronis KB article: http://kb.acronis.com/content/36248
2. Separate log of the backup procedure which gives you the above mentioned error. You can do this by selecting particular log in the "Log" view and clicking "Save selected to file"
3. Also, please describe your Hyper-V environment more precisely, as well as explain your current backup strategy.

I will PM you the Acronis FTP account link, where you'll be able to upload the requested data.

Yours truly,

My registration username and password does not give me access to http://kb.acronis.com/content/36248

Edit: I found a link and I am collecting the information now.
Edit: Hyper-V Environment
We have a two-node Hyper-V cluster (R2) with the latest patches running with an iSCSI backend. The iSCSI hardware is 2x Dell MD3000i SANs fully populated with 600G 10krpm drives. There are 3 cluster shared volumes, and all guests and divided up among the 3 volumes. Each host has 64GB of ram and enough local storage for the full installation of Windows 2008 R2 Enterprise. Each host is connected to the network via 10GB copper. Most guests are Windows 2008 R2 server, with a few being Windows 2003 Server. The backup server is on the same network as the Hyper-V servers, and is also connected to the network via 10GB copper.

Well, I guess I really stumped tech support on this one. They have not contacted me since I uploaded the files.

Hello Jason,

I have checked the information in the system report and the log entry which you have provided and the reason of the warning is still unclear.
Since you have a valid maintenance, I am now creating the support case and will follow up via e-mail later today.

Yours truly,

Bagaudin: It has been quite a few days since I sent you the information for the SnapApi log. Any word yet about a resolution?

Hello Jason,

Thank you for the follow-up.

Bagaudin is currently working with you directly and as soon as the issue is resolved we will post an update with the solution for our forum community.

Please let me know if you have any other questions.

Thank you.