WBS Backup issues

[Guest Mark Murphy]

I am having an issue using WBS on a Hyper-v Host with 4 VM's running on it.

Config is as follows

 

64bit Windows 2008 with Hyper-v role

WBS feature is installed.

All the latest patchs released to 09/12/2008

 

Including Update for Windows Server 2008 x64 Edition (KB956697)

 

Installation date: ‎9/‎12/‎2008 8:23 PM

 

Installation status: Successful

 

Update type: Recommended

 

Install this update to resolve an issue in which the Hyper-V Volume Shadow

Copy Service (VSS) does not back up virtual machines properly. After you

install this item, you may have to restart your computer. This update is

provided to you and licensed under the Windows Server 2008 License Terms.

 

More information:

http://support.microsoft.com/kb/956697

 

Help and Support:

http://support.microsoft.com

 

 

VM's are

1 Windows 2008 DC using a VHD for storage

1 Windows 2008 Web server Ed. using a VHD for storage

1 Windows 2008 Exchange server 2007 using VHD's for storage

1 Windows 2003 SP2 using pass through disks for storage

 

All VM's have the Hyper-v Intagraition tools loaded and the VSS backup

option in the VM settings is sellected for all

 

Evertime I reboot the first backup attempt fails and then every backup

atempt after reports success. However I do not belive the backups after the

first one is using the Hyper-v Writer for VSS Bellow is the steps to show the

behavor.

 

 

 

Issued command after reboot >> C:\Users\Administrator>vssadmin list writers

 

 

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

© Copyright 2001-2005 Microsoft Corp.

 

Writer name: 'Microsoft Hyper-V VSS Writer'

Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

Writer Instance Id: {4a8930b1-165d-4f9b-8024-c37961a4b7ce}

State: [1] Stable

Last error: No error

 

Writer name: 'System Writer'

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

Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

State: [1] Stable

Last error: No error

 

Writer name: 'ASR Writer'

Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

State: [1] Stable

Last error: No error

 

Writer name: 'BITS Writer'

Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

State: [1] Stable

Last error: No error

 

Writer name: 'Registry Writer'

Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

State: [1] Stable

Last error: No error

 

Writer name: 'WMI Writer'

Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

State: [1] Stable

Last error: No error

 

Writer name: 'COM+ REGDB Writer'

Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

State: [1] Stable

Last error: No error

 

Writer name: 'Shadow Copy Optimization Writer'

Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

State: [1] Stable

Last error: No error

 

Then:

Start the backup and wait for failed job

 

 

Issued Command as soon as backup failes >> C:\Users\Administrator>vssadmin

list writers

 

 

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

© Copyright 2001-2005 Microsoft Corp.

 

 

Writer name: 'Microsoft Hyper-V VSS Writer'

Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

Writer Instance Id: {4a8930b1-165d-4f9b-8024-c37961a4b7ce}

State: [9] Failed

Last error: Not responding

 

Writer name: 'System Writer'

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

Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

State: [5] Waiting for completion

Last error: No error

 

Writer name: 'ASR Writer'

Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

State: [5] Waiting for completion

Last error: No error

 

Writer name: 'WMI Writer'

Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

State: [5] Waiting for completion

Last error: No error

 

Writer name: 'BITS Writer'

Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

State: [1] Stable

Last error: No error

 

Writer name: 'Shadow Copy Optimization Writer'

Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

State: [5] Waiting for completion

Last error: No error

 

Writer name: 'COM+ REGDB Writer'

Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

State: [5] Waiting for completion

Last error: No error

 

Writer name: 'Registry Writer'

Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

State: [5] Waiting for completion

Last error: No error

 

 

Issue command about 30 Sec later >> C:\Users\Administrator>vssadmin list

writers

 

As you can see the writer is gone.

 

 

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

© Copyright 2001-2005 Microsoft Corp.

 

Writer name: 'System Writer'

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

Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

State: [5] Waiting for completion

Last error: No error

 

Writer name: 'ASR Writer'

Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

State: [5] Waiting for completion

Last error: No error

 

Writer name: 'BITS Writer'

Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

State: [1] Stable

Last error: No error

 

Writer name: 'Shadow Copy Optimization Writer'

Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

State: [5] Waiting for completion

Last error: No error

 

Writer name: 'COM+ REGDB Writer'

Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

State: [5] Waiting for completion

Last error: No error

 

Writer name: 'Registry Writer'

Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

State: [5] Waiting for completion

Last error: No error

 

Writer name: 'WMI Writer'

Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

State: [5] Waiting for completion

Last error: No error

 

 

Writer is gone till next reboot. Backup Jobs kick off and finish succesfully

after this but don't think it is getting the benifits of the Hyper-v Writer

and don't know constance the VHD's are.

 

This error in the event is also logged.

 

 

 

 

Log Name: Application

Source: VSS

Date: 9/13/2008 2:39:57 PM

Event ID: 12301

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: vmserv.markandbeth.net

Description:

Volume Shadow Copy Service error: Writer Microsoft Hyper-V VSS Writer did

not respond to a GatherWriterStatus call.

 

Operation:

Gather writers' status

Executing Asynchronous Operation

 

Context:

Current State: GatherWriterStatus

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="VSS" />

<EventID Qualifiers="0">12301</EventID>

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2008-09-13T18:39:57.000Z" />

<EventRecordID>2505</EventRecordID>

<Channel>Application</Channel>

<Computer>vmserv.markandbeth.net</Computer>

<Security />

</System>

<EventData>

<Data>Microsoft Hyper-V VSS Writer</Data>

