Article ID: 828481
Article Last Modified on 12/3/2007
APPLIES TO
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Small Business Server 2003 Premium Edition
SYMPTOMS
When you back up data from a volume by using the Backup program in Microsoft Windows Server 2003, the following information appears in the backup log file:
Therefore, you cannot use Backup to perform a Volume Shadow Copy service backup of data from the volume.
Additionally, the following event may appear in the Application Event log:
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 6004
Date: DATE
Time: TIME
User: N/A
Computer: COMPUTERNAME
Description: Sqllib error: Database database name is not simple. For more information, see Help and Support Center at http://support.microsoft.com.
Data:
0000: 53 51 4c 53 4e 41 50 43 SQLSNAPC
0008: 33 39 37 00 00 00 00 00 397.....
0010: 53 51 4c 53 4e 41 50 43 SQLSNAPC
0018: 32 39 37 00 00 00 00 00 297.....
CAUSE
This problem occurs when the following conditions are true:
- You back up data from a volume that contains a Microsoft SQL Server database.
- The recovery model of the SQL Server database is configured to use an option that is different from Simple.
Note This problem occurs even when you do not back up any SQL Server database information.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
No prerequisites are required.
Restart requirement
You must restart your computer to apply the changes after you install this hotfix. However, you do not have to restart your computer immediately after you install this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003, 32-bit editions
Date Time Version Size File name -------------------------------------------------------------- 07-Nov-2003 13:36 5.2.3790.99 1,170,432 Ntbackup.exe 06-Nov-2003 09:51 5.2.3790.101 30,720 Ws03res.dll
Windows Server 2003, 64-bit edition
Date Time Version Size File name Platform ----------------------------------------------------------------------- 03-Nov-2003 14:48 5.2.3790.99 3,337,216 Ntbackup.exe IA-64 06-Nov-2003 09:51 5.2.3790.101 30,208 Ws03res.dll IA-64 06-Nov-2003 09:51 5.2.3790.101 30,720 Wws03res.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
MORE INFORMATION
After you install this hotfix, you can use Backup to perform a Volume Shadow Copy service backup of the non-SQL Server data from a volume that contains a SQL Server database. This hotfix prevents Windows Backup from reverting to non-shadow copy backup mode when it encounters a SQL database with a recovery model that is not set to Simple. This hotfix does not let Windows Backup perform a Volume Shadow Copy service backup of a SQL Server database with a recovery model that is set to Full or Bulk-Logged. You must use the SQL Server backup procedure to back up your SQL Server databases that have a recovery model that is set to Full or Bulk-Logged. Additionally, when you use Backup to back up information from a volume that contains a SQL Server database file in non-simple recovery mode, the following information appears in the backup log file:
The following warning will be logged in the application event log:
Event Type: Warning
Event Source: NTBackup
Event Category: None
Event ID: 900
Date: <DATE>
Time:
User: N/A
Computer: COMPUTERNAME
Description: MSDEWriter has reported a VSS error. NtBackup does not support backing up SQL databases which are configured in non-simple recovery mode. If the database has been backed up, it is likely corrupted. Please do not restore this database. The recommended way of backing up non-simple SQL database is to use the backup solution that comes with SQL Server.
This log file information is intended to notify you that you must use the SQL Server backup procedure to back up your SQL Server database files. All non-SQL Server data is backed up by using the Volume Shadow Copy service.
Using SQL Server 2000 backup
- Start SQL Server Enterprise Manager.
- Double-click Microsoft SQL Servers, double-click SQL Server Group, (Local), and then double-click Databases.
- Right-click each database, point to All Tasks, and then click Backup Database.
- In the Name box, type the backup set name. Alternatively, in the Description box, type a description of the backup set.
- Under Backup, click Database - complete.
- Under Destination, click Tape or click Disk, and then specify a backup destination. If no backup destinations appear, click Add to add an existing destination or to create a new one.
- Under Overwrite, use one of the following procedures:
- Click Append to media to append the backup to any existing backups on the backup device.
- Click Overwrite existing media to overwrite any existing backups on the backup device.
- Alternatively, click to select the Schedule check box to schedule the backup operation for later or for periodic execution.
- Alternatively, click the Options tab and do one or more of the following:
- Click to select the Verify backup upon completion check box to cause the backup to be verified when it is backed up.
- Click to select the Eject tape after backup check box to cause the tape to be ejected when the backup operation has completed.
Note This option is available only with tape devices.
- Click to select the Check media set name and backup set expiration check box to cause the backup media to be checked. Doing this prevents accidental overwrites.
- In the Media set name text box, type the name of the media that is to be used for the backup operation. Leave this text box blank when specifying only the backup set expiration.
- If it is the first use of the backup media, or if you want to change an existing media label, under Media set labels, click to select the Initialize and label media check box, and then type the Media set name and Media set description. The media can be initialized and labeled only when overwriting the media.
For more information about SQL Server database recovery models, see SQL Server Help and search for "recovery model."
If you want to convert your SQL Server databases to Simple recovery model to let the Volume Shadow Copy service to back them up, follow these steps.
Setting the SQL Server 2000 database recovery model to Simple
- Start SQL Server Enterprise Manager.
- Double-click Microsoft SQL Servers, double-click SQL Server Group, (Local), and then double-click Databases.
- Right-click each database, and then click Properties.
- Click the Options tab.
- Under Recovery, set the model to Simple.
If you are using the Simple Recovery model, and you want more frequent backups of your SQL data, you can perform differential backups with your regular backups.
Creating a differential database backup
- Expand a server group, and then expand a server.
- Expand Databases, right-click the database, point to All Tasks, and then click Backup Database.
- In the Name text box, type the backup set name. Alternatively, in the Description text box, type a description of the backup set.
- Under Backup, click Database - differential.
- Under Destination, click Tape or click Disk, and then specify a backup destination. If no backup destinations appear, click Add to add an existing backup device or to create a new one.
- Under Overwrite, use one of the following procedures:
- Click Append to media to append the backup to any existing backups on the backup device.
- Click Overwrite existing media to overwrite any existing backups on the backup device.
- Alternatively, click to select the Schedule check box to schedule the backup operation for later or periodic execution.
- Alternatively, click the Options tab, and then take one or more of the following actions:
- Click to select the Verify backup upon completion check box to cause the backup to be verified when backed up.
- Click to select the Eject tape after backup check box to cause the tape to be ejected when the backup operation has completed.
Note This option is only available with tape devices.
- Click to select the Check media set name and backup set expiration check box to cause the backup media to be checked. Doing this prevents accidental overwrites.
- In the Media set name text box, type the name of the media that is to be used for the backup operation. Leave this text box blank when specifying only the backup set expiration.
- If it is the first use of the backup media, or if you want to change an existing media label, under Media set labels, click to select the Initialize and label media check box, and then type the Media set name and Media set description. The media can be initialized and labeled only when overwriting the media.
For more information about SQL Server database recovery models, see SQL Server Help and search for "recovery model."
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional query words: VSS
Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe kbwinserv2003presp1fix KB828481
