Appendix g: transporting thresholds, Movedb – HP NonStop G-Series User Manual
Page 103
Appendix G: Transporting Thresholds 103
Appendix G: Transporting Thresholds
OVNM provides tools that assist in migrating common thresholds from one HP NonStop node to another. These
tools are:
•
•
•
•
AutoRpt (Auto Maintenance Report)
•
MOVEDB
The MOVEDB utility was developed to allow customers to move OVNM database from one location to another
without having to re-enter the thresholds. This would be used when multiple HP NonStop nodes need to be
configured with the same thresholds. If the nodes monitor entirely different objects, then it will be easier to go
through the install process on each node.
The two files involved with the MOVEDB utility are:
•
MOVEDB
MOVEDB is a TACL routine that will prompt the user for the necessary information, move the files to the
remote location and then modify the necessary files.
•
CHGSYS
CHGSYS is an object file that is used to modify the contents of the database files to alter the node name
that is recorded in some of the records. It will display the number of records written and the number of
records modified. In most cases, these values should be identical.
To use this utility, perform the following steps:
1.
Switch to the subvolume where OVNM is installed.
2.
Use the following command to start initializing the MOVEDB utility.
RUN MOVEDB
The MOVEDB utility will prompt you to enter the information required to duplicate the OVNM environment in
another HP NonStop node. The following questions will be asked. Most questions will recognize QUIT, EXIT and
STOP, which will cause the routine to stop processing. Responses are NOT case sensitive.
a.
Enter the $vol.subvol where OVNM is already installed
.
Enter the volume and subvolume that has the OVNM database. This would be the location that already
contains all of the thresholds that you want duplicated to the second node. This utility will verify that
certain files exist in that location. The utility will terminate if the required files are not found.
b.
Enter the (\node.)$vol.subvol where you want this duplicated.
The normal response to this prompt is the location on the remote node where you want to duplicate the
database. The node name is optional and you can specify a local volume to temporarily store the
database. It will be created in such a way that it will be possible to backup those files and restore them
to the remote node without making any additional changes. If you do specify a node, the next question
will be skipped – it will assume that you want the database changed to contain the node name
supplied in this response.
The subvolume specified in this response must be empty.
c.
Enter the new node name.
This question is asked only if the previous question did not contain a node name and will be used to
replace the node name in the database. This should be the name of the node that will receive the files
created as a result of this utility.