Start a Conversation

Unsolved

This post is more than 5 years old

5730

November 20th, 2014 11:00

VSS error 0x8004230e causes backup to fail

Good morning,

I'm hoping someone here has an idea of what's going on with my Networker 8.1.1.2 environment.

After a few months of successful backups, suddenly one of the HP servers I take care of stopped backing up.  Here's the full error:

77259:save: VSS reports adding volume to snapshot set failed for both hardware/software provider.VSS OTHER: ERROR: VSS failed to process snapshot: The given shadow copy provider does not support shadow copying the specified volume. (VSS error 0x8004230e)

90108:save: Unable to save the SYSTEM STATE save sets: cannot create the snapshot.

94693:save: The backup of save set 'D:\' failed.

Concordia:D:\: retried 1 times.

Volume E: is a fat32 partition created by the HP smartstart process that contains the server drivers and software.  I don't need to have it backed up.

The save set is currently set to ALL-NTFS

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{4b23b82c-890a-4acb-852a-77480e67c924}\

Volume path: \\?\Volume{97bc992c-696a-11e3-acd1-806e6f6e6963}\

    Volume name: \\?\Volume{97bc992c-696a-11e3-acd1-806e6f6e6963}\

Volume path: C:\

    Volume name: \\?\Volume{97bc992d-696a-11e3-acd1-806e6f6e6963}\

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

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: 'System Writer'

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

   Writer Instance Id: {970c8b54-0a67-4609-ad24-3ac83ab7da9a}

   State: [1] Stable

   Last error: No error

Writer name: 'ASR Writer'

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

   Writer Instance Id: {b894965f-d989-40d3-bdb2-6bb91d3825dc}

   State: [1] Stable

   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'

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

   Writer Instance Id: {6ae5c776-867b-4898-95bc-471610941f94}

   State: [1] Stable

   Last error: No error

Writer name: 'Registry Writer'

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

   Writer Instance Id: {96e28372-8b50-4992-8d39-02d5d120f580}

   State: [1] Stable

   Last error: No error

Writer name: 'COM+ REGDB Writer'

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

   Writer Instance Id: {f03126c7-a6bf-491a-a539-d53327f9371d}

   State: [1] Stable

   Last error: No error

Writer name: 'BITS Writer'

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

   Writer Instance Id: {253c09a8-64d9-4407-994e-f3c1039e3de7}

   State: [1] Stable

   Last error: No error

Writer name: 'WMI Writer'

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

   Writer Instance Id: {9bea25d7-eba2-492b-98a5-c60f4225f5ab}

   State: [1] Stable

   Last error: No error

Thanks for any help you might be able to provide.

Gabriel

November 20th, 2014 12:00

Oops, it's Win2k8R2.

I'm not familiar with the wbadmin tool, should I find out about it?

155 Posts

November 20th, 2014 12:00

Can you help us with client OS win2k3/2k8? Is it possible for you to take Backup from Native tool(wbadmin)?

2.4K Posts

November 20th, 2014 23:00

As your VSS infrastructure seems to work fine, I expect an issue with ALL-NTFS. It seems that E:\ will be added to the worklist although it is a FAT32 volume. What if you select all save sets except E:\ via the browser?

1.7K Posts

November 21st, 2014 02:00

Hello Gabriel,

I see this as an issue with MS VSS and the FAT partition.


As suggested already, can you try to run a backup with Windows Backup tool and check te results?

I this fails you will need to contact MS or HP, or esle just exclude the E;\ drive.

Thank you,

Carlos

155 Posts

November 21st, 2014 03:00

open run window and type wbadmin.msc, it will open wbadmin management console. If this feature is not installed on your server you will have to add this feature which might require reboot of systm as well. contact windows gouy to help you add this feature in 2k8

1.7K Posts

November 24th, 2014 01:00

Hello Gabriel,

Did you have the chance to try the steps suggested?

What is the current status?

Thank you,

Carlos

November 26th, 2014 10:00

Thanks for your suggestions guys.

bingo, I tried to replace ALL-NTFS with just C: D:, however it still failed with the same error message about E:

Suraj, I get the message "Windows Server Backup is not installed on this computer"

Carlos, I looked into excluding the E drive searching on this forum and I found these registry keys that I modified on the guest system that was failing:

HKLM\System\CurrentControlSet\Control\BackupRestore\FilesNotToBackup and HKLM\System\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot

In each I added a key with the value E:\*.* /s to make VSS leave that directory alone.  I don't know if I only needed one or the other of those commands, but that change has allowed the backups to complete without errors.

Does this seem like a valid long term solution?

155 Posts

November 26th, 2014 21:00

This is not a solution if you are skippping data of Drive from Backup, Is data present in E:\ drive not important for you?

If Windows feature is not installed then please get this feature installed, and try a Backup. May be your Windows support guy will help you in this task.

4 Operator

 • 

1.3K Posts

November 26th, 2014 22:00

I dont think shadow copy is enabled on the E: partition. Go to my computer -> Right click on the E drive -> select properties -> click on the tab "Shadow Copies". If you find that the shadow copy is not enabled for E then get your Windows admin to enable it.

No Events found!

Top