6.1.2 Backing up the settings
- Organization of this subsection
(1) Backing up JP1/IM - EG for NNMi setup information
This subsection describes backup of the JP1/IM - EG for NNMi settings.
Whenever you make a backup of JP1/IM - EG for NNMi, you should also make a backup of JP1/Base. For details about backing up the definition files set by the JP1/Base user, see the JP1/Base User's Guide.
You can use any appropriate method to make a backup, such as by copying the files. You can make a backup while JP1/IM - EG for NNMi is running.
The following table lists the JP1/IM - EG for NNMi files to be backed up.
|
File name |
Description |
|---|---|
|
imevtgw_nnmi.conf |
Operation definition file |
|
imevtgw_nnmi_cia_map.conf |
Custom attribute mapping definition file# |
|
imevtgw_nnmi_forward_filter.conf |
NNMi incident forwarding filter definition file |
|
imevtgw_nnmi_label_mapping_category_en.conf |
Mapping definition file (for category) |
|
imevtgw_nnmi_label_mapping_family_en.conf |
Mapping definition file (for family) |
- #
-
If custom attribute mapping is not set, this file does not exist.
The files to be backed up are stored at the following locations:
- In Windows:
-
-
Physical host: EG-for-NNMi-path\conf
-
Logical host: shared-folder\JP1EG4NNMI\conf
-
- In UNIX:
-
-
Physical host: /etc/opt/jp1eg4nnmi/conf
-
Logical host: shared-directory/jp1eg4nnmi/conf
-
(2) Backing up common definition information
JP1/IM - EG for NNMi, you must back up common definition information as well as the definition files. This information includes common definition information for JP1/Base, JP1/IM, and JP1/AJS.
To back up common definition information, execute the following command to acquire only the common definition information for JP1/IM - EG for NNMi:
jbsgetcnf -c JP1EG4NNMI > backup-file
When you run JP1/Base in a cluster system, execute the following command to acquire only the common definition information for JP1/IM - EG for NNMi:
jbsgetcnf -h logical-host-name -c JP1EG4NNMI > backup-file
Note that the logical host name must be correctly specified with lower or upper case as specified when the logical host was set up.
- Important
-
When the logical host in question is used in a cluster system, execute the command on the primary node. The backed-up common definition information must be restored on both the primary server and the secondary server.