IBM Support

Backup of Windows System State fails with ANS5283E The operation was unsuccessful.

Troubleshooting


Problem

When running a backup of the Windows system state, the client may state that the snapshot of the system state was successful but the backup fails and logs the message "ANS5283E The operation was unsuccessful."

Symptom

The client schedule log or command line reports messages similar to the following when the backup is attempted:


01/26/2015 17:00:06 Incremental backup of volume 'SYSTEMSTATE'
01/26/2015 17:00:32 ANS1959I Removing previous incomplete group '\System State\0\SystemState' Id:0-348990904
01/26/2015 17:00:32 Backing up object 'ASR Writer' component 'ASR' using shadow copy.
01/26/2015 17:00:32 Backing up object 'ASR Writer' component 'This is the path to the boot BCD store and the boot managers.
All the files in this directory need to be backed up.' using shadow copy.
01/26/2015 17:00:32 Backing up object 'ASR Writer' component 'Select this volume (C:) if it is a critical volume.
Critical volumes are those which ASR must restore.' using shadow copy.
01/26/2015 17:00:32 Backing up object 'ASR Writer' component 'Select to include disk #0 (of signature 0xec0328c2) for ASR restore.' using shadow copy.
01/26/2015 17:00:32 Backing up object 'ASR Writer' component 'Select to include disk #1 (of signature 0xd563576) for ASR restore.' using shadow copy.
01/26/2015 17:00:33 Backing up object 'COM+ REGDB Writer' component 'COM+ REGDB' using shadow copy.
01/26/2015 17:00:33 Backing up object 'Registry Writer' component 'Registry' using shadow copy.
01/26/2015 17:00:33 Backing up object 'System Writer' component 'System Files' using shadow copy.
01/26/2015 17:00:34 Backing up object 'IIS Config Writer' component 'IISCONFIG' using shadow copy.
01/26/2015 17:00:34 Backing up object 'IIS Metabase Writer' component 'IISMETABASE' using shadow copy.
01/26/2015 17:00:34 Backing up object 'NPS VSS Writer' component 'NPS Database' using shadow copy.
01/26/2015 17:00:34 Backing up object 'TS Gateway Writer' component 'TSGComponent' using shadow copy.
01/26/2015 17:00:35 Backing up object 'WMI Writer' component 'Windows Managment Instrumentation' using shadow copy.
01/26/2015 17:00:39 ANS5283E The operation was unsuccessful.
01/26/2015 17:00:39 ANS1228E Sending of object 'TSMCLIENT\SystemState\NULL\System State\SystemState' failed.
01/26/2015 17:00:39 ANS5283E The operation was unsuccessful.

Checking the windows application logs, windows will also report an error:


Error 01/26/2015 5:00:39 PM TsmVssPlugin 4112
None "VSS processing encountered error
'VSS_E_UNEXPECTED_PROVIDER_ERROR'
in the Volume Shadow Copy API 'AddToSnapshotSet'.

Cause

The Windows client system has multiple providers registered.

By default, any software that uses Microsoft Volume Shadow Copy Service will be assigned a VSS provider by the operating system in the following order:

1. Registered vendor hardware provider
2. Registered vendor software provider
3. Microsoft System software provider

This can cause the system to try and take the system state image with a provider other than the Microsoft Shadow Copy provider.

Environment

Windows

Diagnosing The Problem

While logged into the system as an administrator, open a windows command line and issue the command: vssadmin list writers

If the output shows that there are multiple snapshot providers listed, this may cause issues with the system state backup.

For example,

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

Provider name: 'StorageCraft Volume Snapshot Software Provider'
Provider type: Software
Provider Id: {24602736-bed9-4619-91b0-243447c6409c}
Version: 1.0.0.0

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

Resolving The Problem

The vssusesystemprovider option specifies whether to use the Windows system provider, or to let Windows decide the most suitable provider to use.

Set the vssusesystemprovider option to YES to force the use of the Microsoft provider. This can be done by adding the following option to the clients dsm.opt file: vssusesystemprovider yes

[{"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Client","Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Supported Versions","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
17 June 2018

UID

swg21699904