This points to the Client Operating System having resource problems as per the following link from IBM:
http://www-01.ibm.com/support/docview.wss?uid=swg21616078
IMPORTANT: The above IBM KBA and below information are provided as a general guidance and Quest Software, are not liable for any problem that arises following Microsoft configuration changes.
You should seek Microsoft expert advice to perform any Microsoft related troubleshooting or configuration change, and we recommend opening a case with Microsoft.
Are you using VSS as the backup job Backup Option as well?
Maybe there isn't enough free disk space for VSS and therefore causes a resource problem too?
Please check the following for troubleshooting VSS issues:
1] Make sure the machine is patched with latest SP and VSS roll-up patches.
2] Check space: 30% free is needed for snapshots.
3] Memory fragmentation is a cause of VSS issues, so reboot if possible.
4] Verify VSS shadow copies are enabled for each of the drives to backup. (My Computer > right click drive > Properties > Shadow Copies).
5] Are there any other backups or applications trying to schedule a snapshot at the same time?
6] Run CHKDSK on each drive with the /f switch to fix any errors on the disk.
7] Make sure that the COM+ Event System service is set to Automatic.
8] Make sure Volume Shadow Copy service is set to Manual.
9] Having the SQL Database residing outside of the SQL Server on an external device can have an impact. Is this how the SQL Server is setup?
10] If we have unwanted shadows left over, then we need to clear them and attempt the backup again, so could you run the following command on the Client:
vssadmin delete shadows
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center