Backing Up and Restoring Operations Connector Configuration and Policies

When backing up Operations Connector, keep in mind the following recommendations:

• Back up the Operations Connector configuration and user created polices. Do not back up runtime data, such as topology repositories or performance store data. You can find a detailed list of items to back up in the following sections.
• Restore the Operations Connector configuration to a clean Operations Connector installation (that is, a new installation without any modifications in the configuration), because some configuration files may be overwritten during the restore procedure.

Operations Connector Policies

The Operations Connector policies are stored in the following directory:

Linux: /var/opt/OV/datafiles/policymanagement/store

Windows: %OvDataDir%datafiles\policymanagement\store

Each policy consists of two files, a data file (*_data) and a header file (*_header.xml).

• To back up the policies:

  Copy the policies to a backup location.

• To restore the policies:

  1. Copy the policies from the backup location back to the folder where Operations Connector policies are stored.

  2. The copied policies are visible in the Operations Connector UI after you sign in. If a UI session is already open, click the refresh button.

Operations Connector Backsync Script

The backsync functionality is implemented as a single Perl script, located in:

Linux: /var/opt/OV/conf/backsync/OMBackSync.pl

Windows: %OvDataDir%conf\backsync\OMBackSync.pl

Back up this script if you modified any settings in it.

• To back up the script:

  1. Stop the ombacksync process:

     ovc –stop ombacksync

  2. Copy the OMBackSync.pl script to a backup location.

  3. Start the ombacksync process:

     ovc –start ombacksync

• To restore the script:

  1. Stop the ombacksync process.
  2. Copy the OMBackSync.pl script from the backup location back to the original location, overwriting the original file in the process.
  3. Start the ombacksync process.

Operations Connector Specific Settings in XPL

Several Operations Connector settings are set in XPL. For details on specific contexts, see the sections that follow.

• To back up the complete local XPL configuration:

  Copy the following file to a backup location:

  Linux: /var/opt/OV/conf/xpl/config/local_settings.ini

  Windows: %OvDataDir%conf\xpl\config\local_settings.ini

• To restore the XPL configuration, restore it on a per context basis, by using the command line interface provided with XPL:

  ovconfchg -edit

  Edit the context options as described in the following sections.

Operations Connector Web Application LWSSO Configuration

The LWSSO configuration consists of an XML configuration file and an XPL setting.

• To back up the configuration file and settings:

  1. Copy the following configuration file to a backup location:

     Linux: /var/opt/OV/conf/HPOprBSMC/lwsso-config.xml

     Windows: %OvDataDir%conf\HPOprBSMC\lwsso-config.xml

  2. Save (write down) the following XPL setting:

     [HPBSMC.LWSSO]
     BSMAccessGroups=<user_group_role_name>

• To restore the configuration file and settings:

  1. Replace the lwsso-config.xml file on the Operations Connector system with the one from the backup.

  2. Restore (add) the BSMAccessGroups XPL setting back to the XPL configuration.

Operations Connector Web Application Logging Configuration

The logging configuration for the Operations Connector Web Application is set in the following configuration file:

Linux: /var/opt/OV/conf/HPOprBSMC/bsmclog4j.properties

Windows: %OvDataDir%conf\HPOprBSMC\bsmclog4j.properties

• To back up the configuration:

  Copy the bsmclog4j.properties file to a backup location.

• To restore the configuration:

  Replace the bsmclog4j.properties file on the Operations Connector system with the one from the backup.

Operations Connector Web Application Ports Configuration

Operations Connector Web Application ports are configured in a configuration file and in XPL.

• To back up the configuration:

  1. Copy the following file to a backup location:

     Linux: /var/opt/OV/conf/HPOprBSMC/ports.properties

     Windows: %OvDataDir%conf\HPOprBSMC\ports.properties

  2. Save (write down) the following XPL configuration settings:

     [NONOV.TomcatB]
     HTTPPort=30001
     HTTPSPort=30000

• To restore the configuration:

  1. Replace the ports.properties configuration file on the Operations Connector system with the one from the backup.

  2. Restore the port configuration in OVTomcat:

     Linux:

     cd /opt/OV/nonOV/tomcat/b/bin
     ./ovtomcatbctl –sethttpport <HTTPPort_from_backed_up_XPL_config>
     ./ovtomcatbctl –sethttpsport <HTTPSPort_from_backed_up_XPL_config>
     ./ovtomcatbctl –configure
     cd /opt/OV/bin./ovc –restart ovtomcatB

     Windows:

     cd %OvInstallDir%\nonOV\tomcat\b\bin
     cscript OvTomcatBCtl.vbs –sethttpport <HTTPPort_from_backed_up_XPL_config>
     cscript OvTomcatBCtl.vbs –sethttpsport <HTTPSPort_from_backed_up_XPL_config>
     cd %OvInstallDir%\bin\win64
     ovc –restart ovtomcatB

Operations Connector Web Application User Configuration

Operations Connector stores its local admin user configuration in the file:

Linux: /var/opt/OV/conf/HPOprBSMC/users.properties

Windows: %OvDataDir%conf\HPOprBSMC\users.properties

• To back up the configuration file:

  Copy the users.properties file to a backup location.

• To restore the configuration file:

  Replace the users.properties file on the Operations Connector system with the one from the backup.

The Operations Connector REST Web Service Receiver Configuration

The Operations Connector REST Web Service Receiver is configured in XPL. Depending on the actual configuration, only some of the XPL configuration parameters listed below may be present.

• To back up the configuration:

  Save (write down) the following XPL configuration settings:

  [eaagt]
  RESTWS_AUTH_PASSWORD=<parameter_value>
  RESTWS_AUTH_USER=<parameter_value>
  RESTWS_PORT=<parameter_value>
  RESTWS_REGISTER_CB=<parameter_value>
  RESTWS_USE_BASIC_AUTH=<parameter_value>

• To restore the configuration:

  Restore the saved settings back to the XPL configuration on a freshly installed Operations Connector system.

Operations Connector Flexible Management Policy Template

Operations Connector contains an out-of-the-box template for creating an Event forwarding policy (the Flexible Management policy). If you made any customizations to this template file, create a backup of this file.

This template is used by the Operations Connector tool deploy-flexmgmt.[bat|sh] to create a policy eligible for event forwarding. The policy template consists of the following two files:

f6b8aff0-f467-4851-8407-5b60395648b4_data.template

f6b8aff0-f467-4851-8407-5b60395648b4_header.xml.template

The files are located in:

Linux: /var/opt/OV/conf/HPOprBSMC/

Windows: %OvDataDir%conf\HPOprBSMC

• To back up the template:

  Copy the listed *.template files to a backup location.

• To restore the template:

  Replace the listed *.template files on the Operations Connector system with the files from the backup.