Volume Shadow Copy Services fails, reporting error number 800xxxxx.
There are several causes for Volume Shadow Copy Services failure. They are listed in order of probability:
- Low disk space on a drive with Volume Shadow Copies Services enabled.
- The disk is highly fragmented.
- SQL Server 2000 is installed and one or more databases have a recovery model that is not set to Simple. Windows Small Business Server 2003 Backup can back up a database only if its recovery model is set to Simple.
- An Event Log is larger than 64 megabytes (MB).
- Directory Service Access auditing is enabled.
Use the information in the following sections to determine which of these issues is causing Volume Shadow Copy Services to fail and to correct the failure.
Cause: Low disk space on a drive with Volume Shadow Copies Services enabled.
Solution: Increase the space available on the system drive and on the drive with previous versions (Volume Shadow Copy Services) enabled.
To verify that a drive with Volume Shadow Copies Services enabled has low disk space
Click Start, and then click My Computer.
Click the Shadow Copies tab.
Click the volume that has Shadow Copies enabled, and then click Settings.
In the Storage Area dialog box, click Details, and compare the Used and Maximum Size columns to determine whether disk space is low.
Cause: The disk is highly fragmented.
Solution: Defragment all system hard disks.
Cause: SQL Server 2000 is installed and one or more databases have a recovery model that is not set to Simple. Windows Small Business Server 2003 Backup cannot back up this type of database.
Solution: Set the SQL Server 2000 database recovery model to Simple.
To set the SQL Server 2000 database recovery model to Simple
Open SQL Server Enterprise Manager.
Double-click Microsoft SQL Servers, double-click SQL Server Group, (Local), and then double-click Databases.
Right click each database, choose Properties, and then on the Options tab, under Recovery, set the model to Simple.
For more information about SQL Server database recovery models, see SQL Server Help and search for "recovery model."
Cause: An Event Log is larger than 64 MB.
Solution: Reduce the size of the Event Log to a maximum of 64 MB.
To complete the following procedure, you must be logged on as a member of the Domain Admins security group.
To reduce the size of the Event Log
Click Start, click Administrative Tools, and then click Event Viewer.
In the console tree, click any Event Log that is larger than 64 MB.
On the Action menu, click Properties.
On the General tab, in Maximum log size, specify a log size of 64000 kilobytes or less.
To put the new setting in effect, click Clear Log.
If you want to retain the information currently in the log, click Yes when a message appears asking if you want to save the original log before clearing it, and then click OK.
Cause: Directory Service Access auditing is enabled.
Solution: Disable Directory Service access auditing.
To verify that Directory Service Access auditing is enabled
Click Start, click Run, and then type rsop.msc.
In the details pane, double-click Computer Configuration, double-click Windows Settings, double-click Security Settings, double-click Local Policies, and then double-click Audit Policy.
In the Computer Setting column, verify that it reads either Success or Failure.
If Directory Service Access is not enabled, the entry in the Computer Setting column will read No auditing.
To disable Directory Service access auditing
Click Start, and then click Server Management.
In the console tree, click Advanced Management, and then click Group Policy Management.
Navigate to /Forest/Domains/your domain/Domain Controllers, and then right-click Small Business Server Auditing Policy.
Click Edit to open Group Policy Object Editor.
In Group Policy Object editor, navigate to Computer Configuration/Windows Settings/Security Settings/Local Policies/Audit Policy.
Double-click Audit directory service access.
Clear the Success and Failure boxes if they are checked.
Click Start, click Command Prompt, and then type gpupdate /Force to refresh the policy setting.