HP NonStop G-Series - Manual (Page 110)

Appendix G: Transporting Thresholds 110
ZTMIGRAT
The ZTMIGRAT job utilizes the same programs and files as ZTEXTRCT and ZTINSERT. It allows you to automate
the process so it can be scheduled, for example on a daily or weekly basis. This job requires you to provide the
list of nodes and subvolume locations for the various OVNM systems you want to be updated. The tool assumes
that you will want ALL thresholds deleted on the receiving nodes before adding the new thresholds. This allows
you to make changes to the thresholds on the master node and duplicate the changes to the rest of your network.
To start using the function, create and edit the CUSTMIGS (Customer Migrations) file. This file will contain a list of
nodes and their corresponding locations ($volume.subvolumes). For example:
\node1$vol.ovnm
\node2$vol2.ovnmx
OVNM can be installed on a different subvolume on each node, or on the same subvolume.
Once the CUSTMIGS file is created, all you have to do is run it. It requires Expand access to all the nodes in the
CUSTMIGS file since it uses Expand to transfer the files from one node to another. As it sends each file to the
other node, it will delete the thresholds in the receiving node before adding the new ones. Once the job is
complete, you will have to stop/start OVNM on each node for the changes to take effect.
NOTE: The ZTEXTRCT and ZTMIGRAT jobs will NOT transfer any thresholds that were added to the original
database using the “Add Object” right-click option in the OCC Threshold pane. It allows you to add objects
that would not normally be discovered by the backend based on the template supplied. When this feature is
used, there is no way for these tools to recognize that happened. The extract job is actually extracting the
threshold description that was specified when the threshold was added. When the data is processed on the
receiving node, OVNM will “re-discover” the list of objects that exist on that node. Therefore, it is entirely
possible that the set of objects being monitored on the second node will be different from the set of objects
being monitored on the first node.
A
pp
en
di
x G