Solved

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

Posted on 2011-03-20
12
345 Views
Last Modified: 2012-06-27
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.
0
Comment
Question by:venk_r
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 6
12 Comments
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 35178209
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..
0
 
LVL 8

Author Comment

by:venk_r
ID: 35179487
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?
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 35181074
>> 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
0
Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

 
LVL 8

Author Comment

by:venk_r
ID: 35181207
The database is 600G in size and there is  particlular table which has 2 billion records in it..
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 35182660
Are you sure it is 600GB or 600MB.
If it is 600GB, then its recommended to go with Backup
0
 
LVL 8

Author Comment

by:venk_r
ID: 35184277
its 600GB.
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 35186167
Then initialize with Backup instead of snapshot..
0
 
LVL 8

Author Comment

by:venk_r
ID: 35189464
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?
0
 
LVL 57

Accepted Solution

by:
Raja Jegan R earned 500 total points
ID: 35195949
>> Since its on the same servers

This is what I have understood till now.

1. You have 600GB database replicated to another server
2. You are trying to move Distribution and Subscriber Server databases to a new SAN storage.

If I am correct, then you need to have some downtime to move your Subscriber Server databases (files) completely to the new SAN storage. Once done, you can bring Subscriber up which would automatically catch up.
This method doesn't require any downtime at the Publishing server.

Kindly confirm whether my understanding about your environment is correct or not.
0
 
LVL 8

Author Comment

by:venk_r
ID: 35198372
You got it right on.But how much time can the subscriber/distributor be left offline .Is there any limit?
0
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 35201438
>> 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...
0
 
LVL 8

Author Closing Comment

by:venk_r
ID: 35386058
thanks
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Slowly Changing Dimension Transformation component in data task flow is very useful for us to manage and control how data changes in SSIS.
Load balancing is the method of dividing the total amount of work performed by one computer between two or more computers. Its aim is to get more work done in the same amount of time, ensuring that all the users get served faster.
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question