G.8 Examples of executing the migration command

This appendix shows examples of executing the migration command in a non-cluster environment. If you execute the command in a cluster environment, add the -aolhost and -rmlhost options to specify the names of the source and destination logical hosts respectively.

Organization of this subsection

(1) Migrating only instance and monitoring target definitions
(2) Migrating between Store databases
(3) Migrating from a backup file to a Store database
(4) Migrating between backup files
(5) Checking whether the size of a Store database file will exceed 2,048 MB after migration
(6) Performing migration if the size of a Store database will exceed 2,048 MB after migration
(7) Measures to take if the destination disk capacity is insufficient

(1) Migrating only instance and monitoring target definitions

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

(a) Migrating to a new instance

In this example, you create a new PFM - RM for Virtual Machine instance, and migrate the PFM - Agent for Virtual Machine instance named inst1 to the new instance. The new instance is named newinst, and the instance inst1 is migrated as target1. The following figure shows an overview of this migration.

Figure G‒3: Overview of migrating to a new instance

The following shows an example of executing the migration command.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm defineonly -aoinst inst1 -rminst newinst -target target1
KAVL20403-I Start the migration process.
KAVL20400-I The instance was successfully transitioned. (inst1 -> newinst / target1)
KAVL20401-I If you are changing location of the performance data, JP1 Event and PFM service automatic restart in the source environment, please review the target environment.

A new PFM - RM for Virtual Machine instance named newinst was created, and the environment was migrated to that instance.

(b) Migrating to an existing instance (add-migration that does not update definitions)

In this example, you migrate a PFM - Agent for Virtual Machine instance to an existing PFM - RM for Virtual Machine instance. The source instance inst2 is added as target2 to the destination instance newinst. The definitions of the destination (PFM - RM for Virtual Machine) instance are not updated.

The following figure shows an overview of this migration.

Figure G‒4: Overview of migrating to an existing instance (add-migration that does not update definitions)

The following shows an example of executing the migration command.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm defineonly -aoinst inst2 -rminst newinst -target target2 -targetadd
KAVL20403-I Start the migration process.
KAVL20400-I The instance was successfully transitioned. (inst2 -> newinst / target2)
KAVL20402-I If you set the some targets to one instance, please review the value of 'Collection Interval'.

A monitoring target was added to the existing PFM - RM for Virtual Machine instance newinst. In this case, the definitions of this instance have not been updated. For an example of migration that updates the destination instance definitions with the source instance definitions, see G.8(1)(c) Migrating to an existing instance (add-migration that updates definitions).

(c) Migrating to an existing instance (add-migration that updates definitions)

In this example, you migrate a PFM - Agent for Virtual Machine instance to an existing PFM - RM for Virtual Machine instance. The definitions of the destination (PFM - RM for Virtual Machine) instance are updated with the definitions of the source (PFM - Agent for Virtual Machine) instance.

The following figure shows an overview of this migration.

Figure G‒5: Overview of migrating to an existing instance (add-migration that updates definitions)

The following shows an example of executing the migration command.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm defineonly -aoinst inst2 -rminst newinst -target target2 -targetadd -instupdate
KAVL20403-I Start the migration process.
KAVL20400-I The instance was successfully transitioned. (inst1 -> newinst / target1)
KAVL20401-I If you are changing location of the performance data, JP1 Event and PFM service automatic restart in the source environment, please review the target environment.
KAVL20402-I If you set the some targets to one instance, please review the value of 'Collection Interval'.

A monitoring target was added to the existing PFM - RM for Virtual Machine instance newinst. In this case, the definitions of this instance have been updated with the definitions of the source (PFM - Agent for Virtual Machine) instance. For an example of migration that does not update the destination instance definitions, see G.8(1)(b) Migrating to an existing instance (add-migration that does not update definitions).

(d) Migrating to a new instance by setting the Target Host property

This method is used if the VM_Host value of the migration-source (PFM - Agent for Virtual Machine) instance is not 1 through 32 bytes long or includes characters that are not single-byte alphanumeric characters or hyphens (-). In this case, the Target Host property must be set for the monitoring target of the PFM - RM for Virtual Machine instance.

In this example, you migrate a source instance whose VM_Host value is VM_A to a new PFM - RM for Virtual Machine instance by setting the Target Host property to VM-A. The following figure shows an overview of this migration.

