7023339: Windows Replications Fail Due to VSS Errors

This document (7023339) is provided subject to the disclaimer at the end of this document.

Environment

PlateSpin Forge 11.x and up

PlateSpin Migrate 12.x and up

PlateSpin Protect 11.x and up

Situation

A replication of a Windows source workload fails with an error message related to VSS or BlockBasedVolumeWrapper.

Resolution

Ensure each drive on the source workload being replicated has at least 10% – 15% free space of the total volume size (Ex: if C: is 100 GB in size, there should be at least 10 GB – 15 GB of free space).
The service Volume Shadow Copy in Services on the source workload should have its startup type set to Manual. The Volume Shadow Copy service should not be disabled.
No other application on the source workload that uses VSS should be running at the time of the replication.
If there is high disk utilization during the time of the replication, the snapshot creation can run into an error. If there is high disk utilization, please schedule the replication to run during a time when the disk is not being used heavily.
In Windows Explorer on the source workload, right click on each drive and choose Configure Shadow Copies.
Look at the settings of each drive. Make sure each drive has the no limit option selected and that the drive selected to store the snapshots has the sufficient space, 10%-15% free space of the total volume size.
Remove all existing shadow copies of each drive on the source. This can be done through the diskshadow utility.
Open a command prompt by right clicking on its icon and choosing run as administrator and run this command.
diskshadow
The diskshadow command line utility will open. Run this command to remove all existing VSS snapshots.
delete shadows all
See this Microsoft document for more information about diskshadow.
Test the creation of shadow copies using “vssadmin create shadow” for each drive; these snapshots can be removed using diskshadow after the snapshots have been taken.
See this Microsoft link for more information about vssadmin.
Test the creation and removal of VSS snapshots using PlateSpin.Athens.SnapshotExecution.exe. See TID 7017929.

Cause

PlateSpin uses the native Windows service Volume Shadow Copy (VSS) to create snapshots of the volumes being replicated. If the snapshots cannot be taken, the job will not complete successfully.

Additional Information

Consult with the system administrator of the source workload before making any changes this TID recommends.

There may be errors related to the creation of VSS snapshots on the source workload’s Event Viewer application and system logs. When submitting a service request, please export those logs as .evtx files and upload them to the service request along with the diagnostics of the failed replication job.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

Re: Inconsistent Shadow Copy with System Writer

Hey guys,

I’m having a problem with one Windows 2012 R2 client running on VMware, backing up with Networker 8.2.3. I’m hoping you guys will be able to straighten me out, I’m about ready to format the server and start over. Here’s the facts and what I’ve done so far.

1) Windows server backup is successful doing a full bare metal backup, therefore I don’t believe VSS is the culprit.

2) Networker reports error:

5388:save: Failure status of writer System Writer – VSS_WS_FAILED_AT_PREPARE_SNAPSHOT

VSS OTHER: ERROR: VSS failed to process snapshot: The shadow-copy set only contains only a subset of the

volumes needed to correctly backup the selected components of the writer. (VSS error 0x800423f0)

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

86024:save: Error occured while saving disaster recovery save sets.

3) After resetting all VSS Writers, rebooting, and performing backup, SYSTEM WRITER reports error:

Writer name: ‘System Writer’

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

Writer Instance Id: {b0094e31-feec-4dec-b372-1d517c14c44b}

State: [8] Failed

Last error: Inconsistent shadow copy

4) No other writers are in error after a Networker backup

5) VSSTRACE reports error during Networker backup

[14:38:33.513 P:03F0 T:044C WRTWRTIC(2600) WRITER] Writer System Writer exposing state<8> failure<0x800423f0>

6) Windows 2012 R2 client is fully patched

7) I’ve tried assigning a drive letter to the system partition on this machine, that did not fix the problem.

8) I tried VSSADMIN DELETE SHADOWS /ALL. This did not fix the issue.

9) I removed the Networker client, deleted all associated directories, and re-installed. This did not fix the issue.

Does anyone have any ideas on what else I can try to resolve this issue before I re-install Windows? I’ve been through about 200 tech articles and EMC user technical questions in this community.

Any help would be appreciated.

Thanks

Joel

Related:

