G.5 Command reference

defineonly
   -aoinst <PFM - Agent for Virtual Machine instance name>
   -rminst <PFM - RM for Virtual Machine instance name>
   -target <PFM - RM for Virtual Machine monitoring-target-name>
   [-targethost <Target Host>]
   [-aolhost PFM-Agent-for-Virtual-Machine-logical-host-name [-rmlhost PFM-RM-for-Virtual-Machine-logical-host-name]]
   [-targetadd [-instupdate]]

The defineonly subcommand migrates only the instance and monitoring target definitions.

Specify this subcommand if you want to start operation of PFM - RM for Virtual Machine without migrating the Store database. You can also specify this subcommand when running both PFM - Agent for Virtual Machine (migration source) and PFM - RM for Virtual Machine (migration destination), and then importing data from the source to the destination.

• Before you execute the migration command with the defineonly subcommand specified, you must stop the service of the migration-target instance.

• If the -targetadd option is not specified, the specified instance environment and monitoring target are created when migration is performed.

• If the -targetadd option is specified, the specified monitoring target is added to an existing instance environment at the migration destination.

store2store
   -aoinst <PFM - Agent for Virtual Machine instance name>
   -rminst <PFM - RM for Virtual Machine instance name>
   -target <PFM - RM for Virtual Machine monitoring-target-name>
   [-targethost <Target Host>]
   [-aolhost PFM-Agent-for-Virtual-Machine-logical-host-name [-rmlhost PFM-RM-for-Virtual-Machine-logical-host-name]]
   [-targetadd [-instupdate]]
   [-sizecheck]

The Store database of PFM - Agent for Virtual Machine is directly migrated to the Store database of the PFM - RM for Virtual Machine.

Because direct read and write operations are performed on these Store databases, the services of both the PFM - Agent for Virtual Machine and PFM - RM for Virtual Machine instances must be stopped. For this reason, this method is suited for migration of a small-scale environment.

• Before you execute the migration command with the store2store subcommand specified, you must stop the services of both the migration-source and migration-target instances.

• If the -targetadd option is not specified, the specified instance environment and monitoring target are created when migration is performed.

• If the -targetadd option is specified, the specified monitoring target is added to an existing instance environment at the migration destination.

backup2store
   -aobkpath PFM-Agent-for-Virtual-Machine's-Store-database-backup-directory
   -rminst <PFM - RM for Virtual Machine instance name>
   -target PFM-RM-for-Virtual-Machine-monitoring-target-name
   [-targethost target-host]
   [-aolhost PFM-Agent-for-Virtual-Machine-logical-host-name [-rmlhost PFM-RM-for-Virtual-Machine-logical-host-name]]
   [-targetadd [-instupdate]]
   [-sizecheck]

A backup file for the Store database of PFM - Agent for Virtual Machine is created. Then data is migrated from that file to the Store database of PFM - RM for Virtual Machine.

This method is suited when you want to perform migration without stopping the service of the source instance.

• Before you execute the migration command with the backup2store subcommand specified, you must stop the service of the migration-target instance. (You do not need to stop the service of the migration-source instance.)

• If the -targetadd option is not specified, the specified instance environment and monitoring target are created when migration is performed.

• If the -targetadd option is specified, the specified monitoring target is added to an existing instance environment at the migration destination.

backup2backup
   -aobkpath PFM-Agent-for-Virtual-Machine's-Store-database-backup-directory
   -rmbkpath PFM-RM-for-Virtual-Machine's-Store-database-backup-directory
   -rminst <PFM - RM for Virtual Machine instance name>
   -target PFM-RM-for-Virtual-Machine-monitoring-target-name
   [-aolhost PFM-Agent-for-Virtual-Machine-logical-host-name [-rmlhost PFM-RM-for-Virtual-Machine-logical-host-name]]

A backup file for the Store database of PFM - Agent for Virtual Machine is created. Then data is migrated from that file to the backup directory of PFM - RM for Virtual Machine.

The data migrated to the backup directory is then imported to PFM - RM for Virtual Machine.

With this method, you do not need to stop the services of the migration-source and migration-destination instances. You can perform migration while both PFM - Agent for Virtual Machine and PFM - RM for Virtual Machine are running concurrently.

• You do not need to stop the services of the migration-source and migration-destination instances before executing the migration command with the backup2backup subcommand specified.

• Make sure that the instance you specify for the -rminst option and the monitoring target you specify for the -target option exist before executing the migration command.

-aoinst <PFM - Agent for Virtual Machine instance name>

Use this option to specify the name of the migration-source PFM - Agent for Virtual Machine instance. The string that you specify must be 1 through 32 bytes long and can have single-byte alphanumeric characters.

-aobkpath PFM-Agent-for-Virtual-Machine's-Store-database-backup-directory-path

Use this option to specify the path of the backup directory for the Store database of the migration-source PFM - Agent for Virtual Machine instance. You can specify either an absolute path or relative path. In both cases, the path length must be 1 through 214 bytes. If you specify a relative path, its actual path (absolute path) must also be 1 through 214 bytes long. When you specify a relative path, the directory that is the current directory when the command is executed is the base directory. You can specify only a directory on the local disk.

