Managing Replication and High Availability Scenarios › Prepare the SharePoint Replica Server › Prepare the Replica for Standalone Deployment

Prepare the Replica for Standalone Deployment

SharePoint Servers store configuration and content data. To protect both kinds of data, perform the Replica Server configuration procedure before you run any high availability scenarios in a SharePoint Server standalone deployment. The procedure ensures the Replica is configured identically to the Master.

Standalone deployments are not scalable and cannot join other SharePoint farms. The Replica server is completely independent from the Master. CA ARCserve RHA automatically synchronizes and replicates the content database on the Master. You must maintain and customize the configuration and administration content database on the Replica so that it is identical with the one on the Master before you run an HA scenario.

Note: The configuration and administration content databases are not displayed in Auto-Discovery when creating HA scenarios for SharePoint Server standalone deployment. Only existing web application databases can be discovered and replicated in Assured Recovery scenarios.

Next Steps
Use the SharePoint Products Configuration Wizard to Prepare the Replica

Use the SharePoint Products Configuration Wizard to Prepare the Replica

The following procedure is the recommended method for configuring the Replica server in SharePoint Server standalone deployments. The SharePoint Products Configuration wizard configures the services and service applications automatically on the Replica server and creates a default web application on port 80. Before you begin, go to Microsoft TechNet to read information about how to change the administrative site port. You should also obtain the following information:

• The alternate access mapping and administrative site port from the Master server
• The display names, headers and ports for all web applications created on the Master server
• The names of the content databases for all web applications created on the Master server

Note: Do not perform the "disconnect from farm" procedure to reconfigure SharePoint servers auto-configured as Replicas for use in new CA ARCserve RHA scenarios. Disconnecting an auto-configured Replica can also cause the Master server in the old scenario to disconnect from the farm. Instead, delete the following registry key:

• For SharePoint Server 2007: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDB
• For SharePoint Server 2010: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\Secure\ConfigDB

After you delete the registry key, you may safely perform the disconnect from farm procedure using the Configuration Wizard.

To use the SharePoint Products Configuration Wizard to prepare the Replica

1. On the Replica server, launch the SharePoint Products Configuration Wizard from the Windows Start menu.
2. Complete the wizard screens. After configuration, use the PowerShell or STSADM tool to change the administrative site port on the Replica to match the one on the Master.

   For PowerShell, enter:

   set-SPCentralAdministration -Port <PortNumber>
   

   When you are prompted to confirm the action, press Y for yes.

   

   For STSADM, enter:

   stsadm -o setadminport -port <PortNumber>
   

   The command line interface returns the message, Operation completed successfully.

   

3. Launch SharePoint 2010 Central Administration on the Replica. Click Configure Alternate Access Mappings and then click Edit Public URLs. Change the public URL on the Replica to match the one on the Master.

   

4. Create the web applications on the Replica using the same display names, headers, and ports as the Master.
   1. From SharePoint 2010 Central Administration, click Manage web applications.

   

   1. Click New.
   2. Enter the same display names, headers, and ports used on the Master server to create web applications.
   3. Click Manage content databases.
   4. Click Add a content database.
   5. Enter the same database name for each content database used on the Master server.
5. Create and run your HA scenarios to protect the standalone deployment.

Next Steps:

• Create a SharePoint Server Scenario for Standalone Deployments
• Create a SharePoint Server Scenario for Farm (All in One) Deployments
• Create Multiple Scenarios for Farm (Distributed) Deployments
• How to Run a Scenario or Group