G.1 Preparation for migration
This appendix describes the preparation that is needed before you can migrate the performance data that was collected by PFM - Agent for Virtual Machine and the properties of the Collector and Store services.
- Organization of this subsection
(1) Overview of migration
The following shows an overview of migration.
|
|
![[Figure]](GRAPHICS/ZUFRKG00.GIF)
(2) Considering the operating environment and migration method
(a) Operating environment
Examine and consider the following items which form the environment for executing the migration command:
-
System configuration
-
PFM - Agent for Virtual Machine configurations
-
Scale of the Store database
■ System configuration
Check whether PFM - Agent for Virtual Machine is in a cluster configuration or in a non-cluster configuration.
■ PFM - Agent for Virtual Machine configurations
Check the PFM - Agent for Virtual Machine configurations, such as the network configuration, performance data collection interval (and offset), JP1 events, and settings for automatically restarting the PFM service.
■ Scale of the Store database
Check the scale of the Store database.
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.
The migration command has a function that calculates the size that the database will have if migration is performed. Before migration, use this function to check whether the database size will exceed the maximum. For details about the size check function of the migration command, see the description of the -sizecheck option in G.5 Command reference.
(b) Migration methods
Decide the method you will use to migrate the Store database.
There are three methods that can be used to migrate the Store database.
|
|
![[Figure]](GRAPHICS/ZUFRKG01.GIF)
- Migration method 1:
-
The Store database of PFM - Agent for Virtual Machine is directly migrated to the Store database of PFM - RM for Virtual Machine.
Because the Store databases are directly accessed to read and write the data, the services of the PFM - Agent for Virtual Machine and PFM - RM for Virtual Machine instances must be stopped.
- Migration method 2:
-
A backup file for the Store database of PFM - Agent for Virtual Machine is first created, and then the backup file is used to migrate the data to the Store database of PFM - RM for Virtual Machine.
During migration, although you need to stop the service of the PFM - RM for Virtual Machine instance, you do not need to stop the service of the PFM - Agent for Virtual Machine instance.
- Migration method 3:
-
A backup file for the Store database of PFM - Agent for Virtual Machine is first created, and then, from the backup file, the data is migrated to the backup directory of PFM - RM for Virtual Machine.
The data in the migrated backup file becomes available by importing the file into PFM - RM for Virtual Machine.
During migration, you do not need to stop the services of the PFM - Agent for Virtual Machine and PFM - RM for Virtual Machine instances. The backup file can be imported while the system is operating stably.
With this method, both migration-source and migration-destination backup files might contain data collected at the same point in time. In such a case, the data collected by PFM - RM for Virtual Machine takes precedence on a daily basis.
In addition to the above three methods, there is a method to migrate only the instance and monitoring target definitions. For example, you can use this method to start operating PFM - RM for Virtual Machine without migrating the Store database. Alternatively you can use this method to import a backup file migrated by method 3 into an instance environment after migrating the definitions.
(3) Updating the version of PFM - Agent for Virtual Machine
The version of migration-source PFM - Agent for Virtual Machine must be 09-01 or later. If the version is 09-00 or earlier, update it to 09-01 or later. If the backup file to be migrated was created by 09-00 or an earlier version, convert the data model by executing the jpctool db dmconvert command.
(4) Updating the version of the Store database
The Store version of the PFM - Agent for Virtual Machine instance environment must be 2.0. If the Store version is 1.0, you must update it to 2.0 before migration by executing the jpcconf db vrset command.