Figure G‒6: Overview of migrating to a new instance by setting the Target Host property

The following shows an example of executing the migration command.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm defineonly -aoinst instA -rminst newinst2 -target targetA -targethost VM-A
KAVL20403-I Start the migration process.
KAVL20400-I The instance was successfully transitioned. (instA -> newinst2 / targetA)
KAVL20401-I If you are changing location of the performance data, JP1 Event and PFM service automatic restart in the source environment, please review the target environment.

The environment was migrated by setting a Target Host value. Note that you do not need to change the host name of the monitored virtual environment.

(e) Migrating to an existing instance by setting the Target Host property

In this example, you migrate a source instance whose VM_Host value is VM_A, adding it to an existing PFM - RM for Virtual Machine instance by setting the Target Host property to VM-A. The following figure shows an overview of this migration.

Figure G‒7: Overview of migrating to an existing instance by setting the Target Host property

The following shows an example of executing the migration command.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm defineonly -aoinst instA -rminst newinst -target targetA -targetadd -targethost VM-A
KAVL20403-I Start the migration process.
KAVL20400-I The instance was successfully transitioned. (instA -> newinst / targetA)
KAVL20401-I If you are changing location of the performance data, JP1 Event and PFM service automatic restart in the source environment, please review the target environment.

The environment was migrated by setting a Target Host value. Note that you do not need to change the host name of the monitored virtual environment.

To Page Top

(2) Migrating between Store databases

You can migrate the Store database of a PFM - Agent for Virtual Machine instance directly to the Store database of a PFM - RM for Virtual Machine instance.

Because the services of the migration source and destination instances must be stopped, this method is suited for migration of a small-scale environment.

To use this method, specify the store2store subcommand.

(a) Migrating to a new instance

Figure G‒8: Overview of migrating to a new instance

The following shows an example of executing the migration command.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm store2store -aoinst inst1 -rminst newinst -target target1
KAVL20486-I Start to analyze the migration files. (Number of files=100)
100.00 % (  100 /   100)
KAVL20487-I End to analyze the migration files.
KAVL20403-I Start the migration process.
KAVL20452-I Start to migrate the Store database.
100.00 % (     500 /      500)
KAVL20453-I End to migrate the Store database.
KAVL20400-I The instance was successfully transitioned. (inst1 -> newinst / target1)
KAVL20401-I If you are changing location of the performance data, JP1 Event and PFM service automatic restart in the source environment, please review the target environment.

A new PFM - RM for Virtual Machine instance named newinst was created, and the environment was migrated to that instance.

(b) Migrating to an existing instance (add-migration that does not update definitions)

Figure G‒9: Overview of migrating to an existing instance (add-migration that does not update definitions)

The following shows an example of executing the migration command.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm store2store -aoinst inst2 -rminst newinst -target target2 -targetadd
KAVL20477-I Start to check the store DB size. (Number of files=100)
100.00 % (  100 /   100)
KAVL20478-I End to check the store DB size.
KAVL20403-I Start the migration process.
KAVL20449-I Start to backup the Store database of the specified PFM - RM for Virtual Machine.
KAVL20450-I End to backup the Store database of the specified PFM - RM for Virtual Machine.
KAVL20452-I Start to migrate the Store database.
100.00 % (     500 /      500)
KAVL20453-I End to migrate the Store database.
KAVL20400-I The instance was successfully transitioned. (inst2 -> newinst / target2)
KAVL20402-I If you set the some targets to one instance, please review the value of 'Collection Interval'.

A monitoring target was added to the existing PFM - RM for Virtual Machine instance newinst. In this case, the definitions of this instance have not been updated. For an example of migration that updates the destination instance definitions with the source instance definitions, see G.8(2)(c) Migrating to an existing instance (add-migration that updates definitions).

(c) Migrating to an existing instance (add-migration that updates definitions)

Figure G‒10: Overview of migrating to an existing instance (add-migration that updates definitions)