<Data>

 

Operation:

Gather writers' status

Executing Asynchronous Operation

 

Context:

Current State: GatherWriterStatus</Data>

 

<Binary>2D20436F64653A2042554543584D4C4330303030343630332D2043616C6C3A2042554543584D4C4330303030343531392D205049443A202030303030333839322D205449443A202030303030333830342D20434D443A202076737361646D696E20206C697374207772697465727320202D20557365723A20564D534552565C41646D696E6973747261746F72202020202D205369643A2020532D312D352D32312D313032393339383634332D3434303331333237312D333337333035313534332D35303020202020</Binary>

</EventData>

</Event>

--

Mark Murphy - MCSE2000

[Guest Meinolf Weber]

Re: WBS Backup issues

 

Hello Mark,

 

Have a look at this one about using pass through disk, scroll down to "Storage

considerations":

http://blogs.technet.com/virtualization/archive/2008/08/29/backing-up-hyper-v-virtual-machines.aspx

 

Also see here and search for "pass-through disks":

http://technet.microsoft.com/en-us/library/cc794762.aspx

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> I am having an issue using WBS on a Hyper-v Host with 4 VM's running

> on it. Config is as follows

>

> 64bit Windows 2008 with Hyper-v role

> WBS feature is installed.

> All the latest patchs released to 09/12/2008

> Including Update for Windows Server 2008 x64 Edition (KB956697)

>

> Installation date: ?9/?12/?2008 8:23 PM

>

> Installation status: Successful

>

> Update type: Recommended

>

> Install this update to resolve an issue in which the Hyper-V Volume

> Shadow Copy Service (VSS) does not back up virtual machines properly.

> After you install this item, you may have to restart your computer.

> This update is provided to you and licensed under the Windows Server

> 2008 License Terms.

>

> More information: http://support.microsoft.com/kb/956697

>

> Help and Support: http://support.microsoft.com

>

> VM's are

> 1 Windows 2008 DC using a VHD for storage

> 1 Windows 2008 Web server Ed. using a VHD for storage

> 1 Windows 2008 Exchange server 2007 using VHD's for storage

> 1 Windows 2003 SP2 using pass through disks for storage

> All VM's have the Hyper-v Intagraition tools loaded and the VSS backup

> option in the VM settings is sellected for all

>

> Evertime I reboot the first backup attempt fails and then every backup

> atempt after reports success. However I do not belive the backups

> after the first one is using the Hyper-v Writer for VSS Bellow is the

> steps to show the behavor.

>

> Issued command after reboot >> C:\Users\Administrator>vssadmin list

> writers

>

> vssadmin 1.1 - Volume Shadow Copy Service administrative command-line

> tool © Copyright 2001-2005 Microsoft Corp.

>

> Writer name: 'Microsoft Hyper-V VSS Writer'

> Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

> Writer Instance Id: {4a8930b1-165d-4f9b-8024-c37961a4b7ce}

> State: [1] Stable

> Last error: No error

> Writer name: 'System Writer'

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

> Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

> State: [1] Stable

> Last error: No error

> Writer name: 'ASR Writer'

> Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

> Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

> State: [1] Stable

> Last error: No error

> Writer name: 'BITS Writer'

> Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

> Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

> State: [1] Stable

> Last error: No error

> Writer name: 'Registry Writer'

> Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

> Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

> State: [1] Stable

> Last error: No error

> Writer name: 'WMI Writer'

> Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

> Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

> State: [1] Stable

> Last error: No error

> Writer name: 'COM+ REGDB Writer'

> Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

> Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

> State: [1] Stable

> Last error: No error

> Writer name: 'Shadow Copy Optimization Writer'

> Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

> Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

> State: [1] Stable

> Last error: No error

> Then:

> Start the backup and wait for failed job

> Issued Command as soon as backup failes >>

> C:\Users\Administrator>vssadmin list writers

>

> vssadmin 1.1 - Volume Shadow Copy Service administrative command-line

> tool © Copyright 2001-2005 Microsoft Corp.

>

> Writer name: 'Microsoft Hyper-V VSS Writer'

> Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

> Writer Instance Id: {4a8930b1-165d-4f9b-8024-c37961a4b7ce}

> State: [9] Failed

> Last error: Not responding

> Writer name: 'System Writer'

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

> Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

> State: [5] Waiting for completion

> Last error: No error

> Writer name: 'ASR Writer'

> Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

> Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

> State: [5] Waiting for completion

> Last error: No error

> Writer name: 'WMI Writer'

> Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

> Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

> State: [5] Waiting for completion

> Last error: No error

> Writer name: 'BITS Writer'

> Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

> Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

> State: [1] Stable

> Last error: No error

> Writer name: 'Shadow Copy Optimization Writer'

> Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

> Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

> State: [5] Waiting for completion

> Last error: No error

> Writer name: 'COM+ REGDB Writer'

> Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

> Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

> State: [5] Waiting for completion

> Last error: No error

> Writer name: 'Registry Writer'

> Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

> Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

> State: [5] Waiting for completion

> Last error: No error

> Issue command about 30 Sec later >> C:\Users\Administrator>vssadmin

> list writers

>

> As you can see the writer is gone.

>

> vssadmin 1.1 - Volume Shadow Copy Service administrative command-line

> tool © Copyright 2001-2005 Microsoft Corp.

>

> Writer name: 'System Writer'

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

> Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

> State: [5] Waiting for completion

> Last error: No error

> Writer name: 'ASR Writer'

> Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

> Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

> State: [5] Waiting for completion

> Last error: No error

> Writer name: 'BITS Writer'

> Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

> Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

> State: [1] Stable

> Last error: No error

> Writer name: 'Shadow Copy Optimization Writer'

> Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

> Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

> State: [5] Waiting for completion

> Last error: No error

> Writer name: 'COM+ REGDB Writer'

> Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

> Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

> State: [5] Waiting for completion

> Last error: No error

> Writer name: 'Registry Writer'

> Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

> Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

> State: [5] Waiting for completion

> Last error: No error

> Writer name: 'WMI Writer'

> Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

> Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

> State: [5] Waiting for completion

> Last error: No error

> Writer is gone till next reboot. Backup Jobs kick off and finish

> succesfully after this but don't think it is getting the benifits of

> the Hyper-v Writer and don't know constance the VHD's are.

>

> This error in the event is also logged.

>

> Log Name: Application

> Source: VSS

> Date: 9/13/2008 2:39:57 PM

> Event ID: 12301

> Task Category: None

> Level: Error

> Keywords: Classic

> User: N/A

> Computer: vmserv.markandbeth.net

> Description:

> Volume Shadow Copy Service error: Writer Microsoft Hyper-V VSS Writer

> did

> not respond to a GatherWriterStatus call.

> Operation:

> Gather writers' status

> Executing Asynchronous Operation

> Context:

> Current State: GatherWriterStatus

> Event Xml:

> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

> <System>

> <Provider Name="VSS" />

> <EventID Qualifiers="0">12301</EventID>

> <Level>2</Level>

> <Task>0</Task>

> <Keywords>0x80000000000000</Keywords>

> <TimeCreated SystemTime="2008-09-13T18:39:57.000Z" />

> <EventRecordID>2505</EventRecordID>

> <Channel>Application</Channel>

> <Computer>vmserv.markandbeth.net</Computer>

> <Security />

> </System>

> <EventData>

> <Data>Microsoft Hyper-V VSS Writer</Data>

> <Data>

> Operation:

> Gather writers' status

> Executing Asynchronous Operation

> Context:

> Current State: GatherWriterStatus</Data>

> <Binary>2D20436F64653A2042554543584D4C4330303030343630332D2043616C6C3A

> 2042554543584D4C4330303030343531392D205049443A202030303030333839322D20

> 5449443A202030303030333830342D20434D443A202076737361646D696E20206C6973

> 74207772697465727320202D20557365723A20564D534552565C41646D696E69737472

> 61746F72202020202D205369643A2020532D312D352D32312D31303239333938363433

> 2D3434303331333237312D333337333035313534332D35303020202020</Binary>

> </EventData>

> </Event>

[Guest Mark Murphy]

Re: WBS Backup issues

 

I understand the limuts of pass through and do not expect to back up those

drives. However there seems to be an issue with the writer failing and

disapering. I would expect that there should be a message that pass through

is not supported and not just error out and disapper untill next reboot. If

this is the issue then Microsoft needs to put better error checking and

reporting into there protuct.

 

Thanks for the links.

--

Mark Murphy - MCSE2000

 

 

"Meinolf Weber" wrote:

> Hello Mark,

>

> Have a look at this one about using pass through disk, scroll down to "Storage

> considerations":

> http://blogs.technet.com/virtualization/archive/2008/08/29/backing-up-hyper-v-virtual-machines.aspx

>

> Also see here and search for "pass-through disks":

> http://technet.microsoft.com/en-us/library/cc794762.aspx

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>

> > I am having an issue using WBS on a Hyper-v Host with 4 VM's running

> > on it. Config is as follows

> >

> > 64bit Windows 2008 with Hyper-v role

> > WBS feature is installed.

> > All the latest patchs released to 09/12/2008

> > Including Update for Windows Server 2008 x64 Edition (KB956697)

> >

> > Installation date: ?9/?12/?2008 8:23 PM

> >

> > Installation status: Successful

> >

> > Update type: Recommended

> >

> > Install this update to resolve an issue in which the Hyper-V Volume

> > Shadow Copy Service (VSS) does not back up virtual machines properly.

> > After you install this item, you may have to restart your computer.

> > This update is provided to you and licensed under the Windows Server

> > 2008 License Terms.

> >

> > More information: http://support.microsoft.com/kb/956697

> >

> > Help and Support: http://support.microsoft.com

> >

> > VM's are

> > 1 Windows 2008 DC using a VHD for storage

> > 1 Windows 2008 Web server Ed. using a VHD for storage

> > 1 Windows 2008 Exchange server 2007 using VHD's for storage

> > 1 Windows 2003 SP2 using pass through disks for storage

> > All VM's have the Hyper-v Intagraition tools loaded and the VSS backup

> > option in the VM settings is sellected for all

> >

> > Evertime I reboot the first backup attempt fails and then every backup

> > atempt after reports success. However I do not belive the backups

> > after the first one is using the Hyper-v Writer for VSS Bellow is the

> > steps to show the behavor.

> >

> > Issued command after reboot >> C:\Users\Administrator>vssadmin list

> > writers

> >

> > vssadmin 1.1 - Volume Shadow Copy Service administrative command-line

> > tool © Copyright 2001-2005 Microsoft Corp.

> >

> > Writer name: 'Microsoft Hyper-V VSS Writer'

> > Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

> > Writer Instance Id: {4a8930b1-165d-4f9b-8024-c37961a4b7ce}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'System Writer'

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

> > Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'ASR Writer'

> > Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

> > Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'BITS Writer'

> > Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

> > Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'Registry Writer'

> > Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

> > Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'WMI Writer'

> > Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

> > Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'COM+ REGDB Writer'

> > Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

> > Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'Shadow Copy Optimization Writer'

> > Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

> > Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

> > State: [1] Stable

> > Last error: No error

> > Then:

> > Start the backup and wait for failed job

> > Issued Command as soon as backup failes >>

> > C:\Users\Administrator>vssadmin list writers

> >

> > vssadmin 1.1 - Volume Shadow Copy Service administrative command-line

> > tool © Copyright 2001-2005 Microsoft Corp.

> >

> > Writer name: 'Microsoft Hyper-V VSS Writer'

> > Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

> > Writer Instance Id: {4a8930b1-165d-4f9b-8024-c37961a4b7ce}

> > State: [9] Failed

> > Last error: Not responding

> > Writer name: 'System Writer'

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

> > Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'ASR Writer'

> > Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

> > Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'WMI Writer'

> > Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

> > Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'BITS Writer'

> > Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

> > Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'Shadow Copy Optimization Writer'

> > Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

> > Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'COM+ REGDB Writer'

> > Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

> > Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'Registry Writer'

> > Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

> > Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

> > State: [5] Waiting for completion

> > Last error: No error

> > Issue command about 30 Sec later >> C:\Users\Administrator>vssadmin

> > list writers

> >

> > As you can see the writer is gone.

> >

> > vssadmin 1.1 - Volume Shadow Copy Service administrative command-line

> > tool © Copyright 2001-2005 Microsoft Corp.

> >

> > Writer name: 'System Writer'

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

> > Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'ASR Writer'

> > Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

> > Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'BITS Writer'

> > Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

> > Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'Shadow Copy Optimization Writer'

> > Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

> > Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'COM+ REGDB Writer'

> > Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

> > Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'Registry Writer'

> > Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

> > Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'WMI Writer'

> > Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

> > Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer is gone till next reboot. Backup Jobs kick off and finish

> > succesfully after this but don't think it is getting the benifits of

> > the Hyper-v Writer and don't know constance the VHD's are.

> >

> > This error in the event is also logged.

> >

> > Log Name: Application

> > Source: VSS

> > Date: 9/13/2008 2:39:57 PM

> > Event ID: 12301

> > Task Category: None

> > Level: Error

> > Keywords: Classic

> > User: N/A

> > Computer: vmserv.markandbeth.net

> > Description:

> > Volume Shadow Copy Service error: Writer Microsoft Hyper-V VSS Writer

> > did

> > not respond to a GatherWriterStatus call.

> > Operation:

> > Gather writers' status

> > Executing Asynchronous Operation

> > Context:

> > Current State: GatherWriterStatus

> > Event Xml:

> > <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

> > <System>

> > <Provider Name="VSS" />

> > <EventID Qualifiers="0">12301</EventID>

> > <Level>2</Level>

> > <Task>0</Task>

> > <Keywords>0x80000000000000</Keywords>

> > <TimeCreated SystemTime="2008-09-13T18:39:57.000Z" />

> > <EventRecordID>2505</EventRecordID>

> > <Channel>Application</Channel>

> > <Computer>vmserv.markandbeth.net</Computer>

> > <Security />

> > </System>

> > <EventData>

> > <Data>Microsoft Hyper-V VSS Writer</Data>

> > <Data>

> > Operation:

> > Gather writers' status

> > Executing Asynchronous Operation

> > Context:

> > Current State: GatherWriterStatus</Data>

> > <Binary>2D20436F64653A2042554543584D4C4330303030343630332D2043616C6C3A

> > 2042554543584D4C4330303030343531392D205049443A202030303030333839322D20

> > 5449443A202030303030333830342D20434D443A202076737361646D696E20206C6973

> > 74207772697465727320202D20557365723A20564D534552565C41646D696E69737472

> > 61746F72202020202D205369643A2020532D312D352D32312D31303239333938363433

> > 2D3434303331333237312D333337333035313534332D35303020202020</Binary>

> > </EventData>

> > </Event>

>

>

>

[Guest Mark Murphy]

Re: WBS Backup issues

 

OK I rebooted and turned off the VM with pass through and so far it is

working. I guess the error reporting could be a bit better. I will turn off

the VSS intagration on this VM as I don't care if the pass through disks are

backed up. Hopefully with that option turned off it will work OK. I will let

you know.

 

Thanks for the direction

--

Mark Murphy - MCSE2000

 

 

"Meinolf Weber" wrote:

> Hello Mark,

>

> Have a look at this one about using pass through disk, scroll down to "Storage

> considerations":

> http://blogs.technet.com/virtualization/archive/2008/08/29/backing-up-hyper-v-virtual-machines.aspx

>

> Also see here and search for "pass-through disks":

> http://technet.microsoft.com/en-us/library/cc794762.aspx

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>

> > I am having an issue using WBS on a Hyper-v Host with 4 VM's running

> > on it. Config is as follows

> >

> > 64bit Windows 2008 with Hyper-v role

> > WBS feature is installed.

> > All the latest patchs released to 09/12/2008

> > Including Update for Windows Server 2008 x64 Edition (KB956697)

> >

> > Installation date: ?9/?12/?2008 8:23 PM

> >

> > Installation status: Successful

> >

> > Update type: Recommended

> >

> > Install this update to resolve an issue in which the Hyper-V Volume

> > Shadow Copy Service (VSS) does not back up virtual machines properly.

> > After you install this item, you may have to restart your computer.

> > This update is provided to you and licensed under the Windows Server

> > 2008 License Terms.

> >

> > More information: http://support.microsoft.com/kb/956697

> >

> > Help and Support: http://support.microsoft.com

