Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference

jimdbrecovery

Function

This command recovers a database from its backup. The command can recover the following types of data:

Recovery for error recovery

In the event of a database failure, the command recovers the database from backup data that was acquired previously. The command recovers only the backup data without using system logs.

Recovery for expansion

Before you expand the size of a database, temporarily back up the data. The databases you need to back up are the integrated monitoring database area and the IM Configuration Management database area.

As part of expanding the size of a database, the command recovers the database from the backup data that was created temporarily.

Format

jimdbrecovery -i backup-file-name
                -m {MAINT|EXPAND}
                [-h logical-host-name]
                [-q]

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

Storage directory

In Windows:

Manager-path\bin\imdb\

In UNIX:

/opt/jp1imm/bin/imdb/

Arguments

-i backup-file-name

Specifies the absolute path name of the file to which the database was backed up by the jimdbbackup command. You must specify a logical drive for the backup file. This option is mandatory.

An error results if you specify a network drive, a UNC path, or a Windows reserved device file.

-m {MAINT|EXPAND}

Specifies the database recovery format. The permitted characters are upper-case letters. This option is mandatory.

• MAINT: Specifies recovery for error recovery
• EXPAND: Specifies recovery for expansion

When you execute recovery for error recovery, specify the backup file that was acquired by a backup for error recovery; when you execute recovery for expansion, specify the backup file that was acquired by a backup for expansion. An error results if the specified argument does not match the type of backup file.

-h logical-host-name

When you are operating in a cluster system, this option specifies the logical host name of the host where the command is executed. The command recovers the database that corresponds to the specified logical host. If this option is omitted, the logical host name specified in the JP1_HOSTNAME environment variable is assumed. If the JP1_HOSTNAME environment variable is not specified, the physical host name is assumed. If you are not using a cluster system, specification of this option is not needed. Note that this logical host name cannot be JP1_DEFAULT.

-q

Specifies that the command is to be executed without requesting confirmation from the user.

Return values

0	Recovery terminated normally
1	Recovery terminated abnormally

Notes

• When you execute the jimdbrecovery command to recover backup data acquired by the jimdbbackup command, use the same OS that was used to make the backup. If the backup is recovered to a database under a different OS, the integrity of the operation cannot be guaranteed.
• If you execute another JP1/IM - Manager command or start a JP1/IM - Manager service while this command is executing, the requested execution might fail because this command places the database in the mode that disables referencing and updating.
• While this command is executing, do not press Ctrl +C or Ctrl + Break. Because the command executes recovery processing in the background, the recovery processing will continue even though Ctrl +C or Ctrl + Break is pressed. If you press Ctrl +C or Ctrl + Break and then immediately attempt to execute another JP1/IM - Manager command or start a JP1/IM - Manager service, execution of the requested command or startup of the requested service might fail.
  If you have canceled command execution by pressing Ctrl +C or Ctrl + Break during error recovery processing, make sure that the pdrstr process is not running before you restart JP1/IM - Manager. If you have canceled command execution by pressing Ctrl +C or Ctrl + Break during a recovery for expansion, make sure that the pdrorg process is not running before you start another command or a JP1/IM - Manager service.
  
• This command creates a temporary file during execution. In the case of a recovery for expansion, the amount of free space that is needed on the drive at the installation target is about 1 gigabyte for a small or medium-sized database and about 4 gigabytes for a large database. In the case of a recovery for error recovery, the amount of free space that is needed on the drive at the installation target is from about 5 to 50 megabytes regardless of the database size.
• When you execute a recovery for error recovery, the database storage directory used to execute the backup for error recovery must be the same as the database storage directory used to execute the recovery for error recovery.
• When you execute a recovery for expansion, the storage space must be larger than when the backup for expansion was executed.
• Recovery for expansion might fail if the available capacity is the same as for the backup for expansion. If this occurs, set up the database again and then, with the database free of data, recover the database.
• When the IM database is used, JP1/IM - Manager must not be running.
• In Windows, the IM database (JP1/IM-Manager DB Server) must be running and the cluster service for the IM database (JP1/IM-Manager DB Cluster Service) must be stopped.

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.