Link to home
Start Free TrialLog in
Avatar of venk_r
venk_rFlag for United States of America

asked on

Migrating Distribution DB and the subscriber db to a different SAN.

As part of SAN Migration we have planned to move the distribution db(different server)
and the subsciber db(different server)
to a different SAN. The  publisher is uneffected in this case.
Whats the best approach to perform this task without any downtime.
Just a FYI. Its an  transactional replication setup  with subscriber db  intitalized from backup.
Avatar of Raja Jegan R
Raja Jegan R
Flag of India image

Since its a SAN migration, I hope you need to have some downtime to implement this change..
Since you are trying to do it without downtime in Publisher, you can try this approach.

1. Create a new publication in Source Server
2. Configure your distribution db and Subscriber for this new publication
3. Once everything is synchronized, remove the old publication..
Avatar of venk_r

ASKER

Thanks for the reply.The way we have initially configured subscription is Initialize from the backup and not thru snapshot.Due to this setting I guess we have to stop other services and application pointing to the publisher and then follow the steps that you have mentioned.But I dont want to have downtime on publisher.I thought we had log retention aound 72 hrs on the replication.Can we make use of it?
>> The way we have initially configured subscription is Initialize from the backup and not thru snapshot
>> I thought we had log retention aound 72 hrs on the replication.Can we make use of it?

Kindly let me know your database sizes..
If it is less, then you can re-initialize from snapshot to get it done else go for Backup
Avatar of venk_r

ASKER

The database is 600G in size and there is  particlular table which has 2 billion records in it..
Are you sure it is 600GB or 600MB.
If it is 600GB, then its recommended to go with Backup
Avatar of venk_r

ASKER

its 600GB.
Then initialize with Backup instead of snapshot..
Avatar of venk_r

ASKER

Since its on the same servers .It just moving the database to a different drive I thought we can handle it without creating new set of publications.Wouldnt the TLogs catch up once we bring the distributor and subscriber online?
ASKER CERTIFIED SOLUTION
Avatar of Raja Jegan R
Raja Jegan R
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of venk_r

ASKER

You got it right on.But how much time can the subscriber/distributor be left offline .Is there any limit?
>> But how much time can the subscriber/distributor be left offline .Is there any limit?

Practically speaking there is no limit on that..
No. of transactions hit in the server when we have distributor & subscriber offline is directly proportional to the time taken to get subscriber synchronized...
Avatar of venk_r

ASKER

thanks