The following shows an example of executing the migration command.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm store2store -aoinst inst2 -rminst newinst -target target2 -targetadd -instupdate
KAVL20477-I Start to check the store DB size. (Number of files=100)
100.00 % (  100 /   100)
KAVL20478-I End to check the store DB size.
KAVL20403-I Start the migration process.
KAVL20449-I Start to backup the Store database of the specified PFM - RM for Virtual Machine.
KAVL20450-I End to backup the Store database of the specified PFM - RM for Virtual Machine.
KAVL20452-I Start to migrate the Store database.
100.00 % (     500 /      500)
KAVL20453-I End to migrate the Store database.
KAVL20400-I The instance was successfully transitioned. (inst2 -> newinst / target2)
KAVL20401-I If you are changing location of the performance data, JP1 Event and PFM service automatic restart in the source environment, please review the target environment.
KAVL20402-I If you set the some targets to one instance, please review the value of 'Collection Interval'.

A monitoring target was added to the existing PFM - RM for Virtual Machine instance newinst. In this case, the definitions of this instance have been updated with the definitions of the source (PFM - Agent for Virtual Machine) instance. For an example of migration that does not update the destination instance definitions, see G.8(2)(b) Migrating to an existing instance (add-migration that does not update definitions).

(d) Migrating to a new instance by setting the Target Host property

Figure G‒11: Overview of migrating to a new instance by setting the Target Host property

The following shows an example of executing the migration command.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm store2store -aoinst instA -rminst newinst2 -target targetA -targethost VM-A
KAVL20486-I Start to analyze the migration files. (Number of files=100)
100.00 % (  100 /   100)
KAVL20487-I End to analyze the migration files.
KAVL20403-I Start the migration process.
KAVL20452-I Start to migrate the Store database.
100.00 % (     500 /      500)
KAVL20453-I End to migrate the Store database.
KAVL20400-I The instance was successfully transitioned. (instA -> newinst2 / targetA)
KAVL20401-I If you are changing location of the performance data, JP1 Event and PFM service automatic restart in the source environment, please review the target environment.

The environment was migrated by setting a Target Host value. Note that you do not need to change the host name of the monitored virtual environment.

(e) Migrating to an existing instance by setting the Target Host property

Figure G‒12: Overview of migrating to an existing instance by setting the Target Host property

The following shows an example of executing the migration command.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm store2store -aoinst instA -rminst newinst -target targetA -targetadd -targethost VM-A
KAVL20477-I Start to check the store DB size. (Number of files=100)
100.00 % (  100 /   100)
KAVL20478-I End to check the store DB size.
KAVL20403-I Start the migration process.
KAVL20449-I Start to backup the Store database of the specified PFM - RM for Virtual Machine.
KAVL20450-I End to backup the Store database of the specified PFM - RM for Virtual Machine.
KAVL20452-I Start to migrate the Store database.
100.00 % (     500 /      500)
KAVL20453-I End to migrate the Store database.
KAVL20400-I The instance was successfully transitioned. (instA -> newinst / targetA)
KAVL20402-I If you set the some targets to one instance, please review the value of 'Collection Interval'.

The environment was migrated by setting a Target Host value. Note that you do not need to change the host name of the monitored virtual environment.

To Page Top

(3) Migrating from a backup file to a Store database

You can first create a backup file for the Store database of PFM - Agent for Virtual Machine, and then migrate data from the backup file to the Store database of PFM - RM for Virtual Machine.

Before starting migration, you must back up the PFM - Agent for Virtual Machine instance that you want to migrate.

You must stop the service of the migration destination instance, but you do not need to stop the service of the migration source instance.

To use this method, specify the backup2store subcommand.

(a) Migrating to a new instance

Figure G‒13: Overview of migrating to a new instance

Create a backup file for the Store database of the instance that you want to migrate. For an example of creating a backup file, see G.2(1) Backing up the source Store database. The following is an example of executing the migration command when a backup file for the Store database is located in C:\Program Files\Hitachi\jp1pc\agt5\store\inst1\backup\01.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm backup2store -aobkpath 
"C:\Program Files\Hitachi\jp1pc\agt5\store\inst1\backup\01" -rminst newinst -target target1
KAVL20486-I Start to analyze the migration files. (Number of files=100)
100.00 % (  100 /   100)
KAVL20487-I End to analyze the migration files.
KAVL20403-I Start the migration process.
KAVL20452-I Start to migrate the Store database.
100.00 % (     500 /      500)
KAVL20453-I End to migrate the Store database.
KAVL20400-I The instance was successfully transitioned. (inst1 -> newinst / target1)
KAVL20401-I If you are changing location of the performance data, JP1 Event and PFM service automatic restart in the source environment, please review the target environment.

A new PFM - RM for Virtual Machine instance named newinst was created, and the environment was migrated to that instance.

