SQL Database mirror causing backup exec job to fail

[dave2korg]

All,

I have two SQL 2005 servers that mirror each other, after upgrading these to 2005 and setting up db mirroring (witness server), Veritas fails with the following error.

Click an error below to locate it in the job log
Backup- SQLSERVER2 An unknown or unexpected database error occurred while attempting a DBCC.
The database "SQLDATABASE" cannot be opened. It is acting as a mirror database.
Backup- SQLSERVER2 V-79-57344-33938 -
An error occurred on a query to database SQLDATABASE.
V-79-57344-33938 - The database "SQLDATABASE" cannot be opened. It is acting as a mirror database.

I checked veritas's website which looked to be no help. Does anyone have a solution to this? It's not really a problem, as the database mirror on sqlserver1 is backed up with no problems. If there was a way I could just tell Veritas that its not a problem, and to overlook it....



David McKissic
A+, Net+, i-net+, CCNA, CNE, CNA
Dell, Compaq, IBM, HP
Network Administrator

 

[dave2korg]

Exceptions
Click an exception below to locate it in the job log
Backup- SQLSERVER2 The item SQLSERVER2\SQLDATABASE in use - skipped.




David McKissic
A+, Net+, i-net+, CCNA, CNE, CNA
Dell, Compaq, IBM, HP
Network Administrator

 

[Zelandakh]

David,
Get SQL to drop the DBs to disk (BAK) then have BE drop those to tape. Its faster, safer and you'll find the error goes away, restore is more likely to work and none DR restoring will be a lot quicker.

 

[dave2korg]

is this the only way to solve that error? I would rather have the SQL agent built into Veritas handle this, rather than fetch a .bak file each night.

I have constant data that is added to this database, thats why its mirrored. If I use SQL's db backup i could possibly skip data between the time that it makes the backup to when its backed up by veritas.



David McKissic
A+, Net+, i-net+, CCNA, CNE, CNA
Dell, Compaq, IBM, HP
Network Administrator

 

[steveot]

That error looks like it coming from SQL. What happend when you use SQL to backup the mirror database. Do you get the same error?

 

[steveot]

Also reference

http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx

Important:
Microsoft support policies do not apply to the database mirroring feature in SQL Server 2005. Database mirroring is currently disabled by default, but may be enabled for evaluation purposes only by using trace flag 1400 as a startup parameter. (For more information about trace flags, see Trace Flags (Transact-SQL).) Database mirroring should not be used in production environments, and Microsoft support services will not support databases or applications that use database mirroring. Database mirroring documentation is included in SQL Server 2005 for evaluation purposes only, and the Documentation Policy for SQL Server 2005 Support and Upgrade does not apply to the database mirroring documentation.

So we probably assume Veritas wont support this