7.14 Restoring a JP1/AO server at a remote site using backup files

If a JP1/AO server stops for some reason, you can restore it at a remote site using backup files. You can use this method to perform disaster recovery when a large-scale disaster or system failure occurs.

An example is shown in the figure below.

Figure 7‒1: Example of restoring a JP1/AO server at a remote site using backup files

In this example, branch A is the main site and branch B the remote site. Branch A obtains a backup file at midnight after close of business every day, which it sends to branch B. This means that branch B always has a backup file for branch A created the previous midnight. If a disaster of some kind occurs that causes the JP1/AO server to stop, the JP1/AO server at branch A can be restored to a server at branch B from the backup file created at midnight.

The procedure for restoring a JP1/AO server at a remote site using a backup file is described below.

Prerequisites

The following items are the same on the JP1/AO servers at the main site and the remote site:
- The system locale
- The version, revision, and restriction code of JP1/AO
- The JP1/AO installation folder
- In environments with Hitachi Command Suite products installed, the environments of the Hitachi Command Suite products (configuration, versions, revisions, and restriction codes)
- When using public key authentication for connections with devices, the locations of the private key files
  
  The following approaches to key allocation can be used:
  
  • Allocating the same key to the main site and the remote site
  
  A private key file is created on the main site and sent to the remote site.
  
  • Allocating different keys to the main site and the remote site
  
  Separate keys are created at the main site and remote site, and the corresponding public key file is allocated to devices on which operations will be performed.
JP1/AO is not operating in a cluster environment.
JP1/AO was not installed by an upgrade installation from version 10-02 or earlier.

General procedure for restoring a JP1/AO server at a remote site using a backup file

The following table shows the general procedure for using a backup file to restore a JP1/AO server at a remote site:

Table 7‒1: Restoring a JP1/AO server at a remote site using a backup file
Timing	Tasks on main site	Tasks on remote site
During normal operation	Acquire a backup file^#.	--
During normal operation	Send the backup file to the remote site.	--
In the event of a disaster or failure	--	Restore the JP1/AO server that was operating at the main site by using the most recent backup file.

Legend:: --: Not applicable.

#: We recommend that you acquire backup files regularly by an automatic process.

Procedure during normal operation

Acquire the latest backup file for the main site, and send it to the remote site.

Acquire the latest backup file for the main site.

For details on how to acquire the backup file for a JP1/AO server, see 7.1 Backing up data in JP1/AO (non-cluster configuration).
Send the backup file for the main site to the remote site.

Tip

The backupsystem command does not back up the files below. If you intend to use the same files at the main site and the remote site, back up these files manually, and send them to the remote site.

SSL server certificate files for https connections
Private key files for https connections
Private key files for public key authentication

You can use different certificate and key files at the main and remote sites. In this case, acquire or create certificate or key files separately for the main and remote sites and place them in the appropriate locations.

Procedure in the event of a disaster or failure

Use the most recent backup file of the main site to restore the JP1/AO server at the remote site.

Tip

You can skip steps 4 to 6 if the following settings are the same on the JP1/AO servers at the main site and the remote site:

Configuration file for external authentication server linkage (exauth.properties)
Security definition file (security.conf)
Port number settings (user_httpsd.conf)
Https connection settings (user_httpsd.conf)
Port number used for communication between JP1/AO and Web browsers

Make sure that there are no tasks in execution status (In Progress, Waiting for Input, In Progress (with Error), In Progress (Terminating), or Long Running). at the remote site. If there are such tasks at the remote site, either stop the tasks, or wait until they enter Completed or Failed status.
If the JP1/AO system is running, shut it down by executing the hcmds64srv command with the stop option specified.
Restore the JP1/AO settings and database data for the main site by executing the restoresystem command.
Tip
The restoresystem command does not restore the files below. If you intend to use the same files at the main site and the remote site, manually place them in the appropriate locations.
- SSL server certificate files for https connections
- Private key files for https connections
- Private key files for public key authentication
Place the files for https connections in the location defined in the user_httpsd.conf file, and the files for public key authentication in the location defined in the user-specified properties file (config_user.properties).
Reconfigure the following definition files to suit the environment of the remote site.

These definition files are backed up by the backupsystem command, but are not restored by the restoresystem command.
- Configuration file for external authentication server linkage (exauth.properties)
- Security definition file (security.conf)
- Port number settings (user_httpsd.conf)
- Https connection settings (user_httpsd.conf)
The definition files are stored in the following folders:
- backup-folder\HBase\base\conf or backup-folder/HBase/base/conf
- backup-folder\HBase\base\httpsd.conf or backup-folder/HBase/base/httpsd.conf
Configure https connections as needed.
If the following port numbers used for communications between JP1/AO and Web browsers were changed from the default, make the same change again by following the procedure for changing port numbers.
Start the JP1/AO system by executing the hcmds64srv command with the start option specified.
Execute the hcmds64chgurl command to update the URL information to suit the environment at the remote site.

Result of operation:

The JP1/AO server that was operating at the main site is recovered at the remote site.