(b) Migrating to an existing instance (add-migration that does not update definitions)

Figure G‒14: Overview of migrating to an existing instance (add-migration that does not update definitions)

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm backup2store -aobkpath 
"C:\Program Files\Hitachi\jp1pc\agt5\store\inst2\backup\01" -rminst newinst -target target2 -targetadd
KAVL20477-I Start to check the store DB size. (Number of files=100)
100.00 % (  100 /   100)
KAVL20478-I End to check the store DB size.
KAVL20403-I Start the migration process.
KAVL20449-I Start to backup the Store database of the specified PFM - RM for Virtual Machine.
KAVL20450-I End to backup the Store database of the specified PFM - RM for Virtual Machine.
KAVL20452-I Start to migrate the Store database.
100.00 % (     500 /      500)
KAVL20453-I End to migrate the Store database.
KAVL20400-I The instance was successfully transitioned. (inst2 -> newinst / target2)
KAVL20402-I If you set the some targets to one instance, please review the value of 'Collection Interval'.

A monitoring target was added to the existing PFM - RM for Virtual Machine instance newinst. In this case, the definitions of this instance have not been updated. For an example of migration that updates the destination instance definitions with the source instance definitions, see G.8(3)(c) Migrating to an existing instance (add-migration that updates definitions).

(c) Migrating to an existing instance (add-migration that updates definitions)

Figure G‒15: Overview of migrating to an existing instance (add-migration that updates definitions)

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm backup2store -aobkpath 
"C:\Program Files\Hitachi\jp1pc\agt5\store\inst2\backup\01" -rminst newinst -target target2 -targetadd -instupdate
KAVL20477-I Start to check the store DB size. (Number of files=100)
100.00 % (  100 /   100)
KAVL20478-I End to check the store DB size.
KAVL20403-I Start the migration process.
KAVL20449-I Start to backup the Store database of the specified PFM - RM for Virtual Machine.
KAVL20450-I End to backup the Store database of the specified PFM - RM for Virtual Machine.
KAVL20452-I Start to migrate the Store database.
100.00 % (     500 /      500)
KAVL20453-I End to migrate the Store database.
KAVL20400-I The instance was successfully transitioned. (inst2 -> newinst / target2)
KAVL20401-I If you are changing location of the performance data, JP1 Event and PFM service automatic restart in the source environment, please review the target environment.
KAVL20402-I If you set the some targets to one instance, please review the value of 'Collection Interval'.

A monitoring target was added to the existing PFM - RM for Virtual Machine instance newinst. In this case, the definitions of this instance have been updated with the definitions of the source (PFM - Agent for Virtual Machine) instance. For an example of migration that does not update the destination instance definitions, see G.8(3)(b) Migrating to an existing instance (add-migration that does not update definitions).

(d) Migrating to a new instance by setting the Target Host property

Figure G‒16: Overview of migrating to a new instance by setting the Target Host property

Create a backup file for the Store database of the instance that you want to migrate. For an example of creating a backup file, see G.2(1) Backing up the source Store database. The following is an example of executing the migration command when a backup file for the Store database named StoreA is located in C:\Program Files\Hitachi\jp1pc\agt5\store\instA\backup\01.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm backup2store -aobkpath 
"C:\Program Files\Hitachi\jp1pc\agt5\store\instA\backup\01" -rminst newinst2 -target targetA -targethost VM-A
KAVL20486-I Start to analyze the migration files. (Number of files=100)
100.00 % (  100 /   100)
KAVL20487-I End to analyze the migration files.
KAVL20403-I Start the migration process.
KAVL20452-I Start to migrate the Store database.
100.00 % (     500 /      500)
KAVL20453-I End to migrate the Store database.
KAVL20400-I The instance was successfully transitioned. (instA -> newinst2 / targetA)
KAVL20401-I If you are changing location of the performance data, JP1 Event and PFM service automatic restart in the source environment, please review the target environment.

The environment was migrated by setting a Target Host value. Note that you do not need to change the host name of the monitored virtual environment.

(e) Migrating to an existing instance by setting the Target Host property

Figure G‒17: Overview of migrating to an existing instance by setting the Target Host property

