April 2, 2014 at 11:26 am
Hello,
We have few different configurations as fat as replication is concerned:
1. Publisher on A, Distributor on B, Subscriber on C - Push and pull both
2. Publisher and distributor on A, subscriber on B - Push
3. Publisher on A, Distributor and Subscriber on B - Pull
Here A, B and C represents different servers or instance.
We have SAN migration taking place. In some cases all A, B and C are migrated the same time.
And there are migration phases where Either ony publisher is migrated on 1 day and distributor is part of other phase.
Regardless, I need to come up with strategy to shut down agents/instances in order to avoid replication failure after SAN migration.
From what I understood, once I stop the log reader agent, I can stop Publisher, subscriber, distributor in thisor any order, it shoudln't break replication.
While bring it back, bring distributor, subscriber and then publisher - logically make sense but not necessary. Also, restart log reader agent after server is brought online.
Does anyone have any insight on how to handle it 'correctly' or 'properly'? Is there any preferred order or way to do maintenance on Publisher, Subscriber and/or distributor server to avoid replication errors?
Only thing keeps me on edge is that in case it fails and we have to resync, it causes 12-14 hours outage which exceeds our curent SLA of max 4 hours maint window or downtime.
I would really appreciate if you have been through this or know what's right vs wrong or preferred vs non-preferred..
Thanks,
A Shah
April 3, 2014 at 4:17 pm
I can't believe I don't get answers in sql server central forums. Hopefully we are not the first shop to go through SAN migration in the environment. This is time sensitive. Any guidance is appreciated.
Aashini
April 3, 2014 at 8:50 pm
If you are simply physically moving the database files from SAN - SAN, it's just a matter or changing the locations via TSQL, shutting down the replication agents as you've already outlined, take the databases offline, COPY (not move) the files, bring the databases back online, start the agents back up. Repeat for each database.
Some things I would do:
1. Check, double-check, triple-check that you are changing the proper paths for each database file
2. Take Full Backups of each DB before the move
3. Move 1 DB at a time, ensuring it comes back online successfully
4. Use a command window and dos commands to perform the copy, do NOT use windows explorer or it will take a lot longer.
5. Make sure that the subscriptions/etc do not expire before the process has completed (depends on the threshold you went with, if default, I believe this is set a 72 hours)
Hope it helps!
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply