AntonVZhbankov
Immortal
Immortal

Windows 2008R2 snapshot problem on 4.1

I have problem with snapshots on one of my VMs. And what's strange it started only last friday.

One of my DC's on Win2008R2 refused to take quiesced snapshot after clod migration from one cluster to another. Remaining DC, absolutely the same configuration still can take snapshots.

I've made new VM, built from nothing, clean installation, promoted to DC instead of failed on and problem still persists.

What I've found in Windows logs:

1) Volume Shadow Copy Service error: Unexpected error DeviceIoControl(
?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 000000000000042C,0x00560000,0000000000000000,0,00000000003C7F70,4096,[0]). hr = 0x80070001, Incorrect function.

.

Operation:

Exposing Recovered Volumes

Locating shadow-copy LUNs

PostSnapshot Event

Executing Asynchronous Operation

Context:

Device:
?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}

Examining Detected Volume: Existing -
?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}

Execution Context: Provider

Provider Name: VMware Snapshot Provider

Provider Version: 1.0.0

Provider ID: {564d7761-7265-2056-5353-2050726f7669}

Current State: DoSnapshotSet

2) lsass (460) An attempt to write to the file "
?\Volume{b6c3b2c0-a388-11df-badc-0050568b0019}\Windows\NTDS\edb.log" at offset 7525888 (0x000000000072d600) for 512 (0x00000200) bytes failed after 0 seconds with system error 19 (0x00000013): "The media is write protected. ". The write operation will fail with error -1032 (0xfffffbf8). If this error persists then the file may be damaged and may need to be restored from a previous backup.

3) lsass (460) Unable to write to logfile
?\Volume{b6c3b2c0-a388-11df-badc-0050568b0019}\Windows\NTDS\edb.log. Error -1032 (0xfffffbf8).


---

MCSA, MCTS Hyper-V, VCP 3/4, VMware vExpert

http://blog.vadmin.ru

EMCCAe, MCITP: SA+VA, VCP 3/4/5, VMware vExpert http://blog.vadmin.ru
0 Kudos
99 Replies
HendersonD
Hot Shot
Hot Shot

In a few days I will be upgrading to vSphere 4.1 from 4.0. Any wise words of wisdom in an attempt to avoid these snapshot issues? I do use Netapp's Snapmanager for Virtual Infrastructure for backups. I have it split into two jobs. One job takes a VMWare snap before taking a filer snapshot, this is bulk of my backup. The other job just takes a filer backup and no VMWare snap first. I have Domain Controllers, SQL, Exchange, and Virtual Center server in this job.

I will be installing the newest VMWare Tools on all my VMs once the upgrade is complete but I am nervous after reading all of these posts since many of my VMs are 2008 R2.

0 Kudos
slusamson
Contributor
Contributor

I'm anxiously awaiting a procedure on this... I'm running vRanger for backups and all of my 2008 R2 servers (one running MS SQL and another running Exchange) are failing when trying to make application consistent quiesed backups. vRanger support pointed out that when a snapshot is taken from their software with quiesing enabled, it actually creates 2 snapshots at the same time for the vmdks. I checked for the dll mentioned in this thread and haven't seen it on any of my servers. Hopefully we'll have something soon!

0 Kudos
lucmorin
Contributor
Contributor

@all,

It seems that the workaround proposed by VMWare is working.

I have taken snapshots, and I've been able to restore the VM without any problem, though I'm not still 100% sure that the snapshot is application consistent (I admit lacking the knowledge to verify this, so guys, feel free to suggest).

I've posted the work around and needed files on my blog at www.stlm.ca/newblog

Let me know if this works for you.

Regards.

0 Kudos
slusamson
Contributor
Contributor

are these for x86 or x64?

0 Kudos
lucmorin
Contributor
Contributor

They are for x64

Forgive my ignorance, but is Windows 2008 R2 even available as x86 ?

Regards

0 Kudos
slusamson
Contributor
Contributor

hehe... forgive my ignorance...it isn't... slipped my mind Smiley Happy

0 Kudos
SewerRat
Contributor
Contributor

The snapshot does indeed complete after I went through the instructions in your blog. Thank you for that. Now if I look in the Event Viewer after a Snapshot there are 5 warnings and errors in there.

Four of them are similar to this one:

Log Name: Application

Source: VSS

Date: 10/25/2010 2:58:35 PM

Event ID: 8194

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: computername

Description:

Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.

. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:

Gathering Writer Data

Context:

Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}

Writer Name: System Writer

Writer Instance ID: {2d606c72-11e4-4063-9e94-a57eb4be60b3}

Event Xml:

0 Kudos
Marcj1
Enthusiast
Enthusiast

Did this work for anyone else? It did not work for me, athough I do now get error messages similar to SewerRat which I did not get before.

Similar situation, 2008 R2 Domain controller on Vsphere 4.1. Can't get a quiesced snapshot.

0 Kudos
SewerRat
Contributor
Contributor

I never did get my 2008 R2 domain controller to take a quiesced snap.

I forgot to mention before that I think that blog is missing a step 2.5 to put the zipped VCBRequestor.dll into the c:\program files\vmware\vmware tools\drivers\vss folder.

0 Kudos
lucmorin
Contributor
Contributor

Thanks SewerRat, good catch.

I'll update the blog post.

Also, I have informed VMWare about the new messages in the event log. I haven't heard from them yet.

Regards

0 Kudos
KWBS
Contributor
Contributor

tried lucmorins solution, too. Manual Snapshot is working. But new event log errors occur:

Protokollname: Application

Quelle: VSS

Datum: 28.10.2010 08:33:23

Ereignis-ID: 8194

Aufgabenkategorie:Keine

Ebene: Fehler

Schlüsselwörter:Klassisch

Benutzer: Nicht zutreffend

Computer: XXXXXXXXXX

Beschreibung:

Volumeschattenkopie-Dienstfehler: Beim Abfragen nach der Schnittstelle "IVssWriterCallback" ist ein unerwarteter Fehler aufgetreten. hr = 0x80070005, Zugriff verweigert

. Die Ursache hierfür ist oft eine falsche Sicherheitseinstellung im Schreib- oder Anfrageprozess.

Vorgang:

Generatordaten werden gesammelt

Kontext:

Generatorklassen-ID: {e8132975-6f93-4464-a53e-1050253ae220}

Generatorname: System Writer

Generatorinstanz-ID: {ac43dc03-7287-418c-a4fe-70478fee8ede}

</Event>

Will now open a service request.

0 Kudos
RobMokkink
Expert
Expert

When will vmware release a new version of vmware tools?

This problem is more then a couple of months old.

0 Kudos
RobMokkink
Expert
Expert

When will VMware release a new version of VMware tools?

This problem is a couple of months old.

0 Kudos
KWBS
Contributor
Contributor

Support is pointing me to http://kb.vmware.com/kb/1018194 ... But when we disable vss it's not crash consistent ^^

0 Kudos
mdgunther
Contributor
Contributor

Support told me this will be fixed in 4.1 U1, but they couldn't tell me when that would be.

It was six months from 4.0 to U1, seven from U1 to U2. 4.1 hit on 7/13. Draw your own conclusions.

0 Kudos
HendersonD
Hot Shot
Hot Shot

For now I am going to create two backup jobs, one that does the VMWare snapshot before my Netapp filer snapshot and one that only does the Netapp snapshot. I will include all of my WinServer 2008 R2 servers in the latter job. Not ideal that I cannot take VMWare snapshots of R2 boxes but at least I am gettting backup. As soon as ESX 4.1 U1 comes out I can move all of my R2 boxes to the first job.

0 Kudos
Marcj1
Enthusiast
Enthusiast

Just got the response from support about the fix coming in 4.1U1. They said that it is scheduled to be released in Q1 2011.

0 Kudos
RobMokkink
Expert
Expert

Q1 2011. That is not acceptable.

0 Kudos
HendersonD
Hot Shot
Hot Shot

I agree. At best this makes the release 8 weeks off, at worst 20 weeks off. You would think this bug would be serioius enough that an interim release just to address it would happen before U1 comes out.

0 Kudos
TK22
Contributor
Contributor

Just wanted to tell you all that you´re not alone. We´re also having the same problems.

Trying to snapshot or VDRbackup of a vCenter 4.1 VM on 2008R2. It´s a ew VM on a new vSphere4.1 ESX system.

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

  • Device:
    ?\fdc#generic_floppy_drive# errors despite removing floppy

  • VSS event errors in VM

We got it all Smiley Happy

UUID key enabled from default

VCBSnapshotProvider.dll is there

And allt that stuff..

Checked a lot of KBs, VSS troubleshooting etc. but no "real" solution.

As lucmorin writes.... if you stop the VMWareVCMSDS service, then the snapshot or VDRbackup finishes without error.

Anyone got a proper solution for this yet or is it just workarounds?

0 Kudos