Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 High Availability (2005)
 Mirror failover

Author  Topic 

lluisdelta
Starting Member

9 Posts

Posted - 2008-10-31 : 16:51:38
Hi,

I have 2 SQL 2005 servers working in a mirror config, high protection mode (no witness). As a disaster recovery plan I wanted to make sure the failover will be seamless. I assumed that (principal) was down. Working on (mirror), tried to promote all databases in the mirror with:
ALTER DATABASE <db_name> SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS;
but received an error about the database not being in a state that it can be promoted.

I ended up going to the (principal) and manually failing over databases individually (through SSMS). The test went through, all the services were made available in the (mirror) server. However this doesnt seem like the real test, because in the real world the principal is down and inaccessible.

Any suggestion on a better way to challenge the mirror?

Thanks!

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-10-31 : 18:37:31
If the principal is up, then you want to run this: http://weblogs.sqlteam.com/tarad/archive/2008/05/04/60585.aspx

The principal must be down in order to run the command that you tried, so that's why you got that error.

See this from Books Online:

quote:

FORCE_SERVICE_ALLOW_DATA_LOSS is available only on the mirror server and only under all the following conditions:

The principal server is down.


WITNESS is set to OFF or the witness is connected to the mirror server.



Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

lluisdelta
Starting Member

9 Posts

Posted - 2008-10-31 : 19:55:13
Makes sense. Great!

Thanks for your reply!

Go to Top of Page
   

- Advertisement -