Troubleshooting
Problem
Backup performing snapshot backup fails with ANS1327 and return code 653, ANS1377E may also be logged.
Symptom
The dsmerror.log will show the following errors:
01/06/2014 11:26:55 ANS1327W The snapshot operation for 'h:\volid4' failed with error code: 653.
01/06/2014 11:26:55 ANS2698E Snapshot operation failed.
...
01/06/2014 11:35:27 ANS1377W The client was unable to obtain a snapshot of '\\testhost1\t$'. The operation will continue without snapshot support.
Cause
The VSS_E_MAXIMUM_NUMBER_OF_VOLUMES_REACHED error in the trace shows that the limit of 64 shadow copied volumes in a single shadow copy set has been reached.
The maximum number of shadow copied volumes in a single shadow copy set is 64, this is documented by Microsoft at this link:
http://msdn.microsoft.com/en-us/library/aa382650%28v=vs.85%29.aspx
Diagnosing The Problem
Generate a trace using the SERVICE trace flag, review the trace for the following:
01/06/2014 11:26:55.377 [611040] [402692] : DVssSnapshot.cpp ( 928): DVssSnapshot::initializeSnapshot(): VSS[AddToSnapshotSet]: add volume 'h:\undo\' to snapshot set '{909a9fc9-3fbb-4b1c-ad58-0bca36af5183}'
01/06/2014 11:26:55.382 [611040] [402692] : DVssSnapshot.cpp (1864): DVssSnapshot::initializeSnapshot(): VSS[AddToSnapshotSet: VSS_E_MAXIMUM_NUMBER_OF_VOLUMES_REACHED (See the Microsoft Application event log for additional VSS messages).
The command used to enumerate the volume shadow copies on a mounted volume is:
vssadmin list shadows /for=:
For example, to list the shadow copies for the D drive:
vssadmin list shadows /for=d:
Resolving The Problem
As this is a Microsoft limitation, backups will need to be split up into portions of 63 (or less) filesystems in a single schedule.
Product Synonym
TSM
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21661854