Re: VSS Backups not working after Windows 10 creators update 1709

Hello everyone,

just wondering whether anyone else has experienced problems with Avamar VSS Backups of Windows 10 clients since the creators update (1709) was rolled out.

I have a relatively new Win10 Client. Backups of Filesystem and VSS were working fine until the creators update was installed a couple of weeks ago. Now the VSS backups fail after 30 seconds. This is happening on all Windows 10 clients (Professional) with this update.

Error code is 10007

Filesystem backups are still working fine. But the System State backups are no longer working.

In the logfiles I see this:

2017-11-28 20:00:25 avvss Info <16480>: EFI system detected. ASR BCD will not be included in shadow copy

2017-11-28 20:00:25 avvss Info <19014>: Determining best VSS provider for volume ‘c:’

2017-11-28 20:00:25 avvss Info <40027>: Volume c: will be frozen by ‘Microsoft Software Shadow Copy provider 1.0’ in Snapshot {a38bcfd5-e1d9-4341-aedb-e9f403391672}

2017-11-28 20:00:25 avvss Info <8776>: Freezing volumes now…

2017-11-28 20:00:25 avvss Info <8780>: Creating the shadow copy set (DoSnapshotSet) …

2017-11-28 20:00:28 avvss Error <10975>: ERROR: Selected writer ‘ASR Writer’ is in failed state!

– Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)

– Writer Failure code: 0x800423f0 (Der Schattenkopiesatz enthält nur eine Teilmenge der

Volumes, die für eine ordnungsgemäße Sicherung der ausgewählten

Komponenten des Generators notwendig sind.)

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

– Instance ID: {5ee97a67-801b-4754-ab89-98f2f8d093c5}

2017-11-28 20:00:28 avvss Error <10976>: ERROR: Selected writer ‘ASR Writer’ reported an error!

– Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)

– Writer Failure code: 0x800423f0 (Der Schattenkopiesatz enthält nur eine Teilmenge der

Volumes, die für eine ordnungsgemäße Sicherung der ausgewählten

Komponenten des Generators notwendig sind.)

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

– Instance ID: {5ee97a67-801b-4754-ab89-98f2f8d093c5}

2017-11-28 20:00:28 avvss Error <12077>: VSS returned an error message exiting HR = 0x8000ffff

2017-11-28 20:00:28 avvss Info <0000>: Finished with backup. Performing cleanup.

The text in German above translates to:

The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer

Avamar Version 7.3.1-125 (Server & Client)

I’ve already tried rebooting the clients.

Just after the backup fails, I ran vssadmin list writers. It showed the ASR Writer in a failed state. But after a while the writer returns to a stable state.

Any ideas?

Thanks and regards,

Stephen

Related:

  • No Related Posts

VSS Backups not working after Windows 10 creators update 1709

Hello everyone,

just wondering whether anyone else has experienced problems with Avamar VSS Backups of Windows 10 clients since the creators update (1709) was rolled out.

I have a relatively new Win10 Client. Backups of Filesystem and VSS were working fine until the creators update was installed a couple of weeks ago. Now the VSS backups fail after 30 seconds. This is happening on all Windows 10 clients (Professional) with this update.

Error code is 10007

Filesystem backups are still working fine. But the System State backups are no longer working.

In the logfiles I see this:

2017-11-28 20:00:25 avvss Info <16480>: EFI system detected. ASR BCD will not be included in shadow copy

2017-11-28 20:00:25 avvss Info <19014>: Determining best VSS provider for volume ‘c:’

2017-11-28 20:00:25 avvss Info <40027>: Volume c: will be frozen by ‘Microsoft Software Shadow Copy provider 1.0’ in Snapshot {a38bcfd5-e1d9-4341-aedb-e9f403391672}

2017-11-28 20:00:25 avvss Info <8776>: Freezing volumes now…

2017-11-28 20:00:25 avvss Info <8780>: Creating the shadow copy set (DoSnapshotSet) …

2017-11-28 20:00:28 avvss Error <10975>: ERROR: Selected writer ‘ASR Writer’ is in failed state!

– Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)

– Writer Failure code: 0x800423f0 (Der Schattenkopiesatz enthält nur eine Teilmenge der

Volumes, die für eine ordnungsgemäße Sicherung der ausgewählten

Komponenten des Generators notwendig sind.)

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

