Re: Database Mirroring SQL 2005
- From: "Ayad Shammout" <ashammout1@xxxxxxxxxxx>
- Date: Fri, 14 Sep 2007 09:40:48 -0400
That's normal, because when you restore a db with NORECOVERY option, it
makes the db in restoring mode to allow for mirroring transactions to roll
forward and synchronized on the mirror partner. Once you failover and switch
roles, the db will become online and accessible while the principal db
becomes in Restoring mode to do the mirror partner.
This applies also when you need to restore Transaction Logs backups.
Ayad Shammout
"Tyler McLaughlin" <TylerMcLaughlin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:72C976D8-DC2B-4E55-9FC3-816D49BB8824@xxxxxxxxxxxxxxxx
I'm setting it up using the directions provided by Microsoft @
http://msdn2.microsoft.com/en-us/library/ms189047.aspx
The problem I originally ran into was exactly like the one mentioned in
the
following posting:
http://www.microsoft.com/technet/community/newsgroups/managed/dgbrowser/en-us/default.mspx?&query=mirroring&lang=en&cr=US&guid=&sloc=en-US&dg=microsoft.public.sqlserver.clustering&p=1&tid=95381f96-a34a-4d99-9e31-12719452a11d
I found an article online stating that this can occur of your principle
backup wasn't restored to the mirror server in NO RECOVERY mode. I missed
that step when performing the first restore, so i deleted that database
and
started over using the NO RECOVERY option on the mirror restore.
The problem I've run into now is that after my restore executes and
completes, the database remains in a (Restoring...) state and never
becomes
accessible.
Anyone know what causes this?
Thank you,
- Tyler
.
- Prev by Date: Re: How to install cluster SQL 2000 SP4
- Next by Date: Re: Failover Clustering - Newbie
- Previous by thread: SQL-Server Integration Service erros on a cluster
- Next by thread: 2 instances of SQL Server
- Index(es):
Relevant Pages
|
