VCB Snapshots Failing

[Brandon7a]

I am getting the below error when VCB tries to create a snapshot of one of my VM's.

Creating a quiesced snapshot failed because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine

I reinstalled VMtools without the sync and VSS drivers and I'm still getting the same error. I have read that renaming the .vmsd and .vmsn files could fix the issue. I do not see a .vmsn file in the datastore but I do see a .vmsd file. Can I rename the .vmsd file while the server is up or does it have to be powered off? Is it safe to rename this file?

Thanks

[vmroyale]

Hello.

Can you create a snapshot manually?  What app(s) is in this VM?  Has VCB ever worked with it?

You should be able to delete the .vmsd file while the VM is running.

Good Luck!

[Brandon7a]

VCB has worked in the past but has suddenly stopped. It is working properly for my other VM's. Creating a snapshot manually will probably work but I would hate to try it now since his is our production database server. So renaming the .vmsd file while the server is in production will not harm the machine?

[vmroyale · Accepted solution]

As long as you have no snapshots, then there should be no issue with renaming this file.