SQLblog.com - The SQL Server blog spot on the web - Pitfalls backing up logs on a mirrored SQL2005 database when failing over?

THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | Join | Help

Home

Opml

SQLblog.com - The SQL Server b... » SQL Server » SQL Server » Pitfalls backing up logs on a mirrored SQL2005 database when failing over?

Pitfalls backing up logs on a mirrored SQL2005 database when failing over?

Last post 07-10-2008, 7:27 by Uri Dimant. 1 replies.


	Sort Posts: Previous Next

06-17-2008, 8:40 7339

Halindar
Joined on 06-17-2008
Posts 1

Pitfalls backing up logs on a mirrored SQL2005 database when failing over?

We are running a SQL 2005 database pair where we mirror two databases. I've created back-up jobs that check the mirror role and state of the mirror (from sys.database_mirroring) before running the back-up commands so we don't try to back-up a mirror database or the database when it's not in a synchronized state.

The back-up is written to a network share on the local network so no matter which of the two servers is the prinicpal, the back-up ends up in the same place.

Now I heard some concerns about breaking the log chain when there is a database fail-over. Is there anyone who can highlight the pitfalls we need to consider regarding our back-up and restore scheme in relation to the SQL 2005 mirroring. (Mirroring is synchronus)