SMS 2003 and Disaster Recovery Site

Posted on 2008-09-29
Last Modified: 2013-11-21
I was wondering if anyone could give me some design advice.

On my production network I have an SMS primary site installed (Site A) and an SMS secondary site (Site B) for SMS.  There are live services with workstations and servers at both sites which require managment via SMS.  

I am looking to implement a DR solution at Site B in the event that Site A is no longer available.  What should I do with my SMS installation ?  I assume that the secondary site will not continue to function correctly without the Primary site in place - eg distribute software, perform workstation builds.  In the event of DR, would I need to build a new primary site or would the secondary site be able to still function ?  I assume if I build a new primary site at Site B, this would cause issues with the existing installation.  What do other people do at their sites ?

Any help would be appreciated.

Question by:dgirl365
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
  • 5
  • 4

Expert Comment

ID: 22603049

Your secondary site will not continue to work as you already guessed, because it depends on the primary site. A secondary site doesn't have its own database, it is using the primary sites database.

What you have to do is uninstall the secondary site and install a new primary site and set it as a child to your Site A.

Author Comment

ID: 22604171
Thanks for the reply.  I guessed as much !!!

I wanted to ask if the following was an option :

The Primary site SMS server is a Virtual Server.  I intend to use Site Recovery Manager which will essentially replicate the server over to Site B.  In the event of a DR situation, could I change the IP address of the primary site SMS server to match site B network topology and amend DNS to reflect new IP ?  My primary site boundary is set by Type Active Directory, which would be available at Site B.

I know this may all sound too simple but if there is a simpler solution then installing a new primary site, that would be easier for me, especially with the ability to replicate my servers across the network.

Expert Comment

ID: 22604219
The problem is still that Site B is a secondary site and depend on Site A so I must say, no thats not an option.

I would install a new primare site side by side to the secondary. Move the site boundaries to the new primary site. Just make sure to remove the boundaries from the secondary site!
Then assign the clients to that site and finally connect it as an child primary to Site A. After that, remove the secondary site.
Free NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.


Author Comment

ID: 22604271
.... I am also guessign I would have to complete some work around AD Sites and Services.

Expert Comment

ID: 22604740
Yes, either that or use IP boundaries if you don't want to create another AD site for the remote office

Author Comment

ID: 22632407
What if Site A Primary site server is not available in the event of DR ?  Will I still be able to install a new site at Site B ?

Author Comment

ID: 22632531
or .... what If I unistall Site B secondary install and make site A primary the SMS server for both Site A and Site B by adding the Site B into my Site Boundary ?

Expert Comment

ID: 22635061
On the first question., yes. You first install a new primare site and after the installation is done you attach it to either a parent och child site.

second question...I'm not sure I understand the question.

Accepted Solution

dgirl365 earned 0 total points
ID: 23690312
Just to give an update on this.

I copied the virtual SMS server to my new infrastructure.  I did the follwing :

Changed the IP address of the primary SMS server I had copied
Updated DNS with the new IP Address for the primary SMS server
Changed the subnets in AD Sites and Services to include the new subnet at my Primary site
Added the secondary site to my primary site as a site to be served.  

After a couple of reboots - this has worked perfectly.  No need for uninstalls !

Featured Post

Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

Question has a verified solution.

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

Every system administrator encounters once in while in a problem where the solution seems to be a needle in haystack.  My needle was an anti-virus version causing problems with my Exchange server. I have an HP DL350 with Windows Server 2008 Stand…
Have you considered what group policies are backwards and forwards compatible? Windows Active Directory servers and clients use group policy templates to deploy sets of policies within your domain. But, there is a catch to deploying policies. The…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor ( Top Charts is a view in which you can set seve…

726 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