Errors on SQL2005 box when backing up the OS System State

Question

Errors on SQL2005 box when backing up the OS System State

Marti Ryan

Ten Centuries

Points: 1058
More actions
June 8, 2006 at 6:20 am

#114013

Good morning all! I really hope someone else out there has experienced and resolved this issue. I have SQL2005 Enterprise installed on a Win2003 machine. Each morning at 5am, a Veritas v9.1 System State backup is scheduled and runs thowing a 'host' of errors in the Event log:
BACKUP failed to complete the command BACKUP DATABASE ADWorks_dbsnapshot_0930. Check the backup application log for detailed messages.
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3002
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: Cannot BACKUP or RESTORE a database snapshot.
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=3024. Thread=3200. Client. Instance=. VD=Global\{AC68674B-2542-4096-98EB-7B302330CD11}1.
BackupVirtualDeviceFile:: PrepareToFreeze: failure on backup device '{AC68674B-2542-4096-98EB-7B302330CD11}1'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3202
Error state: 2, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: Write on "{AC68674B-2542-4096-98EB-7B302330CD11}3" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)
Any help would be Greatly appreciated!
-Marti

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

peterhe SSChampion Points: 11469 More actions · Answer 1

From the error message, database ADWorks_dbsnapshot_0930 is a database snapshot. Database snapshot cannot be backed up.

you can filter out database snapshots in your scheduled backup task. For database snapshot, the source_database_id in sys.database is not null.

SELECT * FROM sys.databases where source_database_id IS NULL

Marti Ryan Ten Centuries Points: 1058 More actions · Answer 2

OK - I feel a little 'silly' but I think I have resolved the issue: that dang SNAPSHOT backup.

Here's the test:

1. Create dbsnapshot on database = Will

2. Execute system state backup (NTBackup)

3. Event log errors occur

4. Drop the dbsnapshot on database = Will

5. Execute system state backup (NTBackup)

6. Event log errors are not present

Microsoft tells us to drop all existing dbsnapshot backups prior to executing a FULL db backup. I suspect the VSS errors and the open thread errors were precisely what they said they were, since the snapshot.mdf file has to be open for changes, right?

So 50 cents worth of 'free advice' : if you have a testing environment, you should drop your snapshots BEFORE running an NT system state backup.

I hope my head scratching helps someone out there!

-Marti

Marti Ryan Ten Centuries Points: 1058 More actions · Answer 3

Thanks peter - I only saw your post after I was finished 'kicking' myself...

-Marti