Create a backup file for the Store database of the instance that you want to migrate. For an example of creating a backup file, see G.2(1) Backing up the source Store database. The following is an example of executing the migration command when a backup file for the Store database named StoreA is located in C:\Program Files\Hitachi\jp1pc\agt5\store\instA\backup\01.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm backup2store -aobkpath 
"C:\Program Files\Hitachi\jp1pc\agt5\store\instA\backup\01" -rminst newinst -target targetA -targetadd -targethost VM-A
KAVL20477-I Start to check the store DB size. (Number of files=100)
100.00 % (  100 /   100)
KAVL20478-I End to check the store DB size.
KAVL20403-I Start the migration process.
KAVL20449-I Start to backup the Store database of the specified PFM - RM for Virtual Machine.
KAVL20450-I End to backup the Store database of the specified PFM - RM for Virtual Machine.
KAVL20452-I Start to migrate the Store database.
100.00 % (     500 /      500)
KAVL20453-I End to migrate the Store database.
KAVL20400-I The instance was successfully transitioned. (instA -> newinst / targetA)
KAVL20402-I If you set the some targets to one instance, please review the value of 'Collection Interval'.

The environment was migrated by setting a Target Host value. Note that you do not need to change the host name of the monitored virtual environment.

To Page Top

(4) Migrating between backup files

You can first create a backup file for the Store database of PFM - Agent for Virtual Machine, and then migrate data from the backup file to the backup directory of PFM - RM for Virtual Machine.

Before starting migration, you must back up the PFM - Agent for Virtual Machine instance that you want to migrate.

You do not need to stop the service of the migration source instance or the migration destination instance.

To use this method, specify the backup2backup subcommand.

With this method, you perform migration by importing a backup file. This means that you can perform migration while both the source (PFM - Agent for Virtual Machine) instance and the destination (PFM - RM for Virtual Machine) instance are running. After you have confirmed stable operation of the destination instance, you can migrate and view the contents of the Store database. The following figure shows an overview of this migration.

Figure G‒18: Overview of migrating between backup files

Note that if you use this method in which both the source and destination instances are running concurrently, you must perform migration in two stages: instance definition migration and data migration.

First, perform migration of instance definitions. For details about the procedure, see G.8(1) Migrating only instance and monitoring target definitions. After this migration succeeds, start the PFM - Agent for Virtual Machine and PFM - RM for Virtual Machine services concurrently. Then, when stable operation of PFM - RM for Virtual Machine is confirmed, proceed to the next stage, data migration.

In this stage, you first create a backup file of the Store database on the PFM - Agent for Virtual Machine side, and then perform migration to the backup directory of PFM - RM for Virtual Machine. The following shows an example of this migration.

(a) Example of executing the migration command with the backup2backup subcommand specified

In this example, you migrate a backup file of the PFM - Agent for Virtual Machine instance inst1 to PFM - RM for Virtual Machine. This example assumes that the monitoring target target1 has already been created in PFM - RM for Virtual Machine by migrating the instance inst1. For details about how to migrate only definitions, see G.8(1) Migrating only instance and monitoring target definitions.

The following figure shows an overview of this migration.

Figure G‒19: Overview of migrating to a new instance

The following is an example of executing the migration command when a backup file for the Store database named Store1 is located in C:\Program Files\Hitachi\jp1pc\agt5\store\inst1\backup\01. Note that the backup directory specified for the -rmbkpath option must be empty.

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm backup2backup -aobkpath 
"C:\Program Files\Hitachi\jp1pc\agt5\store\inst1\backup\01" -rmbkpath 
"C:\rm4vm\inst1\backup" -rminst newinst -target target1
KAVL20486-I Start to analyze the migration files. (Number of files=100)
100.00 % (  100 /   100)
KAVL20487-I End to analyze the migration files.
KAVL20403-I Start the migration process.
KAVL20452-I Start to migrate the Store database.
100.00 % (     500 /      500)
KAVL20453-I End to migrate the Store database.
KAVL20400-I The instance was successfully transitioned. (inst1 -> newinst / target1)

The backup file was migrated to the backup folder of PFM - RM for Virtual Machine.

For the migrated data to be viewed with PFM - RM for Virtual Machine, import the backup file to PFM - RM for Virtual Machine. The following shows a command execution example.

