SQL server 2005 - database mirroring AND transaction log shipping on the same DB?
I have a database setup with mirroring (high protection mode, no witness server). I would like to setup transaction log shipping to a remote SQL server for the purpose of off-site backup.
Is it even possible to utilize transaction log shipping in a mirrored environment? What happens if the principle server does down and I make the mirror server the principle server?
Also - with transaction log shipping, do I have to worry about identity columns like I'd have to with replication?
Thanks,
-- Jim
Is it even possible to utilize transaction log shipping in a mirrored environment? What happens if the principle server does down and I make the mirror server the principle server?
Also - with transaction log shipping, do I have to worry about identity columns like I'd have to with replication?
Thanks,
-- Jim
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sirees:
Thanks for the help. You didn't mention anything about identity columns in this scenario -- do I have to worry about them?
Thanks for the help. You didn't mention anything about identity columns in this scenario -- do I have to worry about them?
"Typically, when combining log shipping and database mirroring, the mirroring session is established before log shipping, although this is not required. Then the current principal database is configured as the log shipping primary (the principal/primary database), along with one or more remote secondary databases. Also, the mirror database must be configured as a log shipping primary (the mirror/primary database). The log shipping secondary databases should be on different server instances than either the principal/primary server or mirror/primary server. "