jimgndbrestore

Function

This command recovers Intelligent Integrated Management Database that was saved as a backup. The following are the types of data that can be recovered:

Disaster recovery

When a database failure occurs, the database is recovered using the backup data that is regularly acquired.

Migration recovery

When you migrate a JP1/IM - Manager to another host, you use the backed-up data to migrate the database.

The following shows Execute conditions for this command:

• Stopping the following services:

  • JP1/IM3-Manager

  • JP1/IM3-Manager Intelligent Integrated DB Server

  • JP1/IM3-Manager Trend Data Management Service

• Stopping the following services when using cluster systems:

  • JP1/IM3-Manager_logical-host-name

  • JP1/IM3-Manager Intelligent Integrated DB Server_logical-host-name

  • JP1/IM3-Manager Trend Data Management Service_logical-host-name

• If this command is run with the MAINT option for argument -m, the IM database must have been recovered using the jimdbrecovery command (with the MAINT option specified for the -m argument).

• Intelligent Integrated Management Database has been re-constructed.

To Page Top

Format

jimgndbrestore -i backup-filename
               -m {MAINT|TRANSF}
              [-h logical-hostname]
              [-q]

To Page Top

Execution permission

In Windows: Administrator permissions (if the Windows UAC feature is enabled, the command is executed from the administrator console)

In UNIX: Superuser permissions

To Page Top

Storage directory

In Windows:

Manager-path\bin\imgndb\

In UNIX:

/opt/jp1imm/bin/imgndb/

To Page Top

Arguments

-i backup-filename

Specifies the absolute pathname of File of the database that was backed up using jimgndbbackup command. Characters that can be used in File are alphanumeric characters and underscores (_), dots (.), sharps (#), and at signs (@). For the backup file, specify the local drive. This option cannot be omitted.

Error if a network drive is specified, UNC path is specified, and reserved device File is specified in Windows.

-m {MAINT|TRANSF}

Specifies the database recovery format. Characters that can be specified are uppercase single-byte characters. This option cannot be omitted.

• MAINT: Execute the disaster recovery.

• TRANSF: Execute the recovery for migration.

When you execute disaster recovery, specify the backup file that was collected in the backup for disaster recovery. When you execute the recovery for migration, specify the backup file that was collected in the backup for migration.

-h logical-hostname

Specifies logical host name of the host that execute the command when operating in a cluster system. The database is recovered for the specified logical host. If this option is omitted, logical host named in the environment variable JP1_HOSTNAME is assumed. If JP1_HOSTNAME is not specified, Physical host is assumed. If you are not using a cluster system, you do not need to specify it. Note that JP1_DEFAULT cannot be specified in a logical host.

-q

Specifies when you execute the command without user-confirmation.

To Page Top

Return values

To Page Top

Notes

• Before you Execute this command, make sure that Execute conditions for this command and jimgndbbackup command are met.

• Recovering the database may cause data inconsistency between the database and JP1/IM-Agent. To prevent the data inconsistency, stop JP1/IM-Agent before recovering the database.

• This command recovers only the data in the database. To prevent data inconsistency between backup data and the data added after the backup has been taken, you must first set up the database again before recovering the database. If data inconsistency occurs, the impact can be diverse, and it is difficult to later discover the data inconsistency. Therefore, be sure to set up the database again before performing a recovery.

• While this command is working, do not start service or any other commands of JP1/IM - Manager or JP1/IM - Agent. This command might fail because this command changes the database-browsing/updating state to prohibited.

• Do not press the Ctrl + C keys or the Ctrl + Break keys while this command is working. To execute the backup in the background, pressing Ctrl + C keys or Ctrl + Break keys will not stop the backup process. If you immediately execute a command or start service for another JP1/IM - Manager or JP1/IM - Agent after pressing Ctrl + C keys or Ctrl + Break keys, execute or service for those commands may fail.

• If the Ctrl + C keys or the Ctrl + Break keys are used to abort the process while this command is working, the process is turned Stopped, but the output message may be corrupted.

• Because the recovery files are indistinguishable for disaster recovery and migration, we recommend that you specify a distinguishable character for each File.

  The access permission for the recovery file is printed in Status that the user can access. After acquiring recovery, we recommend that you change the access permissions or move them to a location where users cannot access them.

• You cannot execute this command in multiple execution or concurrently with Intelligent Integrated Management Database operation commands. For details about Intelligent Integrated Management Database operation command multiplexing execute, see About multiple execution of the commands related to the Intelligent Integrated Management Database.

To Page Top