SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Manually failing over a mirror without access to Primary Server


Manually failing over a mirror without access to Primary Server

Author
Message
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (51K reputation)SSC Guru (51K reputation)SSC Guru (51K reputation)SSC Guru (51K reputation)SSC Guru (51K reputation)SSC Guru (51K reputation)SSC Guru (51K reputation)SSC Guru (51K reputation)

Group: General Forum Members
Points: 51743 Visits: 17672
arnipetursson (8/21/2014)
One more question.

If you do not have access to server B beyond db_owner in the database,
how do you ensure that the logins (server principals) are synced?

Curious, how did you manage to implement the mirror session in the first place.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Brandie Tarvin
Brandie Tarvin
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: General Forum Members
Points: 36362 Visits: 9267
happycat59 (8/21/2014)
arnipetursson (8/21/2014)
One more question.

If you do not have access to server B beyond db_owner in the database,
how do you ensure that the logins (server principals) are synced?


As db_owner, you cannot do anything except ask someone else to sort it out (e.g. someone with sysadmin or securityadmin priveleges).
You would already need to be doing that - mirroring does not do anything about logins. Logins are at the server level, database mirroring is at the database level.


I've already provided the server owners with a list of jobs and logins I need created on the server. When I failover, all I have to do then is run the update users proc to resync everything. If some logins don't sync because of different SIDs or other issues, I'm db_owner on those databases, so I can just manually add them to the DB after deleting the orphaned login out of the database.

Of course, keeping up with login changes is my responsiblity. Anytime something gets added or removed, I have to communicate that to the server owners. But that's why we use SQL logins and Windows Groups instead of individual logins. When people leave the company or get newly hired, we just make sure they're part of the proper Windows Groups so there's little back and forth on that particular issue.

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Brandie Tarvin
Brandie Tarvin
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: General Forum Members
Points: 36362 Visits: 9267
Perry Whittle (8/21/2014)
arnipetursson (8/21/2014)
One more question.

If you do not have access to server B beyond db_owner in the database,
how do you ensure that the logins (server principals) are synced?

Curious, how did you manage to implement the mirror session in the first place.


The server owners did it for us. When we get to End of Life, we're going to look for a better solution, but we needed this in a hurry so we were granted limited perms on someone else's server. Of course testing the solution requires the server owners cooperation (which is going to be a pain), but it's better than not having a DR solution at all.

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
SQLisAwE5OmE
SQLisAwE5OmE
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2924 Visits: 3075
Hi Brandie,

"I've created a job to initiate failover of the mirrors in case of database failure"

Do you mind sharing how you setup the job?

Regards,
SQLisAwe5oMe.
Brandie Tarvin
Brandie Tarvin
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: General Forum Members
Points: 36362 Visits: 9267
SQLisAwE5OmE (8/23/2014)
Hi Brandie,

"I've created a job to initiate failover of the mirrors in case of database failure"

Do you mind sharing how you setup the job?


The job I set up is for when I have access to the Data Center and the primary server. It's very simple (with a lot of notes in the job's General tab).


USE master;
GO

ALTER DATABASE DB1 SET PARTNER FAILOVER;
GO

ALTER DATABASE DB2 SET PARTNER FAILOVER;
GO

ALTER DATABASE DB3 SET PARTNER FAILOVER;
GO

ALTER DATABASE DB4 SET PARTNER FAILOVER;
GO

ALTER DATABASE DB5 SET PARTNER FAILOVER;
GO



Then I disabled the job so everyone would know that it shouldn't be run on a schedule and named it "DBA_VendorX_DR_MirrorFailover_Job".

EDIT: I forgot to mention... This vendor uses a table to store path names for reports, files, server and instance names (YAY! Data driven stuff!). So on the DR (secondary) server, I have a job that updates all those keys to point to the DR locations once the mirrors are failed over.

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search