> >

> > VM's are

> > 1 Windows 2008 DC using a VHD for storage

> > 1 Windows 2008 Web server Ed. using a VHD for storage

> > 1 Windows 2008 Exchange server 2007 using VHD's for storage

> > 1 Windows 2003 SP2 using pass through disks for storage

> > All VM's have the Hyper-v Intagraition tools loaded and the VSS backup

> > option in the VM settings is sellected for all

> >

> > Evertime I reboot the first backup attempt fails and then every backup

> > atempt after reports success. However I do not belive the backups

> > after the first one is using the Hyper-v Writer for VSS Bellow is the

> > steps to show the behavor.

> >

> > Issued command after reboot >> C:\Users\Administrator>vssadmin list

> > writers

> >

> > vssadmin 1.1 - Volume Shadow Copy Service administrative command-line

> > tool © Copyright 2001-2005 Microsoft Corp.

> >

> > Writer name: 'Microsoft Hyper-V VSS Writer'

> > Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

> > Writer Instance Id: {4a8930b1-165d-4f9b-8024-c37961a4b7ce}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'System Writer'

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

> > Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'ASR Writer'

> > Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

> > Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'BITS Writer'

> > Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

> > Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'Registry Writer'

> > Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

> > Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'WMI Writer'

> > Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

> > Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'COM+ REGDB Writer'

> > Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

> > Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'Shadow Copy Optimization Writer'

> > Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

> > Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

> > State: [1] Stable

> > Last error: No error

> > Then:

> > Start the backup and wait for failed job

> > Issued Command as soon as backup failes >>

> > C:\Users\Administrator>vssadmin list writers

> >

> > vssadmin 1.1 - Volume Shadow Copy Service administrative command-line

> > tool © Copyright 2001-2005 Microsoft Corp.

> >

> > Writer name: 'Microsoft Hyper-V VSS Writer'

> > Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

> > Writer Instance Id: {4a8930b1-165d-4f9b-8024-c37961a4b7ce}

> > State: [9] Failed

> > Last error: Not responding

> > Writer name: 'System Writer'

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

> > Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'ASR Writer'

> > Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

> > Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'WMI Writer'

> > Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

> > Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'BITS Writer'

> > Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

> > Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'Shadow Copy Optimization Writer'

> > Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

> > Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'COM+ REGDB Writer'

> > Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

> > Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'Registry Writer'

> > Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

> > Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

> > State: [5] Waiting for completion

> > Last error: No error

> > Issue command about 30 Sec later >> C:\Users\Administrator>vssadmin

> > list writers

> >

> > As you can see the writer is gone.

> >

> > vssadmin 1.1 - Volume Shadow Copy Service administrative command-line

> > tool © Copyright 2001-2005 Microsoft Corp.

> >

> > Writer name: 'System Writer'

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

> > Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'ASR Writer'

> > Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

> > Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'BITS Writer'

> > Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

> > Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'Shadow Copy Optimization Writer'

> > Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

> > Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'COM+ REGDB Writer'

> > Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

> > Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'Registry Writer'

> > Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

> > Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'WMI Writer'

> > Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

> > Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer is gone till next reboot. Backup Jobs kick off and finish

> > succesfully after this but don't think it is getting the benifits of

> > the Hyper-v Writer and don't know constance the VHD's are.

> >

> > This error in the event is also logged.

> >

> > Log Name: Application

> > Source: VSS

> > Date: 9/13/2008 2:39:57 PM

> > Event ID: 12301

> > Task Category: None

> > Level: Error

> > Keywords: Classic

> > User: N/A

> > Computer: vmserv.markandbeth.net

> > Description:

> > Volume Shadow Copy Service error: Writer Microsoft Hyper-V VSS Writer

> > did

> > not respond to a GatherWriterStatus call.

> > Operation:

> > Gather writers' status

> > Executing Asynchronous Operation

> > Context:

> > Current State: GatherWriterStatus

> > Event Xml:

> > <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

> > <System>

> > <Provider Name="VSS" />

> > <EventID Qualifiers="0">12301</EventID>

> > <Level>2</Level>

> > <Task>0</Task>

> > <Keywords>0x80000000000000</Keywords>

> > <TimeCreated SystemTime="2008-09-13T18:39:57.000Z" />

> > <EventRecordID>2505</EventRecordID>

> > <Channel>Application</Channel>

> > <Computer>vmserv.markandbeth.net</Computer>

> > <Security />

> > </System>

> > <EventData>

> > <Data>Microsoft Hyper-V VSS Writer</Data>

> > <Data>

> > Operation:

> > Gather writers' status

> > Executing Asynchronous Operation

> > Context:

> > Current State: GatherWriterStatus</Data>

> > <Binary>2D20436F64653A2042554543584D4C4330303030343630332D2043616C6C3A

> > 2042554543584D4C4330303030343531392D205049443A202030303030333839322D20

> > 5449443A202030303030333830342D20434D443A202076737361646D696E20206C6973

> > 74207772697465727320202D20557365723A20564D534552565C41646D696E69737472

> > 61746F72202020202D205369643A2020532D312D352D32312D31303239333938363433

> > 2D3434303331333237312D333337333035313534332D35303020202020</Binary>

> > </EventData>

> > </Event>

>

>

>

[Guest Mark Murphy]

Re: WBS Backup issues

 

Disabling the VSS intagration on the VM with Pass through disk is now letting

the backups work now. The VM now is saved, VSS snapshots are taken from the

other 3 and then the Passthrough VM starts back up and the backup procedds

with no issues. Microsoft please add better errror checking for this kind of

