High level steps involved in the failover from Production to DR

1. Once all the transaction logs have been applied the Databases on DR the attaching of those databases to SharePoint can begin
   
2. Stsadm can be used to attach the databases on DR to the pre-created web applications that have the same settings as Production
   
3. The DNS AHOST records and Load Balancer can be reconfigured to point to the DR SharePoint farm
   
   1. DNS - Reconfigured to associate production DNS AHOST records IP addresses of DR Load Balancer
      
   2. DR Load Balancer - Reconfigured to route requests for web applications to Application and WFE Servers on DR
      
4. Alter the AAM of all the Web Applications on DR to the same settings as Production
   

e.g. For the BGE Portal and BGE My Sites

1. BGE Portal (1 AAM for Intranet Zone)
   

   Internal URL: http://bgeportal Public URL: http://bgeportal]
   

2. BGE MySites (1 AAM for Intranet Zone)
   

   Internal URL: http://bgemysite Public URL: http://bgemysite]
   

 

Once these steps have been completed the web applications should be accessible on the same URLs on DR.

 

Note: The Central Administration site and SSP web application are not included in these steps. The Central Administration site on DR is separate from Production i.e. there are separate farms using separate configuration databases. Any settings on the Central Administration Site on Production will have to be replicated on DR and this is a manual step so all changes made to central Administration will need to be documented and reapplied

 

Note: The SSP on DR will be configured to index the production URLs so in the event of a DR the search index will not have to be rebuilt. If changes are made to the SSP on Production they will need to be replicated to the DR SSP, alternatively, when the Production SSP is configured it can be backed up and restored to DR where it can be configured as the default SSP and therefore have an identical configuration as production. Any subsequent changes to production will have to be replicated on DR.

 

Note: All configuration settings and solutions on the Production environment will need to be deployed on the DR environment. This includes all customisations for systems designed by PM Centrix and all third party components such as those from the following vendors.

• Bamboo Solutions
  
• KWizCom
  

 

Note: The majority of the steps involved in the reconfiguration of SharePoint can be scripted to minimise the amount of time required to get the system up and running on the DR environment.