– Instance ID: {5ee97a67-801b-4754-ab89-98f2f8d093c5}

2017-11-28 20:00:28 avvss Error <10976>: ERROR: Selected writer ‘ASR Writer’ reported an error!

– Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)

– Writer Failure code: 0x800423f0 (Der Schattenkopiesatz enthält nur eine Teilmenge der

Volumes, die für eine ordnungsgemäße Sicherung der ausgewählten

Komponenten des Generators notwendig sind.)

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

– Instance ID: {5ee97a67-801b-4754-ab89-98f2f8d093c5}

2017-11-28 20:00:28 avvss Error <12077>: VSS returned an error message exiting HR = 0x8000ffff

2017-11-28 20:00:28 avvss Info <0000>: Finished with backup. Performing cleanup.

The text in German above translates to:

The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer

Avamar Version 7.3.1-125 (Server & Client)

I’ve already tried rebooting the clients.

Just after the backup fails, I ran vssadmin list writers. It showed the ASR Writer in a failed state. But after a while the writer returns to a stable state.

Any ideas?

Thanks and regards,

Stephen

Related:

  • No Related Posts

Re: VSS Error ?

5388:save: Failure status of writer System Writer – FAILED_AT_FREEZE

5386:save: VSS failed to take the snapshot

The writer’s timeout expired between the Freeze and Thaw events. (VSS error 0x80043f2)

80517:save Snapshot attempt number 2 of 3 will occur in 10 minutes

VSS OTHER: ERROR: VSS failed to process snapshot: A function call was made when the object was in an incorrect state for that function (VSS error 0x80042301)

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

86024:save: Error occurred while saving disaster recovery save sets.

I can’t figure out why my backup failed with the message above, any suggestion is most appreciated.

Using NetWorker Management version 8.2.0.1 build 479

Related:

Re: Re: SQL Backup Configured as NSRSQLSV suddenly failing – error attached

Your output indicates that the shadow storage is not set up.

Did you look at the event logs, and there were no VSS issues?

On my system, I deleted all my shadows, bit it still shows the shadow storage association:

C:windowssystem32>vssadmin List volumes

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

(C) Copyright 2001-2005 Microsoft Corp.

Volume path: C:

Volume name: \?Volume{1c425a42-db08-11e5-93c5-806e6f6e6963}

C:windowssystem32>vssadmin List shadows

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

(C) Copyright 2001-2005 Microsoft Corp.

No items found that satisfy the query.

C:windowssystem32>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: (C:)\?Volume{1c425a42-db08-11e5-93c5-806e6f6e6963}

Shadow Copy Storage volume: (C:)\?Volume{1c425a42-db08-11e5-93c5-806e6f6e6963}

Used Shadow Copy Storage space: 0 B (0%)

Allocated Shadow Copy Storage space: 0 B (0%)

Maximum Shadow Copy Storage space: 46.576 GB (5%)

Refer to the following article on how to recreate the shadow storage area, and then see that changes the backup results.

https://www.petri.com/forums/forum/server-operating-systems/windows-server-2008-2008-r2/58571-vss-error-0x8004230f-on-a-brand-new-system

Related:

Event ID 1 — Volume Shadow Copy Service Initialization

Event ID 1 — Volume Shadow Copy Service Initialization

Updated: January 27, 2011

Applies To: Windows Server 2008 R2

The Volume Shadow Copy Service (VSS) provides the ability to create a point in time image (shadow copy) of one or more volumes that can be used to perform backups. The service is also used during restores of applications. After the VSS service is initialized, VSS requester applications can perform backups and restores in cooperation with VSS writers that manage application data to be backed up and VSS providers that create and manage shadow copies.

Event Details

Product: Windows Operating System
ID: 1
Source: VSS
Version: 6.1
Symbolic Name: VSS_ERROR_STARTING_SERVICE_CTRL_DISPATCHER
Message: Volume Shadow Copy Service initialization error: the control dispatcher cannot be started [%1]. %2

Resolve
Review Service Control Manager events in Event Viewer and take appropriate action

