12.11 Restoring JP1/AO servers remotely by using backup files

You can restore JP1/AO servers remotely by using backup files, even if a JP1/AO server stops for any reason. You can use this method for disaster recovery when a large disaster or system failure occurs.

See the following figure for details.

Figure 12‒1: Example of restoring a JP1/AO server remotely by using backup files

Branch A, which is the main site, obtains the backup file after close of business at midnight every day, and sends it to branch B, which is a remote site. Branch B always retains the backup file of branch A created at midnight on the previous day. Because of this, if a disaster occurs in branch A and its JP1/AO server stops, the JP1/AO server can be restored in branch B from the backup file created at midnight on the previous day.

The procedure for restoring the JP1/AO server remotely by using the backup file is described below.

Prerequisite conditions

• The following items must match between the JP1/AO server in the main site and the JP1/AO server in the remote site:

  • System locale

  • JP1 user settings used in JP1/AO (permissions and uses of the mapped OS)

  • Versions of JP1/Base

  • Installation destination folder for JP1/Base

  • Versions of JP1/AO

  • Installation folder of JP1/AO

  • If Hitachi Command Suite products are installed, the environment of the Hitachi Command Suite products (configuration, versions, and revisions)

  • When public key authentication is used for connection with the target device, the storage location of the private key file

    Note that the key can be allocated by the following methods:

    • Allocating the same key for the main site and a remote site

      Send and allocate the private key file created in the main site to the remote site.

    • Allocating different keys in the main site and the remote site

      Create separate keys for the main site and a remote site, and then allocate the corresponding public key file to the device to be used.

• The cluster environment is not constructed

• No update programs from versions 10-00 have been installed after the upgrade

Flow of restoring JP1/AO servers remotely by using the back-up file:

The following figure explains the flow for restoring the JP1/AO server in a remote site by using the backup file of the main site.

Table 12‒1:  Flow of restoring JP1/AO servers remotely by using the backup file

Timing	Main site	Remote site
During normal operation	Backs up data.#	--
	Sends the backed up file to a remote site.	--
When a disaster or failure occurs	--	Uses the latest backup file to restore the JP1/AO server in the main site.

Legend:

--: N/A

#

We recommend you back up data regularly and automatically.

Procedure during normal operation

Obtain the latest backup file of the main site, and send it to a remote site.

1. Obtain the latest backup file of the main site.

   For details about how to obtain the backup file of JP1/AO servers, see 12.1 Backing up data in a JP1/AO system (non-cluster configuration).

   Note, however, that you do not need to perform the procedure for backing up JP1/Base settings or database information.

2. Send the obtained backup file of the main site to a remote site.

Tip

• You cannot back up the files below by the backupsystem command. If you intend to use the same file in the main site and a remote site, back up data manually when necessary, and send it to the remote site.

  • SSL server certificate file for HTTPS connection

  • Private key file for HTTPS connection

  • Private key file for public key authentication

  You can use different files in the main site and a remote site. In that case, back up or create the above files separately in the main site and the remote site.

Procedure when a disaster or failure occurs

Use the latest backup file of the main site in the remote site to restore the JP1/AO server in the main site.

Tip

If the following settings for the JP1/AO servers in the main site and the remote site are the same, you do not need to perform steps 4 through 6:

• Configuration file for external authentication server linkage (exauth.properties)

• Security definition file (security.conf)

• Port number settings (httpsd.conf, hsso.conf)

• HTTPS connection settings (httpsd.conf)

• Number of the port between JP1/AO and the Web browser

• Number of the port used for communication between JP1/AO and the task-processing engine

1. In the remote site, make sure there is no task in In Progress, Waiting for Response, Abnormal Detection, or Terminated status. If there is such a task, stop execution of the task, or wait until it enters Completed or Failed status.

2. When the JP1/AO system is running, execute the hcmdssrv command with the /stop option specified to stop the JP1/AO system.

3. Execute the restoresystem command to restore settings or database information of JP1/AO in the main site.

   Tip

   You cannot restore the files below by using the restoresystem command. If you intend to use the same file in the main site and a remote site, reallocate it manually when necessary.

   • SSL server certificate file for HTTPS connection

   • Private key file for HTTPS connection

   • Private key file for public key authentication

   Store the files for HTTPS connection in the location defined in the httpsd.conf file, and the files for public key authentication in the location defined in the property file (config_user.peroperties).

4. Reset the definition files below according to the remote site environment.

   You can back up the following definition files by using the backupsystem command, but cannot restore by using the restoresystem command.

   • Configuration file for external authentication server linkage (exauth.properties)

   • Security definition file (security.conf)

   • Port number settings (httpsd.conf, hsso.conf)

   • HTTPS connection settings (httpsd.conf)

   The definition files are stored in the following folders:

   • backup-destination-folder\HBase\base\conf

   • backup-destination-folder\HBase\base\httpsd.conf

5. Specify HTTPS connection settings if necessary.

6. If you have changed the default port number settings listed below, reset them according to the procedure for changing the port number:

   • Number of the port used for communication between JP1/AO and the Web browser

   • Number of the port used for communication between JP1/AO and the task-processing engine

7. Execute the hcmdssrv command with the /start option specified to start the JP1/AO system.

8. Execute the following command in the command prompt:

   • set JP1_USERNAME=JP1-user-to-use-in-JP1/AO (the value for shared built-in service property JP1-user-name)

   • ajsagtalt -a loop -s host-name-in-remote-site

   • ajsagtalt -a userResponse -s host-name-in-remote-site

   Tip

   Commands beginning with ajs are stored in the storage destination folder of the system file in the task-processing engine. For details, see List of folders in the Job Management Partner 1/Automatic Operation Configuration Guide.

9. Execute the hcmdschgurl command to update the URL information according to the remote site environment.

The JP1/AO server of the main site is restored in the remote site.

Related topics

• Procedure for setting up the configuration file for external authentication server linkage in the Job Management Partner 1/Automatic Operation Configuration Guide

• Security definition file (security.conf) in the Job Management Partner 1/Automatic Operation Configuration Guide

• Procedure to enable HTTPS connections in the Job Management Partner 1/Automatic Operation Configuration Guide

• Procedure to change the port number in the Job Management Partner 1/Automatic Operation Configuration Guide

• Procedure to change the URL in the Job Management Partner 1/Automatic Operation Configuration Guide

• Procedure to set public key authentication for SSH connections in the Job Management Partner 1/Automatic Operation Configuration Guide

To Page Top