senaro and have the VSS writer fail more gracfully. Having the VSS writer

fail and drop out till next reboot is not aceptable

 

 

--

Mark Murphy - MCSE2000

 

 

"Meinolf Weber" wrote:

> Hello Mark,

>

> Have a look at this one about using pass through disk, scroll down to "Storage

> considerations":

> http://blogs.technet.com/virtualization/archive/2008/08/29/backing-up-hyper-v-virtual-machines.aspx

>

> Also see here and search for "pass-through disks":

> http://technet.microsoft.com/en-us/library/cc794762.aspx

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>

> > I am having an issue using WBS on a Hyper-v Host with 4 VM's running

> > on it. Config is as follows

> >

> > 64bit Windows 2008 with Hyper-v role

> > WBS feature is installed.

> > All the latest patchs released to 09/12/2008

> > Including Update for Windows Server 2008 x64 Edition (KB956697)

> >

> > Installation date: ?9/?12/?2008 8:23 PM

> >

> > Installation status: Successful

> >

> > Update type: Recommended

> >

> > Install this update to resolve an issue in which the Hyper-V Volume

> > Shadow Copy Service (VSS) does not back up virtual machines properly.

> > After you install this item, you may have to restart your computer.

> > This update is provided to you and licensed under the Windows Server

> > 2008 License Terms.

> >

> > More information: http://support.microsoft.com/kb/956697

> >

> > Help and Support: http://support.microsoft.com

> >

> > VM's are

> > 1 Windows 2008 DC using a VHD for storage

> > 1 Windows 2008 Web server Ed. using a VHD for storage

> > 1 Windows 2008 Exchange server 2007 using VHD's for storage

> > 1 Windows 2003 SP2 using pass through disks for storage

> > All VM's have the Hyper-v Intagraition tools loaded and the VSS backup

> > option in the VM settings is sellected for all

> >

> > Evertime I reboot the first backup attempt fails and then every backup

> > atempt after reports success. However I do not belive the backups

> > after the first one is using the Hyper-v Writer for VSS Bellow is the

> > steps to show the behavor.

> >

> > Issued command after reboot >> C:\Users\Administrator>vssadmin list

> > writers

> >

> > vssadmin 1.1 - Volume Shadow Copy Service administrative command-line

> > tool © Copyright 2001-2005 Microsoft Corp.

> >

> > Writer name: 'Microsoft Hyper-V VSS Writer'

> > Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

> > Writer Instance Id: {4a8930b1-165d-4f9b-8024-c37961a4b7ce}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'System Writer'

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

> > Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'ASR Writer'

> > Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

> > Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'BITS Writer'

> > Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

> > Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'Registry Writer'

> > Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

> > Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'WMI Writer'

> > Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

> > Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'COM+ REGDB Writer'

> > Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

> > Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'Shadow Copy Optimization Writer'

> > Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

> > Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

> > State: [1] Stable

> > Last error: No error

> > Then:

> > Start the backup and wait for failed job

> > Issued Command as soon as backup failes >>

> > C:\Users\Administrator>vssadmin list writers

> >

> > vssadmin 1.1 - Volume Shadow Copy Service administrative command-line

> > tool © Copyright 2001-2005 Microsoft Corp.

> >

> > Writer name: 'Microsoft Hyper-V VSS Writer'

> > Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

> > Writer Instance Id: {4a8930b1-165d-4f9b-8024-c37961a4b7ce}

> > State: [9] Failed

> > Last error: Not responding

> > Writer name: 'System Writer'

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

> > Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'ASR Writer'

> > Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

> > Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'WMI Writer'

> > Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

> > Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'BITS Writer'

> > Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

> > Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'Shadow Copy Optimization Writer'

> > Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

> > Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'COM+ REGDB Writer'

> > Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

> > Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'Registry Writer'

> > Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

> > Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

> > State: [5] Waiting for completion

> > Last error: No error

> > Issue command about 30 Sec later >> C:\Users\Administrator>vssadmin

> > list writers

> >

> > As you can see the writer is gone.

> >

> > vssadmin 1.1 - Volume Shadow Copy Service administrative command-line

> > tool © Copyright 2001-2005 Microsoft Corp.

> >

> > Writer name: 'System Writer'

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

> > Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'ASR Writer'

> > Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

> > Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'BITS Writer'

> > Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

> > Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

> > State: [1] Stable

> > Last error: No error

> > Writer name: 'Shadow Copy Optimization Writer'

> > Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

> > Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'COM+ REGDB Writer'

> > Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

> > Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'Registry Writer'

> > Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

> > Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer name: 'WMI Writer'

> > Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

> > Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

> > State: [5] Waiting for completion

> > Last error: No error

> > Writer is gone till next reboot. Backup Jobs kick off and finish

> > succesfully after this but don't think it is getting the benifits of

> > the Hyper-v Writer and don't know constance the VHD's are.

> >

> > This error in the event is also logged.

> >

> > Log Name: Application

> > Source: VSS

> > Date: 9/13/2008 2:39:57 PM

> > Event ID: 12301

> > Task Category: None

> > Level: Error

> > Keywords: Classic

> > User: N/A

> > Computer: vmserv.markandbeth.net

> > Description:

> > Volume Shadow Copy Service error: Writer Microsoft Hyper-V VSS Writer

> > did

> > not respond to a GatherWriterStatus call.

> > Operation:

> > Gather writers' status

> > Executing Asynchronous Operation

> > Context:

> > Current State: GatherWriterStatus

> > Event Xml:

> > <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

> > <System>

> > <Provider Name="VSS" />

> > <EventID Qualifiers="0">12301</EventID>

