G.2 Migration in a non-cluster environment
This appendix describes the procedure for migration in a non cluster-environment. Perform the necessary steps for each instance to be migrated.
- Organization of this subsection
(1) Backing up the source Store database
If you use method 2 or 3 to migrate the Store database, create a backup file for the Store database of the instance that you want to migrate.
The following is an example of a command line that creates a backup file for the Store database in PFM - Agent for Virtual Machine.
C:\Program Files\Hitachi\jp1pc\tools> jpctool db backup -id 5S1inst1[aovmhost] KAVE06000-I Backup processing of the Store database terminated normally. (service=5S1inst1[aovmhost])
(2) Backing up the destination Store database
If you perform migration by adding a monitoring target to an existing instance environment, make sure that you back up the Store database of the migration-destination instance. (This is in case of a failure.)
The following is an example of a command line that creates a backup file for the Store database in PFM - RM for Virtual Machine.
C:\Program Files\Hitachi\jp1pc\tools> jpctool db backup -id 8S1newinst[rmvmhost] KAVE06000-I Backup processing of the Store database terminated normally. (service=8S1newinst[rmvmhost])
(3) Migrating the instance
Use the migration command to migrate the instance.
For details about how to use the migration command, see G.8 Examples of executing the migration command. For details about the migration command, see G.5 Command reference.
(4) Performing post-migration setup
After migrating the Store database, perform the following tasks, if necessary:
(a) Specifying the network environment settings
Specify the IP address, port number, and other settings. For details about the network environment settings, see 2.1.4(6) Network settings.
(b) Setting the performance data storage destination
You can set the performance data storage destination if you want to store performance data somewhere other than the default storage destination. For details about setting the performance data storage destination, see 2.4.1 Changing the performance data storage destination.
The following is an example of a command line that changes the performance data storage destination.
C:\Program Files\Hitachi\jp1pc\tools> jpcconf db define -key RMVM -inst newinst -sd "c:\Store" -move KAVE05856-I Updating the configuration information of the Store database ended normally. (servicekey=RMVM, inst=newinst, label=Store Dir)
(c) Setting the performance data collection interval and the start-time offset
You can set the performance data collection interval (Collection Interval) and collection start-time offset (Collection Offset). To specify these settings, use PFM - Web Console.
The default collection interval of PFM - Agent for Virtual Machine is 60 seconds, whereas the default Interval value of the PFM - RM for Virtual Machine collection process is 300 seconds. If there are problems with the collection interval and offset settings, a KAVL20516-W error is reported.
To avoid this error, make sure that the Interval value does not exceed the Collection Interval value. If the error occurs frequently even when the Interval value does not exceed the Collection Interval value, increase the Collection Interval value or reduce the number of hosts monitored in the instance environment.
For details about the performance data collection interval and offset settings, see the chapter on designing an operation monitoring system in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
For details about the Interval setting for the collection process, see 1.3.1 General procedure for performance data collection tasks.
(d) Other necessary settings
Other settings, such as alarm and report definitions, must also be specified. Specify these necessary settings by referring to the settings that were specified during PFM - Agent for Virtual Machine environment setup.