-rmbkpath PFM-RM-for-Virtual-Machine's-Store-database-backup-directory-path

Use this option to specify the path of the backup directory for the Store database of the migration-destination PFM - RM for Virtual Machine instance. You can specify either an absolute path or relative path. In both cases, the path length must be 1 through 214 bytes. If you specify a relative path, its actual path (absolute path) must also be 1 through 214 bytes long. When you specify a relative path, the directory that is the current directory when the command is executed is the base directory. You can specify only a directory on the local disk.

The migration-destination directory must be empty. If it is not empty, an error occurs.

-rminst <PFM - RM for Virtual Machine instance name>

Use this option to specify the name of the PFM - RM for Virtual Machine instance that you want to create or update, or for which you want to set a monitoring target. The string that you specify must be 1 through 32 bytes long and can have single-byte alphanumeric characters.

• To add a monitoring target to an existing instance environment, use the -targetadd option, instead of using the -rminst option. If you specify the name of an existing instance for the -rminst option, an error occurs.

• When you specify an instance for the -rminst option of the backup2backup subcommand, make sure that the instance exists. If the instance does not exist, an error occurs.

-target PFM-RM-for-Virtual-Machine-monitoring-target-name

Use this option to specify a string that identifies a monitoring target of the instance. The string that you specify must be 1 through 32 bytes long, and can have single-byte alphanumeric characters and hyphens (-).

• If you specify the same name as the name of another monitoring target of the same instance, an error occurs.

• You cannot specify a monitoring target name that begins with a hyphen (-).

• When you specify the -target option of the backup2backup subcommand, make sure that the instance specified for the -rminst option exists. If the instance does not exist, an error occurs.

-targethost <Target Host>

Use this option to specify the name of the monitoring-target host that is the migration destination. The string that you specify must be 1 through 32 bytes long, and can have single-byte alphanumeric characters and hyphens (-).

• You cannot specify a monitoring-target host name that begins with a hyphen (-).

• If you omit specifying the monitoring-target host name, the VM_Host value of PFM - Agent for Virtual Machine will be used. However, if that value is not 1 through 32 bytes long or that value uses characters that are not single-byte alphanumeric characters or hyphens (-), an error occurs.

-aolhost PFM-Agent-for-Virtual-Machine-logical-host-name

Use this option to specify the name of the logical host that contains the migration-source PFM - Agent for Virtual Machine instance environment. The string that you specify must be 1 through 32 bytes long, and can have single-byte alphanumeric characters and hyphens (-).

• For the value of this option, you cannot specify the string localhost, an IP address, or a host name that begins with a hyphen (-).

• The string that you specify cannot include spaces and the following symbols:

  \ (backslash)

  / (slash)

  : (colon)

  ; (semicolon)

  * (asterisk)

  ? (question mark)

  " (double quotation mark)

  <> (angle brackets)

  | (vertical bar)

  . (period)

  = (equal sign)

• If you omit specifying a logical host name, the physical host name will be assumed.

-rmlhost PFM-RM-for-Virtual-Machine-logical-host-name

Use this option to specify the name of the PFM - RM for Virtual Machine logical host to which an instance environment will be added. The string that you specify must be 1 through 32 bytes long, and can have single-byte alphanumeric characters and hyphens (-).

• For the value of this option, you cannot specify the string localhost, an IP address, or a host name that begins with a hyphen (-).

• The string that you specify cannot include spaces and the following symbols:

  \ (backslash)

  / (slash)

  : (colon)

  ; (semicolon)

  * (asterisk)

  ? (question mark)

  " (double quotation mark)

  <> (angle brackets)

  | (vertical bar)

  . (period)

  = (equal sign)

• If you omit specifying a logical host name, the PFM - Agent for Virtual Machine logical host name specified for the -aolhost option will be assumed.

-targetadd

Specify this option to add a monitoring target to an existing PFM - RM for Virtual Machine instance environment.

• An attempt to migrate to an existing instance environment without specifying the -targetadd option results in an error.

• If the specified instance environment does not exist, an error occurs.

• When adding a monitoring target, make sure that the monitoring target you specify for the -targetadd option has not been deleted by using the jpcconf target unsetup command. If you specify the name of a deleted monitoring target, migration might fail. Specify a new monitoring target name or a new PFM - RM for Virtual Machine instance when performing migration.

-instupdate

Specify this option to update the definitions of an existing PFM - RM for Virtual Machine instance environment.

• When you specify the -instupdate option, you must also specify the -targetadd option.

• For the values that you can update, see G.7 Items that can be migrated when the -targetadd and -instupdate options are specified.

-sizecheck

Specify this option to output the results of checking how large the Store database and its backup file will be after migration. After command execution, a message indicating whether migration is possible is output. With the message, the user can determine whether migration is possible.

When the migration command is executed without the -sizecheck option, migration immediately starts if the Store database will not become so large that migration fails.