C:\Program Files\Hitachi\jp1pc\tools\ jpctool db import -key RMVM -inst newinst -d "C:\rm4vm\inst1\backup" -add
KAVE05841-I Import processing of the Store database will now start. (servicekey=RMVM, inst=newinst, dir=C:\rm4vm\inst1\backup)
KAVE05842-I Store database import processing ended normally. (servicekey=RMVM, inst=newinst, dir=C:\rm4vm\inst1\backup)

The backup file was imported. The imported data can now be viewed from PFM - RM for Virtual Machine. You can delete the backup file.

To Page Top

(5) Checking whether the size of a Store database file will exceed 2,048 MB after migration

Because the Store database of PFM - RM for Virtual Machine has a more extended format than the Store database of PFM - Agent for Virtual Machine, the size of the Store database increases after migration. The size of the Store database also increases when multiple instances of PFM - Agent for Virtual Machine are integrated into one instance of PFM - RM for Virtual Machine. Note that migration is impossible if one of the database files that make up the destination Store database becomes larger than 2,048 MB.

You can use the migration command to check whether migration is possible before you perform migration.

To do this, add the -sizecheck option when executing the migration command with the store2store or backup2store subcommand. If this option is specified, the command only checks whether migration is possible, and does not perform migration of definitions, the Store database, or a backup file.

Note that you can specify the -sizecheck option only when you perform migration to an existing instance.

The following shows command execution examples:

If the sizes of no database files will exceed 2,048 MB after migration:

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm store2store -aoinst inst1 -rminst newinst -target target1 -targetadd -sizecheck
KAVL20404-I Be calculating of the size of post-migration Store database (inst1 -> newinst)
KAVL20477-I Start to check the store DB size. (Number of files=100)
100.00 % (  100 /   100)
KAVL20478-I End to check the store DB size.
KAVL20406-I Finished to calculate size of the Store database. You can do the migration because Store database capacity after migration is less than maximum migration capacity.

If the size of at least one database file will exceed 2,048 MB after migration:

C:\Program Files\Hitachi\jp1pc\agt8\tools>jpcaovm2rmvm store2store -aoinst inst2 -rminst newinst -target target1 -targetadd -sizecheck
KAVL20404-I Be calculating of the size of post-migration Store database (inst1 -> newinst)
KAVL20477-I Start to check the store DB size. (Number of files=100)
50.00 % (   50 /   100)
KAVL20407-I Finished to calculate size of the Store database. You cannot do the migration because Store database capacity after migration is more than maximum migration capacity. As destination, please specify a new instance or another instance with spare Store database.

An attempt to migrate the Store database additionally to an existing PFM - RM for Virtual Machine instance fails if the size of a Store database file exceeds 2,048 MB. If the size that a Store database file will have after migration exceeds 2,048 MB, you need to perform migration in another way. For details, see G.8(6) Performing migration if the size of a Store database will exceed 2,048 MB after migration.

To Page Top

(6) Performing migration if the size of a Store database will exceed 2,048 MB after migration

However, you can ignore the 2,048 MB limitation when migrating a backup file (by executing the migration command with the backup2backup subcommand) and importing that file (by using the jpctool db import command).

If migration is impossible, try any of the following measures:

Specify another instance as the migration destination.

Specify a new instance for the -rminst option.

If you have to specify an existing instance, make sure that the Store database of that instance has sufficient capacity.
Migrate only definitions without migrating the database.

If migration of the Store database or a backup file is unnecessary, you can migrate the definitions only. For how to add a monitoring target without updating instance definitions, see G.8(1)(b) Migrating to an existing instance (add-migration that does not update definitions). For how to add a monitoring target by updating instance definitions, see G.8(1)(c) Migrating to an existing instance (add-migration that updates definitions).

To Page Top

(7) Measures to take if the destination disk capacity is insufficient

Migration of the Store database or a backup file from PFM - Agent for Virtual Machine to PFM - RM for Virtual Machine requires more disk space. If migration is impossible because the destination disk does not have sufficient free space, try any of the following measures:

Secure sufficient free disk space.

Secure free disk space that is large enough for migration by, for example, deleting unnecessary files or adding a disk.
Perform migration of only definitions without migrating the database.

If migration of the Store database or a backup file is unnecessary, you can migrate the definitions only. For how to add a monitoring target without updating instance definitions, see G.8(1)(b) Migrating to an existing instance (add-migration that does not update definitions). For how to add a monitoring target by updating instance definitions, see G.8(1)(c) Migrating to an existing instance (add-migration that updates definitions).

To Page Top