12.3.2 Changing the settings of a disaster recovery environment
The following figure shows the flow of changing the settings or configuration of a disaster recovery environment.
|
Use the procedure below to change the configuration of JP1/AJS3 in a disaster recovery environment.
In a non-cluster environment, only perform the tasks designated for the primary node.
- Cautionary note
-
Perform these tasks while JP1/AJS3 - Manager and the embedded database are stopped at the remote site.
-
Stop JP1/AJS3 - Manager and the embedded database on the primary and secondary nodes of the main site as needed.
-
Make the necessary changes on the primary and secondary nodes of the main site.
Make the changes on the primary and secondary nodes. The procedure is the same as for a cluster system. For details, see 8. Setup for Operation in a Cluster System in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 17. Setup for Operation in a Cluster System in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).
After you finish changing the settings at the main site, execute the ajsembdbidlist command and keep a record of the following information related to the embedded DB on the main site logical host:
-
Folder where embedded database is installed
-
Setup identifiers
For details about the ajsembdbidlist command, see ajsembdbidlist in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
-
-
On the primary node at the main site, export the disaster recovery operation setup information as needed.
Execute the following command:
jajs_rpenvexport -h logical-host-at-main-site -d output-directory
For details about the jajs_rpenvexport command, see jajs_rpenvexport in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
-
On the primary node at the remote site, install or uninstall the embedded database as needed.
If you added or deleted a scheduler service when you configured the main site, you will need to install or uninstall the corresponding embedded database at the remote site. Check the details of the embedded database you recorded in step 2, and match the configuration between the main and remote sites.
- When installing an embedded database
-
Execute the following command:
ajsembdbinstl -s directory-of-embedded-DB-installation-media -mh logical-host-at-remote-site -i installation-folder-of-embedded-DB -id setup-identifier
- When uninstalling an embedded database
-
Execute the following command:
ajsembdbuninstl -mh logical-host-at-remote-site -id setup-identifier
For details about the ajsembdbinstl command and the ajsembdbuninstl command, see 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
-
On the primary node at the remote site, import the disaster recovery operation setup information as needed.
Execute the command below.
Copy the disaster recovery operation setup information you exported in step 3 to the remote site, and then execute the following command:
jajs_rpenvimport -h logical-host-at-remote-site -d input-directory
For details about the jajs_rpenvimport command, see jajs_rpenvimport in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
-
On the primary node at the remote site, perform individual settings as needed.
Not all settings related to the disaster recovery environment are included in the import information. Information that is outside the scope of the import function must be set individually. For details, see 9.2.3(3) Specifying specific settings on the remote site in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 18.2.3(3) Specifying specific settings on the remote site in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).
-
Repeat steps 4 to 6 on the secondary node at the remote site.
-
If you stopped JP1/AJS3 - Manager or the embedded database in step 1, start them again on the primary and secondary nodes at the main site.
Having configured the environment, resume work task activity at the main site.