> > <Level>2</Level>

> > <Task>0</Task>

> > <Keywords>0x80000000000000</Keywords>

> > <TimeCreated SystemTime="2008-09-13T18:39:57.000Z" />

> > <EventRecordID>2505</EventRecordID>

> > <Channel>Application</Channel>

> > <Computer>vmserv.markandbeth.net</Computer>

> > <Security />

> > </System>

> > <EventData>

> > <Data>Microsoft Hyper-V VSS Writer</Data>

> > <Data>

> > Operation:

> > Gather writers' status

> > Executing Asynchronous Operation

> > Context:

> > Current State: GatherWriterStatus</Data>

> > <Binary>2D20436F64653A2042554543584D4C4330303030343630332D2043616C6C3A

> > 2042554543584D4C4330303030343531392D205049443A202030303030333839322D20

> > 5449443A202030303030333830342D20434D443A202076737361646D696E20206C6973

> > 74207772697465727320202D20557365723A20564D534552565C41646D696E69737472

> > 61746F72202020202D205369643A2020532D312D352D32312D31303239333938363433

> > 2D3434303331333237312D333337333035313534332D35303020202020</Binary>

> > </EventData>

> > </Event>

>

>

>

[Guest Meinolf Weber]

Re: WBS Backup issues

 

Hello Mark,

 

Thanks for the feedback, maybe someone from MS will take care of this. Nice

to hear that you get it running.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> Disabling the VSS intagration on the VM with Pass through disk is now

> letting the backups work now. The VM now is saved, VSS snapshots are

> taken from the other 3 and then the Passthrough VM starts back up and

> the backup procedds with no issues. Microsoft please add better errror

> checking for this kind of senaro and have the VSS writer fail more

> gracfully. Having the VSS writer fail and drop out till next reboot is

> not aceptable

>

> "Meinolf Weber" wrote:

>

>> Hello Mark,

>>

>> Have a look at this one about using pass through disk, scroll down to

>> "Storage considerations":

>> http://blogs.technet.com/virtualization/archive/2008/08/29/backing-up

>> -hyper-v-virtual-machines.aspx

>>

>> Also see here and search for "pass-through disks":

>> http://technet.microsoft.com/en-us/library/cc794762.aspx

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> I am having an issue using WBS on a Hyper-v Host with 4 VM's running

>>> on it. Config is as follows

>>>

>>> 64bit Windows 2008 with Hyper-v role

>>> WBS feature is installed.

>>> All the latest patchs released to 09/12/2008

>>> Including Update for Windows Server 2008 x64 Edition (KB956697)

>>> Installation date: ?9/?12/?2008 8:23 PM

>>>

>>> Installation status: Successful

>>>

>>> Update type: Recommended

>>>

>>> Install this update to resolve an issue in which the Hyper-V Volume

>>> Shadow Copy Service (VSS) does not back up virtual machines

>>> properly. After you install this item, you may have to restart your

>>> computer. This update is provided to you and licensed under the

>>> Windows Server 2008 License Terms.

>>>

>>> More information: http://support.microsoft.com/kb/956697

>>>

>>> Help and Support: http://support.microsoft.com

>>>

>>> VM's are

>>> 1 Windows 2008 DC using a VHD for storage

>>> 1 Windows 2008 Web server Ed. using a VHD for storage

>>> 1 Windows 2008 Exchange server 2007 using VHD's for storage

>>> 1 Windows 2003 SP2 using pass through disks for storage

>>> All VM's have the Hyper-v Intagraition tools loaded and the VSS

>>> backup

>>> option in the VM settings is sellected for all

>>> Evertime I reboot the first backup attempt fails and then every

>>> backup atempt after reports success. However I do not belive the

>>> backups after the first one is using the Hyper-v Writer for VSS

>>> Bellow is the steps to show the behavor.

>>>

>>> Issued command after reboot >> C:\Users\Administrator>vssadmin list

>>> writers

>>>

>>> vssadmin 1.1 - Volume Shadow Copy Service administrative

>>> command-line tool © Copyright 2001-2005 Microsoft Corp.

>>>

>>> Writer name: 'Microsoft Hyper-V VSS Writer'

>>> Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

>>> Writer Instance Id: {4a8930b1-165d-4f9b-8024-c37961a4b7ce}

>>> State: [1] Stable

>>> Last error: No error

>>> Writer name: 'System Writer'

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

>>> Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

>>> State: [1] Stable

>>> Last error: No error

>>> Writer name: 'ASR Writer'

>>> Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

>>> Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

>>> State: [1] Stable

>>> Last error: No error

>>> Writer name: 'BITS Writer'

>>> Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

>>> Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

>>> State: [1] Stable

>>> Last error: No error

>>> Writer name: 'Registry Writer'

>>> Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

>>> Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

>>> State: [1] Stable

>>> Last error: No error

>>> Writer name: 'WMI Writer'

>>> Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

>>> Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

>>> State: [1] Stable

>>> Last error: No error

>>> Writer name: 'COM+ REGDB Writer'

>>> Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

>>> Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

>>> State: [1] Stable

>>> Last error: No error

>>> Writer name: 'Shadow Copy Optimization Writer'

>>> Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

>>> Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

>>> State: [1] Stable

>>> Last error: No error

>>> Then:

>>> Start the backup and wait for failed job

>>> Issued Command as soon as backup failes >>

>>> C:\Users\Administrator>vssadmin list writers

>>> vssadmin 1.1 - Volume Shadow Copy Service administrative

>>> command-line tool © Copyright 2001-2005 Microsoft Corp.

