asked on

URGENT - Hyper-V VSS writer problem

about two weeks ago the Hyper-V VSS writer started failing so my Windows Bakckup that I used to backup the VMs stopped working, other software (BackupExec) can't backup either because it used the same writer. I updated to SP1 (W2K8 R2) but that didn't resolve the issue. I can see error 521 and 22 in my event log

What can I do to resolve the issue? It's critical as it impacts my backup

Thank you

Svet Paperov

I had the same error not so long time ago. It was caused by the fact that the default timeout of 10 minutes of Backup Server admin was expiring before the VSS was ready.

The fix was simple:
In HKLM \ Software \ Microsoft \ WindowsNT \ CurrentVersion \ SPP create a DWORD (32-bit) value CreateTimeout and set it to 12000000 (2*10*60*1000 = 20 min.)

I hope this helps

piotrmikula108

ASKER

did that but each time I run the backup Hyper-V VSS writer goes into Waiting For Completion State and Last Error: Unexpected Error. Event Log logs erro 521

Svet Paperov

Do you have enough free disk space to create shadow copies? You can use the tool DiskShadow to list and delete shadow copies. http://technet.microsoft.com/en-us/library/cc772172%28WS.10%29.aspx

piotrmikula108

ASKER

I've got 80GB free on C and 1TB on D where the virtual machines reside

I went head also and registered the Hyper-V writers by following this article

http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/backup-recovery/installing-configuring-windows-server-backup-hyper-v.html

however other Hyper-V server I use don't have that entry and WB works fine

piotrmikula108

ASKER

I also reinstalled WSB (it fixed the issues for others) but that didn't help in my case

ASKER CERTIFIED SOLUTION

Svet Paperov

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

piotrmikula108

ASKER

when I stopped one of the servers I found the backup worked, I removed AppAssure ReplaySoftware that was causing this issue