This event indicates that the Volume Shadow Copy Service (VSS) could not register its dispatcher function with the Service Control Manager during VSS service initialization.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To view the VSS events in the Windows System event log:

  1. Open Event Viewer. Click Start, click Run, type eventvwr.msc, and then click OK. If the User Account Control dialog box appears, ensure that the action it displays is what you want, and then click Continue.
  2. In Event Viewer, expand Windows Logs, and then click System.
  3. To create a filtered view of just the Service Control Manager events, click Action, click Create Custom View, choose By source, and in the Event sources drop-down list, select Service Control Manager, and then click OK.
  4. In Save Filter to Custom View, provide a name and description.
  5. In the left pane, expand Custom View, right-click the name of the custom view that you created, and then click Find.
  6. To find all the Service Control Manager Eventlog Provider events for VSS, in Find what, type: Shadow Copy.
  7. To examine an event, double-click the event, and then click Event Log Online Help for more information about how to resolve the issue.
  8. If you cannot resolve the issue, contact Microsoft Customer Service and Support. For more information, see http://go.microsoft.com/fwlink/?LinkId=102491. You should provide the entire event log message as it appears in the Event Viewer.

Verify

To verify that the Volume Shadow Copy Service (VSS service) is available, perform the following procedure, and then retry the previous Volume Shadow Copy Service (VSS) operation.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the VSS service is available:

  1. Open an elevated Command Prompt window by clicking Start, pointing to All Programs, clicking Accessories, right-clicking Command Prompt, and then clicking Run as administrator.
  2. At the prompt, type: net start vss.
  3. View the text message to verify that the service starts or is already started.

Related Management Information

Volume Shadow Copy Service Initialization

File Services

Related:

Event ID 8225 — Volume Shadow Copy Service Operations

Event ID 8225 — Volume Shadow Copy Service Operations

Updated: January 27, 2011

Applies To: Windows Server 2008 R2

The Volume Shadow Copy Service (VSS) provides the ability to create a point in time image (shadow copy) of one or more volumes that can be used to perform backups. The service is also used during restores of applications.

Event Details

Product: Windows Operating System
ID: 8225
Source: VSS
Version: 6.1
Symbolic Name: VSS_INFO_SHUTDOWN_SIGNAL
Message: The VSS service is shutting down due to shutdown event from the Service Control Manager. %1

Resolve

This is a normal condition. No further action is required.

Related Management Information

Volume Shadow Copy Service Operations

File Services

Related:

Event ID 8228 — Volume Shadow Copy Service Operations

Event ID 8228 — Volume Shadow Copy Service Operations

Updated: January 27, 2011

Applies To: Windows Server 2008 R2

The Volume Shadow Copy Service (VSS) provides the ability to create a point in time image (shadow copy) of one or more volumes that can be used to perform backups. The service is also used during restores of applications.

Event Details

Product: Windows Operating System
ID: 8228
Source: VSS
Version: 6.1
Symbolic Name: VSS_ERROR_IXMLDOMDOCUMENT_PARSEERROR
Message: Fail to parse XML file. Reason %1 Line %2 Position %3 Errorcode %4 Problem text %5 %6

Resolve
Contact the backup software vendor

This event is usually caused by restoring from a backup that was created on a more recent Windows operating system version.

To resolve this issue, contact the backup software vendor for further support.

Verify

To verify that the Volume Shadow Copy Service (VSS) is operating correctly, retry the previous VSS operation.

Related Management Information

Volume Shadow Copy Service Operations

File Services

Related:

Event ID 8220 — Volume Shadow Copy Service Operations

Event ID 8220 — Volume Shadow Copy Service Operations

Updated: January 27, 2011

Applies To: Windows Server 2008 R2

The Volume Shadow Copy Service (VSS) provides the ability to create a point in time image (shadow copy) of one or more volumes that can be used to perform backups. The service is also used during restores of applications.

Event Details

Product: Windows Operating System
ID: 8220
Source: VSS
Version: 6.1
Symbolic Name: VSS_INFO_DELETION_TIMEOUT
Message: Ran out of time while deleting files. %1

Resolve

This is a normal condition. No further action is required.

Related Management Information

Volume Shadow Copy Service Operations

File Services

Related: