Disaster Recovery - How To

Topics | How To | Related Topics

Recover the CommNet Server in the Event of a Disaster

Recover the CommNet Agent in the Event of a Disaster

Change the IP Address of the CommNet Server

Building a Standby CommNet Server Using Log Shipping

Recover the CommNet Server in the Event of a Disaster

The following procedures assume that you have planned for disaster recovery as described in Planning for Disaster Recovery of the CommNet Server.

Required Capability: See Capabilities and Permitted Actions

To recover the CommNet Server computer:

Use the following procedure to recover the CommNet Server to the same computer or to a different computer.

  1. Rebuild the CommNet Server computer.
    It is NOT necessary to install all these components in the same drives and folders in which they were previously installed.
  2. From the CommNet Server computer, Stop CommNet Server Services.
  3. From the CommCell Console, restore the CommNet Server database to the same location from which it was backed up.
  4. From the CommNet Server computer, Start CommNet Server Services.
  5. If the software is restored to another computer or to the same computer with a new name, perform the following steps on all the CommCells that were registered in this CommNet Server:
  6. Synchronize the CommCell in the CommNet Browser to obtain up-to-date information about the CommCell.

To recover the CommNet Server in a Computer with the CommNet Agent:

Use the following procedure to recover the CommNet Server with the CommNet Agent to the same computer or to a different computer.

  1. Rebuild the computer as described in CommServe Disaster Recovery documentation.
  2. Install the CommNet Server software.
  3. Install the for SQL Server Agent in the CommCell in which it was previously installed.
    It is NOT necessary to install all these components in the same drives and folders in which they were previously installed.
  4. Follow the procedure above To recover the CommNet Server computer.

To recover the CommNet Server database:

Use the following procedure to recover only the CommNet Server database:

  1. If necessary install the CommNet Server software.
  2. From the CommNet Server computer, Stop CommNet Server Services.
  3. From the CommCell Console, restore the CommNet Server database to the same location from which it was backed up.
  4. From the CommNet Server computer, Start CommNet Server Services.
  5. If necessary, synchronize the CommCell in the CommNet Browser to obtain up-to-date information about the CommCell.

Recover the CommNet Agent in the Event of a Disaster

Before You Begin

The following procedure assumes that you have planned for disaster recovery as described in Planning for Disaster Recovery of the CommNet Server.

Required Capability: See Capabilities and Permitted Actions

To recover the CommNet Agent:

  1. Rebuild the CommCell as described in the documentation.
  2. Install the CommNet Agent.
  3. Re-register the CommCell in the CommNet Browser.

Change the IP Address of the CommNet Server

If the IP Address of the CommNet Server has changed, intentionally, or as a result of disaster recovery, the CommNet Server license must reconfigured.

Required Capability: See Capabilities and Permitted Actions

To change the IP Address of the CommNet Server::

  1. Change the IP Address of the CommNet Server, if it has not already changed.
  2. Start the CommNet Browser.
  3. From the Setup menu, click License Administration.
  4. A new license must be assigned to the CommNet Server. Contact your software provider's Customer Support if you do not have an available license. Once you've obtained a new license from your software provider, you can activate the license using the instructions described in Add New Licenses.

Building a Standby CommNet Server Using Log Shipping

If the CommNet Server is installed in the primary production environment, a standby CommNet Server can be built as described in the following sections.

Requirements

Review the following requirements before setting up the primary and standby CommNet Server and the Microsoft SQL Server Database Engine on separate computers:

 

Procedure

Setting up the Primary CommNet Server
1. Install the CommNet Server software on the primary CommNet Server computer. See Deployment - CommNet Server, for more information.
2. Install the SQL Server iDataAgent on the primary CommNet Server computer. (Client 1 of CS1 in the above illustration.) See Deployment - Microsoft SQL Server iDataAgent for more information.
Setting up the Standby CommNet Server
3. Install the CommNet Server software on the standby CommNet Server computer.

Make sure that all the updates installed in the primary CommNet Server are also installed on the standby CommNet Server

See Deployment - CommNet Server, for more information.
4. Stop all Services on the standby CommNet Server.

