1.2.2 Database backup and recovery
When you perform backup and recovery, all of the following items need to match on the backup source and the recovery destination:
-
Host name
-
IP address
-
PP model name
-
PP version (match the format of VVRRZZ)
-
Directory structure used by the product (permissions and the like must match)
It is assumed that the OS and hardware on the source and the destination are able to perform the same operations.
If the above conditions are not met, you will need to move files.
See 1.5 Migrating the configuration information and databases and perform the operations described there.
You can use OS commands or backup software to make a full backup of the entire system. However, we recommend that you back up or recover data by using the commands provided with individual JP1/IM - Manager functions that do not depend on OS commands or backup software. If you use OS commands or backup software, the following conditions must be met:
-
Data is backed up when all JP1/IM - Manager services, including the IM database, have been stopped.
-
Data is backed up when all file and registry information, including the information registered in the OS, is consistent.
-
The backup target files are not sparse files.
Databases cannot be partially backed up and recovered. If a database is partially backed up or recovered, database associations become contradictory. In this case, incorrect data could be referenced.
Back up and recover definition information in addition to the database itself. If you back up only the database, relationships with the definition information might become inconsistent.
Stop JP1/IM - View when you perform backup and recovery.
- Organization of this subsection
(1) Command execution log backup and recovery procedures
The following explains the procedures for backing up and recovering the command execution log.
(a) Backup procedure
To back up the command execution log:
-
Stop JP1/IM - Manager.
-
Stop JP1/Base.
-
Back up the target files.
For details about which files to back up, see 1.2.2(1)(c) Files to back up.
-
Start JP1/Base.
-
Start JP1/IM - Manager.
(b) Recovery procedure
To recover the command execution log:
-
Stop JP1/IM - Manager.
-
Stop JP1/Base.
-
Place the backup files in their respective directories.
-
Start JP1/Base.
-
Start JP1/IM - Manager.
- Important
-
When the log is recovered, the history of the automated actions taken and the commands executed from the Command Execution window between the time of backup and the time of recovery cannot be viewed.
(c) Files to back up
The files to back up are listed below.
- In Windows:
-
Table 1‒7: Files to back up (Windows) Information type
Files to back up
Command execution log file
All files under Base-path\log\COMMAND\
All files under shared-folder\jp1base\log\COMMAND\
Action information file
Console-path\log\action\actinf.log
shared-folder\jp1cons\log\action\actinf.log
Action hosts file
Console-path\log\action\acttxt{1|2}.log
shared-folder\jp1cons\log\action\acttxt{1|2}.log
- In UNIX:
-
Table 1‒8: Files to back up (UNIX) Information type
Files to back up
Command execution log file
All files under /var/opt/jp1base/log/COMMAND/
All files under shared-directory/jp1base/log/COMMAND/
Action information file
/var/opt/jp1cons/log/action/actinf.log
shared-directory/jp1cons/log/action/actinf.log
Action hosts file
/var/opt/jp1cons/log/action/acttxt{1|2}.log
shared-directory/jp1cons/log/action/acttxt{1|2}.log
For details about the command execution log file, see the JP1/Base User's Guide.
(2) Monitored object database backup and recovery procedures
The following explains the procedures for backing up and recovering the monitored object database. The monitored object database is used when the Central Scope functions are used.
(a) Backup procedure
To back up the monitored object database:
-
Stop JP1/IM - Manager.
-
Back up the target files.
The table below shows the files to back up.
Table 1‒9: Files to back up OS
Information type
Files to back up
Windows
Monitored object database
All files under Scope-path\database\jcsdb\
All files under shared-folder\jp1scope\database\jcsdb\
UNIX
Monitored object database
All files under /var/opt/jp1scope/database/jcsdb/
All files under shared-directory/jp1scope/database/jcsdb/
-
Start JP1/IM - Manager.
(b) Recovery procedure
To recover the monitored object database:
-
Stop JP1/IM - Manager.
-
Place the backup files in directories.
-
Start JP1/IM - Manager.
(3) Host information database backup and recovery procedures
The following explains the procedures for backing up and recovering the host information database. The host information database is used when the Central Scope functions are used.
(a) Backup procedure
To back up the host information database:
-
Stop JP1/IM - Manager.
-
Back up the target files.
The table below shows the files to back up.
Table 1‒10: Files to back up OS
Information type
Files to back up
Windows
Host information database
All files under Scope-path\database\jcshosts\
All files under shared-folder\jp1scope\database\jcshosts\
UNIX
Host information database
All files under /var/opt/jp1scope/database/jcshosts/
All files under shared-directory/jp1scope/database/jcshosts/
-
Start JP1/IM - Manager.
(b) Recovery procedure
To recover the host information database:
-
Stop JP1/IM - Manager.
-
Place the backup files in directories.
-
Start JP1/IM - Manager.
(4) Event database backup and recovery procedures
For details about the procedures for backing up and recovering the event database, see the explanation on backup and recovery in the JP1/Base User's Guide.
When you are recovering the event database of a JP1/IM - Manager host, you must also back up and recover the command execution log at the same time. For details about the procedures for backing up and recovering the command execution log, see 1.2.2(1) Command execution log backup and recovery procedures.
- Important
-
When you are backing up and recovering the event database, you must also back up and recover the command execution log at the same time.
If you back up and recover only the event database, an inconsistency will occur in the association of JP1 event execution results and automated actions inside the event database.
The results of automated actions executed before the event database recovery may be displayed as the execution results of automated actions for JP1 events registered after the event database recovery.
(5) Backup and recovery procedures for the file for accumulated response-waiting events
The following explains the procedures for backing up and recovering the file for accumulated response-waiting events. This file is used by the response-waiting event management function.
(a) Backup procedure
-
Stop JP1/IM - Manager.
-
Back up the target files.
The table below shows the files to back up.
Table 1‒11: Files to back up OS
Files to back up
Windows
Console-path\log\response\resevent.dat
shared-folder\jp1cons\log\response\resevent.dat
UNIX
/var/opt/jp1cons/log/response/resevent.dat
shared-directory/jp1cons/log/response/resevent.dat
-
Start JP1/IM - Manager.
(b) Recovery procedure
-
Stop JP1/IM - Manager.
-
Place the backup files in the appropriate directories.
-
Start JP1/IM - Manager.
(6) IM database backup and recovery procedures
This subsection explains the procedures for backing up and recovering the IM database on a physical host, and in a cluster environment.
- Important
-
When you back up and recover the IM database, you must also back up and recover the event database. For details about the procedure for backing up and recovering the event database, see 1.2.2(4) Event database backup and recovery procedures.
- Important
-
Depending on the method used to recover the event database, you might need to re-create the event database. Depending on the method used to re-create the event database, you might also need to re-create the IM database. In such a case, do not recover the IM database. If the IM database is recovered, information in the IM database might no longer match the information in the event database, resulting in an unexpected change to the JP1 event handling status when the handling status is changed.
- Important
-
Do not recover the backup data that was acquired before jimdbupdate command execution from the pre-update IM database to the IM database after jimdbupdate command execution.
After you have executed the jimdbupdate command, use the jimdbbackup command again to acquire a backup.
(a) Procedures for backing up and recovering the IM database on a physical host
To back up the IM database on a physical host:
-
In Windows, check whether the IM database service (JP1/IM3-Manager DB Server) is running.
-
Stop the following services:
-
JP1/IM3-Manager service
-
In Windows, the cluster service (JP1/IM3-Manager DB Cluster Service) of the IM database
-
If JP1/IM - MO is being used, the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source
-
-
Use the jimdbbackup command to make a backup of the target database.
For details about the jimdbbackup command, see jimdbbackup in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
-
Back up the target files.
For details about which files to back up, see 1.1.1(1) Backup (in Windows) and 1.1.1(3) Backup (in UNIX).
-
Start the services that were stopped in step 2.
To recover the IM database on a physical host:
-
In Windows, check whether the IM database service (JP1/IM3-Manager DB Server) is running.
-
Stop the following services:
-
JP1/IM3-Manager service
-
In Windows, the cluster service (JP1/IM3-Manager DB Cluster Service) of the IM database
-
If JP1/IM - MO is being used, the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source
-
-
Using the jimdbrecovery command, recover the target database.
For details about the jimdbrecovery command, see jimdbrecovery in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
-
Place the backed up files in their respective directories.
With IM configuration management enabled, place the backed up files in their respective directories.
-
When you are using the Intelligent Integrated Management Base, delete the file shown in the table below.
OS
Files to delete
Windows
Manager-path\data\imdd\actevent.ser
Manager-path\data\imdd\imdd_nodeStatus.ser
Manager-path\data\imdd\jddactseq.ser
UNIX
/var/opt/jp1imm/data/imdd/actevent.ser
/var/opt/jp1imm/data/imdd/imdd_nodeStatus.ser
/var/opt/jp1imm/data/imdd/jddactseq.ser
-
Start the services that were stopped in step 2.
-
When you use the Intelligent Integrated Management Base, execute the jddupdatetree command in the new and rebuilding mode.
(b) Procedures for backing up and recovering the IM database in a cluster environment
The procedure for backing up the IM database in a cluster environment is described below. In the case of a cluster environment, execute the backup process on the executing host. Furthermore, the shared directory must be accessible.
To back up the IM database in a cluster environment:
-
Stop the JP1/IM3-Manager service and the cluster service (JP1/IM3-Manager DB Cluster Service_logical-host-name) of the IM database.
If JP1/IM - MO is being used, also start the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source.
-
Using the jimdbbackup command, make a backup of the target database.
For details about the jimdbbackup command, see jimdbbackup in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
-
Back up the target files.
For details about which files to back up, see 1.1.1(1) Backup (in Windows) and 1.1.1(3) Backup (in UNIX).
-
Start the JP1/IM3-Manager service and the cluster service (JP1/IM3-Manager DB Cluster Service_logical-host-name) of the IM database that was stopped in Step 1.
If JP1/IM - MO is being used, also start the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source.
To recover the IM database in a cluster environment. If the system operates in a cluster configuration, perform recovery on the active host. You will also need to be able to access shared directories.
-
Stop the JP1/IM3-Manager service and the cluster service (JP1/IM3-Manager DB Cluster Service_logical-host-name) of the IM database.
If JP1/IM - MO is being used, also stop the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source.
-
Using the jimdbrecovery command, recover the target database.
For details about the jimdbrecovery command, see jimdbrecovery in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
-
Place the backed up files in their respective directories.
With IM configuration management enabled, place the backed up files in their respective directories.
-
When you are using the Intelligent Integrated Management Base, delete the file shown in the table below.
OS
Files to delete
Windows
shared-folder\data\imdd\actevent.ser
shared-folder\data\imdd\imdd_nodeStatus.ser
shared-folder\data\imdd\jddactseq.ser
UNIX
shared-directory/jp1imm/data/imdd/actevent.ser
shared-directory/jp1imm/data/imdd/imdd_nodeStatus.ser
shared-directory/jp1imm/data/imdd/jddactseq.ser
-
Start the JP1/IM3-Manager service and the cluster service (JP1/IM3-Manager DB Cluster Service_logical-host-name) of the IM database that was stopped in Step 1.
If JP1/IM - MO is being used, also start the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source.
-
When you use the Intelligent Integrated Management Base, execute the jddupdatetree command in the new and rebuilding mode.
(7) Backup and recovery procedure of Intelligent Integrated Management Database
Perform regular backups as a means of recovery in the event of a failure of the Intelligent Integrated Management Database. The way to get a backup is an offline backup.
Describes how to perform offline backups and recovery while Intelligent Integrated Management Database services are stopped, when Intelligent Integrated Management Database services can be stopped, for example, due to planned outages.
When copying files and directories, in the case of Linux, please copy them while preserving the directory and file attributes.
(a) Backup procedure
The procedure for offline backup of the Intelligent Integration Management Database is as follows:
-
Stop JP1/IM - Manager services.
For details on how to stop Intelligent Integrated Management Database service, see 3.2 Stopping JP1/IM - Manager.
-
Stop Intelligent Integrated Management Database service.
For Windows
To stop Intelligent Integrated Management Database service and trend data management service, select [Control Panel]-[Management tools]-[Service] and then stop the trend data management service and Intelligent Integrated Management Database service.
For Linux
As JP1/IM - Manager goes down, Intelligent Integrated Management Database, and Trend Data Management services are also stopped. For details, see 3.2.2 In UNIX.
-
Back up IM database (Integrated Monitoring DB) for disaster recovery (when backing up the Integrated Monitoring DB according to Intelligent Integrated Management Database).
For details on how to back up, see 1.2.2(6)(a) Procedures for backing up and recovering the IM database on a physical host and 1.2.2(6)(b) Procedures for backing up and recovering the IM database in a cluster environment.
-
Back up Intelligent Integrated Management Database for disaster recovery using jimgndbbackup command-with MAINT in the parameter-m.
For details and examples of the jimgndbbackup command, see jimgndbbackup in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
-
Start the services in the Intelligent Integrated Management Database.
For Windows
To start Intelligent Integrated Management Database service, start Intelligent Integrated Management Database service and Trend Data Management Service in order from [Control Panel]-[Management tools]-[Service] (There is a dependency. When you start the Trend Data Management Service, Intelligent Integrated Management Database service starts automatically.)
For Linux
As JP1/IM - Manager starts, Intelligent Integrated Management Database, and Trend Data Management Services are also started. For details, see 3.1.2 In UNIX.
-
Start JP1/IM - Manager services.
For details about how to start, see 3.1 Starting JP1/IM - Manager.
(b) Recovery procedure
Following are the steps to recover a backup of an Intelligent Integrated Management Database taken by an offline backup:
-
Stop JP1/IM - Manager services.
For details on how to stop Intelligent Integrated Management Database service, see 3.2 Stopping JP1/IM - Manager.
-
Stop JP/IM - Agent service.
For details, see 10.3 Stopping the service
-
Delete Intelligent Integrated Management Database.
For details, see 1.25.1 (1) The procedure for delete Intelligent Integrated Management Database and 2.23.1 (1) The procedure for delete Intelligent Integrated Management Database in the JP1/Integrated Management 3 - Manager Configuration Guide.
-
Construct Intelligent Integrated Management Database.
For details, see 1.5 Construction of Intelligent Integrated Management Database (for Windows) and 2.5 Construction of Intelligent Integrated Management Database (for UNIX) in the JP1/Integrated Management 3 - Manager Configuration Guide.
-
Stop Intelligent Integrated Management Database service.
For Windows
To stop Intelligent Integrated Management Database service and trend data management service, select [Control Panel]-[Management tools]-[Service] and then stop the trend data management service and Intelligent Integrated Management Database service.
For Linux
As JP1/IM - Manager goes down, Intelligent Integrated Management Database, and Trend Data Management services are also stopped. For details, see 3.2.2 In UNIX.
-
Perform disaster recovery for IM database (Integrated Monitoring DB) if you want to recover the Integrated Monitoring DB for Intelligent Integrated Management Database.
For recovery methods, see 1.2.2(6)(a) Procedures for backing up and recovering the IM database on a physical host and 1.2.2(6)(b) Procedures for backing up and recovering the IM database in a cluster environment.
-
Use jimgndbrestore command-with MAINT in the parameter-m-to perform disaster recovery for Intelligent Integrated Management Database.
For details and examples of the jimgndbrestore command, see jimgndbrestore in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
-
Start Intelligent Integrated Management Database service.
For Windows
To start Intelligent Integrated Management Database service, start Intelligent Integrated Management Database service and Trend Data Management Service in order from [Control Panel]-[Management tools]-[Service] (There is a dependency. When you start the Trend Data Management Service, Intelligent Integrated Management Database service starts automatically.)
For Linux
As JP1/IM - Manager starts, Intelligent Integrated Management Database, and Trend Data Management Services are also started. For details, see 3.1.2 In UNIX.
-
Start JP/IM - Agent service.
For details, see 10.2 Starting the Service.
-
Start JP1/IM - Manager service.
For how to start Intelligent Integrated Management Database service, see 3.1 Starting JP1/IM - Manager.
-
Execute jddupdatetree command in the new/rebuild mode.
For details about the jddupdatetree command, see jddupdatetree in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
If you also want to perform IM database (integrated monitoring DB) recovery, perform it after performing IM database (integrated monitoring DB) recovery.