Solved

SMS 2003 and Disaster Recovery Site

Posted on 2008-09-29
9
539 Views
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.

0
Comment
Question by:dgirl365
  • 5
  • 4
9 Comments
 
LVL 8

Expert Comment

by:U_Mansson
ID: 22603049
Hi

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.
0
 

Author Comment

by:dgirl365
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.
0
 
LVL 8

Expert Comment

by:U_Mansson
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.
0
U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

 

Author Comment

by:dgirl365
ID: 22604271
.... I am also guessign I would have to complete some work around AD Sites and Services.
0
 
LVL 8

Expert Comment

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

Author Comment

by:dgirl365
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 ?
0
 

Author Comment

by:dgirl365
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 ?
0
 
LVL 8

Expert Comment

by:U_Mansson
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.
0
 

Accepted Solution

by:
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 !
0

Featured Post

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.

Question has a verified solution.

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

On a regular basis I get questions about slow RDP performance, RDP connection problems, strange errors and even BSOD, remote computers freezing or restarting after initiation of a remote session. In a lot of this cases the quick solutions made b…
Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip is around source server preparation. No migration is an easy migration, there is a…
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.

825 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