Recovering Hitachi Ops Center applications from a backup archive

Recovering Administrator

To recover Administrator from a backup archive, complete the following steps:

Access the Virtual Appliance Manager by opening a browser and entering the following URL.
```
https://ip-address:port/vam
```
where:
- ip-address is the IP address of the Administrator server.
- port is the port number of the Administrator server. The default port number is 443 or 20961. The default login credentials are sysadmin/sysadmin.
Click Restore and either drag and drop the backup file or click the plus sign (+) to browse.
Click Submit. The restore procedure can take up to an hour, after which Administrator restarts.
Remove and reregister Administrator in Common Services.
1. Remove Administrator from Common Services by going to the Hitachi Ops Center Portal and deleting it.
2. Run the setupcommonservice command to register with Common Services.
3. If necessary, change permissions for user groups.

Recovering Analyzer

To recover Analyzer from a backup archive, complete the following steps:

Run the tar command to extract the backup archive file.
tar xf backup-archive-file -C destination-directory
Run the following restoresystem command.
Analyzer-installation-directory/Analytics/bin/restoresystem -dir destination-directory -type all

For details, see the description of the restoresystem command in the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Analyzer RAID Agent

<For Linux>

Before recovering Analyzer RAID Agent, verify the following:

If instances with the same names as those on the backup source do not exist in the restore destination, manually create RAID Agent instances using the same instance names as those on the backup source.
Verify that the following items are the same between the backup source host and the restore destination host:
- OS (Linux)
- Version number of the RAID Agent
- Instance name
- Hybrid Store storage destination
Stop all RAID Agent services on the restore destination host.
Verify that the restore destination has free space equal to or greater than the size of the data to be restored.

To recover Analyzer RAID Agent from a backup archive, complete the following steps:

Confirm that the same name instance exists as when the backup was taken, and if it does not exist, create it.
Copy the backup archive file to a working directory and extract it:
tar xf backup-archive-file
Run the following command to restore the performance data and configuration information files:
/opt/jp1pc/htnm/bin/htmhsrestore -dir extracted-data-directory
Run the jpctdchkinst command to check whether the instance is monitoring the targets correctly. If it is not, run the jpcinssetup command to change the settings, and then run the jpctdchkinst command again to check the monitoring status.

For details, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note:

Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.
You cannot restore the following by using the htmhsrestore command and must make any required changes manually:
- If you changed the port numbers or SSL communication settings in the backup source environment, you must also change them in the restore destination by editing the following file.
  /opt/jp1pc/htnm/Rest/config/htnm_httpsd.conf
- If you changed the port numbers specified in the following files in the backup source environment, you must also change them in the restore destination.
  /opt/jp1pc/htnm/Rest/config/htnm_httpsd.conf
  
  /opt/jp1pc/htnm/HBasePSB/CC/server/usrconf/ejb/AgentRESTService/usrconf.properties

<For Windows>

Before recovering Analyzer RAID Agent, verify the following:

If instances with the same names as those on the backup source do not exist in the restore destination, manually create RAID Agent instances using the same instance names as those on the backup source.
Verify that the following items are the same between the backup source host and the restore destination host:
- OS (Windows)
- Version number of the RAID Agent
- Instance name
- Hybrid Store storage destination
Stop all RAID Agent services on the restore destination host.
Verify that the restore destination has free space equal to or greater than the size of the data to be restored.

To recover Analyzer RAID Agent from a backup archive, complete the following steps:

Confirm that same name instance exists as when the backup was taken, and if it does not exist, create it.
Copy the backup archive file to a working folder and extract it:
tar xf backup-archive-file
Run the following command to restore the performance data and configuration information files:
Analyzer-RAID-Agent-Installation-folder\htnm\bin\htmhsrestore -dir extracted-data-folder
Run the jpctdchkinst command to check whether the instance is monitoring the targets correctly. If it is not, run the jpcinssetup command to change the settings, and then run the jpctdchkinst command again to check the monitoring status.

For details, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note:

Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.
You cannot restore the following settings by using the htmhsrestore command and must make any required changes manually:
- If you changed the port numbers or SSL communication settings in the backup source environment, you must also change them in the restore destination by editing the following file.
  Analyzer-RAID-Agent-Installation-folder\htnm\Rest\config\htnm_httpsd.conf
- If you changed the port numbers specified in the following files in the backup source environment, you must also change them in the restore destination.
  Analyzer-RAID-Agent-Installation-folder\htnm\Rest\config\htnm_httpsd.conf
  
  Analyzer-RAID-Agent-Installation-folder\htnm\HBasePSB\CC\server\usrconf\ejb\AgentRESTService\usrconf.properties

Recovering Analyzer detail view

To recover Analyzer detail view from a backup archive, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Analyzer probe

To recover Analyzer probe from a backup archive, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Analyzer viewpoint

To recover Analyzer viewpoint from a backup archive, run the following command:

Run the following restore command.
/opt/hitachi/analyzer_viewpoint/bin/restore --file {backup-archive-file-path}

For details, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Analyzer Virtual Storage Software Agent

To recover Analyzer Virtual Storage Software Agent from a backup archive, complete the following steps:

Extract the archive file. For the specific file path, see the Protector GUI.
Copy the contents to the following directories:
/var/{installation-directory}/system/access-points.yaml

/var/{installation-directory}/config/userconfig-setting.yaml

For details, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Analyzer On-demand real time monitoring module (Linux only)

To recover the Analyzer On-demand real time monitoring module for Linux from a backup archive, complete the following steps:

Extract the archive file. For the specific file path, see the Protector GUI.
Copy the contents to the following directories:
/opt/hitachi/Analytics/granular-data-collection-api/conf/user-granular-data-collection-api.conf

/opt/hitachi/Analytics/granular-data-collection-api/conf/system-granular-data-collection-api.conf

For details, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Automator

Verify the following settings are the same between the backup source host and the restore destination host:
- Host name and IP address
- Account of the OS user used by Automator
- Hitachi Ops Center product environment (configuration, version, and revision)
- Installation path of Automator
- System locale and character set
Verify that no tasks are currently being processed in the Automator "Status" column of the Tasks tab with a status of "In Progress", "Waiting for Input", "In Progress (with Error)", "Long Running", or "In Progress (Terminating)".

To recover Automator from a backup archive, complete the following steps:

Run the tar command to extract the backup archive file:
tar xvf backup-archive-file -C destination-file-path
Run the restoresystem command:
Automator-installation-directory/bin/restoresystem -dir destination-file-path -auto

For details about restoresystem command, see the Hitachi Ops Center Automator Installation and Configuration Guide.

Recovering API Configuration Manager

To recover API Configuration Manager from a backup archive, complete the following steps:

Run the jar command to extract the backup archive file:

Windows:

Configuration-Manager-installation-directory\base\jdk\bin\jar xf backup-archive-file ConfManager

Linux:

Configuration-Manager-installation-directory/base/jdk/bin/jar xf backup-archive-file ConfManager
Restore the extracted files. For details, see "Restoring the REST API database and environment settings file" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.

Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Common Services

Verify the installation path and version number of Common Services are the same between the backup source host and the restore destination host.

To recover Common Services from a backup archive, run the following csrestore command for the applicable data.

Common-Services-installation-directory/utility/bin/csrestore.sh -file backup-archive-file

For details, see Restoring Common Services.

Note: Data backed up by using Common Services in a viewpoint OVF environment cannot be restored to the installer version of Common Services.

Recovering Protector

To restore Protector from a backup archive, see the Hitachi Ops Center Protector User Guide.