VSS SYSTEM FILESET backup failure

Hi,

never met Hyper-V, but is VSS enabled after all in OS?

Regards,

AM

Hi there,

We should some more information such as:

1.- What are you backing up in hte Hyper-V Server?

2.- Which VSS providers do you have in place? Please run the following command and attach the output:

vssadmin list providers

And also:

vssamdin list writers

Thant error message indicates:

0x8004232C

The specified volume is nested too deeply to  participate in the VSS operation.

Also please run the following commands:

vssadmin list volumes

vssdminlist shadows

vassdmin list shadowstorage

Thank you.

Carlos.

Thanks guys for the replied.

Hi Carlos,

Below is the output, please take a look

This is what we backup in saveset

D:\Backup
VSS OTHER:\
VSS SYSTEM BOOT:\
VSS SYSTEM FILESET:\
VSS SYSTEM SERVICES:\
VSS USER DATA:\

C:\>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {8d5c3f6b-67d2-4a2d-a21d-470cee74c7e6}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {55afdb95-55a6-448f-a7eb-cf27e05e785f}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {67aaf0d4-6206-4946-a639-b1086bcdef57}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {c9d453a9-b326-4505-a04c-66f5751910af}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {67a29784-4f0c-4284-a228-cbb58864ffa1}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {cded336f-be59-4595-8a57-25dd79a51a22}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {c27912ef-2847-47a1-8563-15c3395d38a8}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {9261d9f9-8973-4cdd-bae1-7ad0edcc2f1a}
   State: [1] Stable
   Last error: No error

C:\>vssadmin list volumes
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Volume path: D:\
    Volume name: \\?\Volume{9e4b1f0d-a060-11df-9467-806e6f6e6963}\
Volume path: E:\
    Volume name: \\?\Volume{b46c93f6-9fd1-11df-aa15-002655d79667}\
Volume path: C:\
    Volume name: \\?\Volume{9e4b1f12-a060-11df-9467-806e6f6e6963}\

C:\>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Contents of shadow copy set ID: {b59d11f9-8197-4ab8-adae-74f12ce28d5c}
   Contained 1 shadow copies at creation time: 3/29/2011 5:13:46 PM
      Shadow Copy ID: {5fa281e5-f0f5-4693-9358-d2e8227a91e9}
         Original Volume: (C:)\\?\Volume{9e4b1f12-a060-11df-9467-806e6f6e6963}\
         Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
         Originating Machine: abc.com
         Service Machine: abc.com
         Provider: 'Microsoft Software Shadow Copy provider 1.0'
         Type: DataVolumeRollback
         Attributes: Persistent, No auto release, No writers, Differential

Contents of shadow copy set ID: {97ad71c6-bb98-4bec-af77-6a6b4be48d4c}
   Contained 1 shadow copies at creation time: 3/29/2011 5:35:31 PM
      Shadow Copy ID: {cffc6cf4-9483-43ae-974d-7fe7cf554da5}
         Original Volume: (C:)\\?\Volume{9e4b1f12-a060-11df-9467-806e6f6e6963}\
         Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2
         Originating Machine: abc.com
         Service Machine: abc.com
         Provider: 'Microsoft Software Shadow Copy provider 1.0'
         Type: DataVolumeRollback
         Attributes: Persistent, No auto release, No writers, Differential

C:\>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Shadow Copy Storage association
   For volume: (D:)\\?\Volume{9e4b1f0d-a060-11df-9467-806e6f6e6963}\
   Shadow Copy Storage volume: (D:)\\?\Volume{9e4b1f0d-a060-11df-9467-806e6f6e6963}\
   Used Shadow Copy Storage space: 0 B (0%)
   Allocated Shadow Copy Storage space: 0 B (0%)
   Maximum Shadow Copy Storage space: 167.619 GB (10%)

Shadow Copy Storage association
   For volume: (C:)\\?\Volume{9e4b1f12-a060-11df-9467-806e6f6e6963}\
   Shadow Copy Storage volume: (C:)\\?\Volume{9e4b1f12-a060-11df-9467-806e6f6e6963}\
   Used Shadow Copy Storage space: 3.425 GB (9%)
   Allocated Shadow Copy Storage space: 3.898 GB (10%)
   Maximum Shadow Copy Storage space: 10.799 GB (30%)

Hi,

The output of the commands looks good to me, I believe that this could be caused by different reasons, however please let me know the following:

1.- Is D:\ hosting any VHD? (Disk of the Virtual Machines hosted by the Hyper-V Server)

2.- Can you please check the Application and System event logs?

This looks to me as a possible VSS issue, in particular looks like VSS is not able to retrieve all the files being hosted in D:\, that's why I was asking about D:\ hosting any VHD.

Please see the Application and System event logs on the Hyper-V server and you will find more information.

Thank you.

Carlos.

Hi Carlos,

Yes, there is VHD folder in D:\ .

And I found some VSS related info in the application log about "The VSS service is shutting down due to idle timeout."

Any clue?

Thanks.

Hi,

That message about VSS is normal, don't worry about it.

Have you tried Windows bakcup? Maybe that could give us more information.

Thank you.

Carlos.

Client Save Sets:-

SYSTEM STATE:\
SYSTEM FILES:\
SYSTEM DB:\

Save operations :- VSS:*=off

Try to fire VSS backup using networker VSS facility

mark command as VSS*=off

put the VSS mount points in to save sets

It looks as you have hit some limit there.  As per http://technet.microsoft.com/nl-nl/library/ee692290(WS.10).aspx:

0x8004232C The specified volume is nested too deeply to participate in the VSS operation.

I never saw this one and I'm not sure what to make out of it as http://msdn.microsoft.com/en-us/library/aa819453(v=vs.85).aspx suggests this return code is not supported (and obviously you're getting one).

I did find on http://pul.se/Blog-Post-New-SCVMM-VMM-2008-R2-rollup-September-2010_SharePoint-fo9CGyzpirt,65uben3DwcmE following though:

Consider the following scenario: You install the Hyper-V role on a computer that is running Windows Server 2008 R2. You configure the computer to start from a virtual hard disk. The computer is part of a Hyper-V failover cluster. The cluster is configured to use cluster shared volumes. You try to create a VM on a cluster shared volume by using SCVMM 2008 R2. In this scenario, the operation fails together with the 2912 (0x8004232C) error code.

Inside last link there are several patches/rollups listed.  Good luck.