5 Backing Up and Restoring Data

This chapter describes how to back up and restore Oracle Communications IP Service Activator data on Windows, Solaris, and Linux.

Introduction

Regular back up of IP Service Activator data is essential and we strongly recommend that you perform a routine daily back up, perhaps as an overnight process. Note that a check on the integrity of the database is also strongly recommended and this check must be performed on the backup database, rather than the live system. For information on checking the integrity of the database, see "Managing the IP Service Activator Database".

Note:

IP Service Activator supports multiple platforms like Windows, Solaris, and Linux.

IP Service Activator Installation Directories

The default installation directory for IP Service Activator server software on Solaris/Linux is:

• /opt/OracleCommunications/ServiceActivator

  Note:

  This chapter refers to the IP Service Activator installation directory as Service_Activator_Home.

The default installation directory for IP Service Activator user interface software on Windows workstations is:

• Program Files\Oracle Communications\Service Activator

Data to be Backed Up

This section provides an overview of the critical and non-critical data for back up:

• Critical system data must be backed up on a regular basis in order to ensure that the system can be restored to a known functioning position in case of a problem.

• Non-critical data is not essential to the running of IP Service Activator but should be backed up if you want to restore the system exactly to its previous state.

Critical Data

• The Oracle database tables

• Component Names: during installation, system components are assigned names automatically by the installation program using the following convention:

  component_type-host_name

  If the proxy agent needs to be reinstalled it should be given the same name, otherwise all existing device associations will be lost – that is, the system will not be able to associate the proxy agent with previously-allocated devices.

  • On Solaris/Linux, component names are stored in Service_Activator_Home/Config/cman.cfg

• Component Manager settings: these are configured on installation. If these are corrupted, the system on the relevant host must be reinstalled. The location of these settings depends on the operating system:

  • On Solaris/Linux, component manager settings are defined in Service_Activator_Home/Config/cman.cfg

• Naming service settings: these define the naming service host machine name and the port number to be used for communication:

  • On Solaris/Linux, these are defined in Service_Activator_Home/Config/omniorb.cfg

Non-critical Data

• User Interface settings: there are user preferences that may affect column ordering selections, and so on.

  • On Windows, user interface settings are defined beneath the HKEY_CURRENT_USER\Software\OracleCommunications registry key

• Device Driver and Network Processor audit logs: log files for each device driver, which are cycled once a day. These are stored in the Audit Trails subdirectory beneath Service_Activator_Home.

• Installed Components: the installed components and related files on the host. These are stored in the Service_Activator_Home/bin subdirectory on Solaris/Linux hosts.

Backing Up and Restoring Data on Windows

This section describes how to back up and restore IP Service Activator data on Windows workstations.

1. Back up the Registry settings HKEY_LOCAL_MACHINE\SOFTWARE\OracleCommunications (see "Backing Up and Restoring Windows Registry Settings").

Full Restore

For each workstation where IP Service Activator software was installed:

1. Restore the Registry settings HKEY_LOCAL_MACHINE\SOFTWARE\OracleCommunications (see "Backing Up and Restoring Windows Registry Settings").

Restart the system when the restore is complete.

Replacing the user interface

This section describes how to replace the user interface software when the hardware or operating system has been replaced or reinstalled. You may need to do this if a host on which a system component is installed stops functioning and has to be replaced.

Note:

When reinstalling components, you must enter the same serial number as was entered for the original installation.

For each workstation where a User Interface has been installed:

1. Reinstall the User Interface.

   You must enter the same serial number during installation as was entered for the original installation.

2. Restore the Registry settings HKEY_LOCAL_MACHINE\SOFTWARE\OracleCommunications (see "Backing Up and Restoring Windows Registry Settings").

Backing Up and Restoring Windows Registry Settings

This section explains how to back up and restore Windows Registry settings using regedt32.

To back up:

1. Start regedt32.

2. Select the appropriate key. For example: HKEY_LOCAL_MACHINE\SOFTWARE\OracleCommunications

3. Select Save Key from the Registry menu. The Save Key dialog box appears.

4. If you are running regedit instead of regedt32, select Export Registry File.

5. Specify a filename.

6. Click Save.

To restore:

1. Start regedt32.

2. Select Restore from the Registry menu. The Restore Key dialog box appears.

   If you are running regedit instead of regedt32, select Import Registry File.

3. Select the file to be restored.

4. Click Open.

5. Ensure the key is restored to the correct place in the registry.

Backup and Restore on Solaris/Linux

This section describes how to back up and restore IP Service Activator data on Solaris/Linux.

Backup Procedures on Solaris/Linux

This section details the procedures required to back up the system.

Full Backup

For the system as a whole

• Back up the Oracle database (for details see the Backup and Recovery procedures that come with your Oracle database).

For each host where IP Service Activator software is installed

• Back up the Service_Activator_Home directory including all subdirectories.

Backup must include everything that appears under Service_Activator_Home, not just the data that physically lives there. For example, if you realize that you need more space for WorkingData and decide to mount additional resource (or symlink it to some other file system on the machine), that information must be included in the backup.

The Service_Activator_Home directory contains symbolic links to files. We recommend you use separate tar commands to back up, and running tar as the root user. For more information about the IP Service Activator directory structure, see the IP Service Activator Installation Guide.

Replacing One or More Components

This section details the procedures to replace components on a host when the hardware or operating system has been replaced or reinstalled. You may need to do this if a host on which a system component is installed stops functioning and has to be replaced.

Note:

When reinstalling components, you must enter the same serial number as was entered for the original installation.

For the host where the Policy Server software has been installed:

1. Reinstall the Common components, the Naming Service, the Policy Server, the Component Manager, and the System Logger.

2. Restore the /opt/OracleCommunications/ServiceActivator/WorkingData directory.

3. Restore the Service_Activator_Home/Config/cman.cfg file.

4. Restore the Service_Activator_Home/Config/omniorb.cfg file.

For each host where the Proxy Agent/Device Drivers are installed:

1. Ensure that you have the component names used on the previous installation to use, otherwise any device associations are lost. Consult the backed up cman.cfg file.

2. Reinstall the Common components, the Component Manager, the Proxy Agent, and the relevant Device Drivers.

3. Restore the /opt/OracleCommunications/ServiceActivator/WorkingData directory.

4. Restore the Service_Activator_Home/Config/cman.cfg file.

5. Restore the Service_Activator_Home/Config/omniorb.cfg file.

For each host where the OIM is installed (optional):

1. Reinstall the Common Components, Component Manager, and the OSS Integration Manager.

2. Restore the Service_Activator_Home/Config/omniorb.cfg file.

For the host where the Event Handler is installed (optional):

1. Reinstall the Common Components, Component Manager, and Event Handler.

2. As the root user, restore the /opt/OracleCommunications/ServiceActivator/WorkingData directory.

3. If the event_handler.props and event_handler.rules files were backed up, restore these files to the Service_Activator_Home/Config directory.

4. If the Event Handler is installed on a dedicated host machine, restore the Service_Activator_Home/Config/omniorb.cfg file.

   Note:

   You do not need to perform the final step if the Event Handler is installed on the same host machine as the OIM.

For the host where the measurement component is installed (optional):

1. Reinstall the Common Components, Component Manager and the SLA Integration (measurement component).

2. If the measurement component is installed on a dedicated host machine, restore the Service_Activator_Home/Config/omniorb.cfg file.

   Note:

   You do not need to perform the final step if the measurement component is installed on the same host machine as the OIM.