You cannot have services running on both the primary and standby computers.

 See Stop CommNet Server Services for step-by-step instructions.
5. Install the SQL Server iDataAgent on the standby CommNet Server computer. (Client 2 of CS1 in the above illustration.) See Deployment - Microsoft SQL Server iDataAgent for more information.
Setting up the Standby CommNet Server Database
6. Using the SQL Server iDataAgent, perform a full backup of the SQL database in the primary CommNet Server and restore it to the SQL Server in the standby CommNet Server. The database must be in the standby state after the restore.
  • See Start a Full/Incremental/Differential Backup for step-by-step instructions on performing a full backup using the SQL Server iDataAgent. This can be found in the Backup - Microsoft SQL Server section.
  • See Restore a Single Database Without Browsing for step-by-step instructions on restoring data using the SQL Server iDataAgent. This can be found in the Restore - Microsoft SQL Server section.
7. Using the SQL Server iDataAgent, schedule frequent backups of the Transaction Logs in the primary server. It is recommended to schedule backups every 30 minutes.

Schedule a restore of the transaction logs to be run after each backup. The database must be in the standby state after every Transaction Log restore.

  • If possible, choose a magnetic storage policy for performance reasons.
  • Make sure to periodically verify the scheduled jobs to ensure that the transaction log backup and restore complete successfully.
See Start a Transaction Log Backup for step-by-step instructions. This can be found in the Backup - Microsoft SQL Server section.

See Also:

Warm Database Restore for more information on the performing this type of restore.
Switching the CommNet Server from Primary to Standby in Case of failures
1. If the primary CommNet Server is still active stop all services on the CommNet Server computer. See Stop CommNet Server Services for step-by-step instructions.
2. In the standby computer, using the SQL Server Management Studio, bring the Calypso Monitor database online. See the SQL Server Management Studio help for information on bringing the database online.
3. In the Standby CommNet Server, start the services. See Start CommNet Server Services for step-by-step instructions.
4. Open the CommNet Console and re-apply the permanent license associated with the standby CommNet Server. See Add New Licenses for step-by-step instructions.
5. Perform the following steps on all the CommCells that are registered with this CommNet Server:
  • From the CommNet Browser, open the Cell Registration dialog box, select each CommCell then click Modify.
  • From the Modify CommCell dialog box, type a new CommNet interface name in the CommNet Interface Name box.
  • Click OK.
  • After all the cells have been changed, click Close from the Cell Registration dialog box.
See Register a Cell for step-by-step instructions.
6. Synchronize the CommCell in the CommNet Browser to obtain up-to-date information about the CommCell See Synchronize Cells for step-by-step instructions.
7. Disable all scheduled job and kill running jobs associated with the SQL Server iDataAgent in the primary CommNet Server.  
Switching the CommNet Server Back From Standby to Primary When the Failure Condition is Cleared
1. Stop all services on the standby CommNet Server. See Stop CommNet Server Services for step-by-step instructions.
2. In the standby CommNet Server, using the SQL Server Management Studio, backup the Calypso Monitor database and create a .dmp file. See the SQL Server Management Studio help for information on creating the dump file.
3. In the primary CommNet Server, using the SQL Server Management Studio, restore the Calypso Monitor  database. See the SQL Server Management Studio help for information on restoring a database.
4. In the primary CommNet Server, start the services. See Start CommNet Server Services for step-by-step instructions.
5. Open the CommNet Console and re-apply the permanent license associated with the primary CommNet Server. See Add New Licenses for step-by-step instructions.
6. Perform the following steps on all the CommCells that are registered with this CommNet Server:
  • From the CommNet Browser, open the Cell Registration dialog box, select each CommCell then click Modify.
  • From the Modify CommCell dialog box, type a new CommNet interface name in the CommNet Interface Name box.
  • Click OK.
  • After all the cells have been changed, click Close from the Cell Registration dialog box.
See Register a Cell for step-by-step instructions.
7. Synchronize the CommCell in the CommNet Browser to obtain up-to-date information about the CommCell See Synchronize Cells for step-by-step instructions.
8. Enable all schedules including the Backup Schedule for the SQL Server iDataAgent.

Back to Top