>>>

>>> Writer name: 'Microsoft Hyper-V VSS Writer'

>>> Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

>>> Writer Instance Id: {4a8930b1-165d-4f9b-8024-c37961a4b7ce}

>>> State: [9] Failed

>>> Last error: Not responding

>>> Writer name: 'System Writer'

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

>>> Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

>>> State: [5] Waiting for completion

>>> Last error: No error

>>> Writer name: 'ASR Writer'

>>> Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

>>> Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

>>> State: [5] Waiting for completion

>>> Last error: No error

>>> Writer name: 'WMI Writer'

>>> Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

>>> Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

>>> State: [5] Waiting for completion

>>> Last error: No error

>>> Writer name: 'BITS Writer'

>>> Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

>>> Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

>>> State: [1] Stable

>>> Last error: No error

>>> Writer name: 'Shadow Copy Optimization Writer'

>>> Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

>>> Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

>>> State: [5] Waiting for completion

>>> Last error: No error

>>> Writer name: 'COM+ REGDB Writer'

>>> Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

>>> Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

>>> State: [5] Waiting for completion

>>> Last error: No error

>>> Writer name: 'Registry Writer'

>>> Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

>>> Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

>>> State: [5] Waiting for completion

>>> Last error: No error

>>> Issue command about 30 Sec later >> C:\Users\Administrator>vssadmin

>>> list writers

>>> As you can see the writer is gone.

>>>

>>> vssadmin 1.1 - Volume Shadow Copy Service administrative

>>> command-line tool © Copyright 2001-2005 Microsoft Corp.

>>>

>>> Writer name: 'System Writer'

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

>>> Writer Instance Id: {d5612e86-0374-44cc-957b-b2616e264fee}

>>> State: [5] Waiting for completion

>>> Last error: No error

>>> Writer name: 'ASR Writer'

>>> Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

>>> Writer Instance Id: {a2cd5ee7-6f09-47f8-9afd-fcca429c9bd4}

>>> State: [5] Waiting for completion

>>> Last error: No error

>>> Writer name: 'BITS Writer'

>>> Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

>>> Writer Instance Id: {5752db5d-5d0b-4ae0-be06-971afd4246b9}

>>> State: [1] Stable

>>> Last error: No error

>>> Writer name: 'Shadow Copy Optimization Writer'

>>> Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

>>> Writer Instance Id: {c74edbcd-071e-41bc-bda8-c5911d08f2e6}

>>> State: [5] Waiting for completion

>>> Last error: No error

>>> Writer name: 'COM+ REGDB Writer'

>>> Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

>>> Writer Instance Id: {0655bb31-ca18-45fc-8a55-7fb5267abb08}

>>> State: [5] Waiting for completion

>>> Last error: No error

>>> Writer name: 'Registry Writer'

>>> Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

>>> Writer Instance Id: {48917837-49d4-4d3b-b564-876e3e7eba1c}

>>> State: [5] Waiting for completion

>>> Last error: No error

>>> Writer name: 'WMI Writer'

>>> Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

>>> Writer Instance Id: {ad730ce5-91e5-48d5-8b81-2a86a0aaf2e5}

>>> State: [5] Waiting for completion

>>> Last error: No error

>>> Writer is gone till next reboot. Backup Jobs kick off and finish

>>> succesfully after this but don't think it is getting the benifits of

>>> the Hyper-v Writer and don't know constance the VHD's are.

>>> This error in the event is also logged.

>>>

>>> Log Name: Application

>>> Source: VSS

>>> Date: 9/13/2008 2:39:57 PM

>>> Event ID: 12301

>>> Task Category: None

>>> Level: Error

>>> Keywords: Classic

>>> User: N/A

>>> Computer: vmserv.markandbeth.net

>>> Description:

>>> Volume Shadow Copy Service error: Writer Microsoft Hyper-V VSS

>>> Writer

>>> did

>>> not respond to a GatherWriterStatus call.

>>> Operation:

>>> Gather writers' status

>>> Executing Asynchronous Operation

>>> Context:

>>> Current State: GatherWriterStatus

>>> Event Xml:

>>> <Event

>>> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

>>> <System>

>>> <Provider Name="VSS" />

>>> <EventID Qualifiers="0">12301</EventID>

>>> <Level>2</Level>

>>> <Task>0</Task>

>>> <Keywords>0x80000000000000</Keywords>

>>> <TimeCreated SystemTime="2008-09-13T18:39:57.000Z" />

>>> <EventRecordID>2505</EventRecordID>

>>> <Channel>Application</Channel>

>>> <Computer>vmserv.markandbeth.net</Computer>

>>> <Security />

>>> </System>

>>> <EventData>

>>> <Data>Microsoft Hyper-V VSS Writer</Data>

>>> <Data>

>>> Operation:

>>> Gather writers' status

>>> Executing Asynchronous Operation

>>> Context:

>>> Current State: GatherWriterStatus</Data>

>>> <Binary>2D20436F64653A2042554543584D4C4330303030343630332D2043616C6C

>>> 3A

>>> 2042554543584D4C4330303030343531392D205049443A202030303030333839322D

>>> 20

>>> 5449443A202030303030333830342D20434D443A202076737361646D696E20206C69

>>> 73

>>> 74207772697465727320202D20557365723A20564D534552565C41646D696E697374

>>> 72

>>> 61746F72202020202D205369643A2020532D312D352D32312D313032393339383634

>>> 33

>>> 2D3434303331333237312D333337333035313534332D35303020202020</Binary>

>>> </EventData>

>>> </Event>