1.1.1 JP1/IM - Manager backups and recoveries
- Organization of this subsection
(1) Backup (in Windows)
This subsection explains how to back up JP1/IM configuration information.
If you change the JP1/IM configuration, make a backup. When you make a backup of JP1/IM, be sure to make a backup of JP1/Base at the same time. For details about how to back up the definition files that are configured by JP1/Base users, see the JP1/Base User's Guide.
In addition, backing up and recovering JP1/IM - Agent product plugin follows JP1/IM - Manager backup and recovery.
Make a backup using a method of your choice, such as copying files. If at all possible, perform backup procedures while the JP1/IM services are not running. If you must make a backup while these services are running, note the following:
-
The definition files may be modified during execution in some cases. If a backup is made while a definition file is being modified, the backup file will be corrupted.
Immediately following the backup operation, compare the collected backup file with the original file to make sure their contents match.
-
When you make a backup, do not lock the target file. If you need to lock the file, first log out from all viewers that are connected, and then copy the target file to another file. After you have copied it, compare the copied file with the original file to make sure their contents match, and then back up the copied file.
-
When you restore the backed-up configuration information, the configuration is simply modified with the restored content, and the events that have already arrived at JP1/IM - Manager are not re-evaluated.
Of the files shown in the table below, back up all those that exist. If only some of the existing files are backed up, interaction with the remaining files might become inconsistent, preventing the system from operating correctly.
Also, if the system operates in a cluster configuration, back up each environment in the order of physical hosts, then logical hosts.
The table below shows the JP1/IM files to back up. For a logical host, replace Console-path in the table with shared-folder\JP1Cons, replace Scope-path with shared-folder\JP1Scope and replace Manager-path with shared-folder\JP1IMM.
#1: The common definition information backup file backs up the definition information of a logical host in a cluster system. This backup file is created during setup of the cluster system. This backup file backs up the definition information of JP1/IM as well as JP1/Base, JP1/AJS, and Version 06-02 and later of JP1/Power Monitor. For details, see 7.1.3(5) Setting common definition information in the JP1/Integrated Management 3 - Manager Configuration Guide.
#2: On a logical host, JP1_DEFAULT is the logical host name.
#3: This file exists only on a physical host.
#4: Files added by the user are backed up.
(2) Recovery (in Windows)
This subsection explains how to recover JP1/IM configuration information.
Before you recover JP1/IM backup information, you must first recover JP1/Base. Make sure that the following prerequisite conditions are met, and then recover the backup files to their original locations.
- Prerequisite conditions:
-
-
JP1/Base has already been installed.
-
JP1/IM - Manager has already been installed.
-
To recover a logical host environment, JP1 must already be set up in the logical host environment.
-
JP1/Base and JP1/IM - Manager are stopped.
-
Backup information is recovered only for the host of the environment that was backed up. To recover backup information, you must perform a recovery operation in each environment.
If the system operates in a cluster configuration, recover each environment in the order of physical hosts, then logical hosts.
(3) Backup (in UNIX)
This subsection explains how to back up JP1/IM configuration information.
If you change the JP1/IM configuration, make a backup. When you make a backup of JP1/IM, be sure to make a backup of JP1/Base at the same time. For details about how to back up the definition files that are configured by JP1/Base users, see the JP1/Base User's Guide.
In addition, backing up and recovering JP1/IM - Agent product plugin follows JP1/IM - Manager backup and recovery.
The available backup methods include the tar and cpio commands. You can also use a backup tool such as JP1/OmniBack II to make a backup. Make a backup using a method of your choice, such as copying files. If at all possible, perform backup procedures when JP1/IM daemons are not running. If you must make a backup while these daemons are running, note the following:
-
The definition files may be modified during execution in some cases. If a backup is made while a definition file is being modified, the backup file will be corrupted.
Immediately following the backup operation, compare the collected backup file with the original file to make sure their contents match.
-
When you make a backup, do not lock the target file. If you need to lock the file, first log out from all viewers that are connected, and then copy the target file to another file. After you have copied it, compare the copied file with the original file to make sure their contents match, and then back up the copied file.
-
When you restore the backed-up configuration information, the configuration is simply modified with the restored content, and the events that have already arrived at JP1/IM - Manager are not re-evaluated.
Of the files shown in the table below, back up all those that exist. If only some of the existing files are backed up, interaction with the remaining files might become inconsistent, preventing the system from operating correctly.
Also, if the system operates in a cluster configuration, back up each environment in the order of physical hosts, then logical hosts.
The table below shows the JP1/IM files to back up. For a logical host, replace /var/opt and /etc/opt in the table with shared-directory.
#1: The common definition information backup file backs up the definition information of a logical host in a cluster system. This backup file is created during setup of the cluster system. This backup file backs up the definition information of JP1/IM as well as JP1/Base, JP1/AJS, and Version 06-02 and later of JP1/Power Monitor. For details, see 7.1.3(5) Setting common definition information in the JP1/Integrated Management 3 - Manager Configuration Guide.
#2: On a logical host, JP1_DEFAULT is the logical host name.
#3: This file exists only on a physical host.
(4) Recovery (in UNIX)
This subsection explains how to recover the JP1/IM configuration information.
Before you recover JP1/IM backup information, you must first recover JP1/Base. Make sure that the following prerequisite conditions are met, and then recover the backup files to their original locations.
- Prerequisite conditions:
-
-
JP1/Base has been installed, and the setup command has already been executed.
-
JP1/IM - Manager has been installed, and the setup command has already been executed.
-
To recover a logical host environment, JP1 must already be set up in the logical host environment.
-
JP1/Base and JP1/IM - Manager are stopped.
-
Backup information is recovered only for the host of the environment that was backed up. To recover backup information, you must perform a recovery operation in each environment.
If the system operates in a cluster configuration, recover each environment in the order of physical hosts, then logical hosts.