HP 9000 rp5405 Servers - Manual (Page 266)

2. Click the Monitoring Setting link.
The Monitoring Setting subwindow appears.
3. Click the link that has the name of the Device Manager server that is an information source to
which the pair management server belongs.
The Device-Manager-server-name subwindow appears.
4.
Click the icon of the pair management server from which you want the copy pair statuses to
be acquired automatically.
The Edit Interval of Refresh Pair Status - pair-management-server-name dialog box appears.
5. Modify the interval settings, and then apply them.
The settings specified in the Device-Manager-server-name subwindow are applied. From
this point, the copy pair statuses are automatically refreshed based on the specified settings.
Related topics
• About refreshing copy pair status , page 259
• Refreshing the copy pair status automatically for each information source , page 264
• Calculating the copy pair status refresh interval , page 135
Refreshing configuration information
You should refresh configuration information to apply the latest configuration information to Replication
Manager.
This module describes methods for refreshing configuration information:
• About refreshing configuration information , page 266
• Refreshing configuration information automatically (using the refresh settings) , page 270
• Refreshing configuration information manually for each information source , page 271
• Refreshing configuration information manually for each storage system , page 271
About refreshing configuration information
In mainframe systems, configuration information is acquired from the instances of HP StorageWorks
P9000 for Business Continuity Manager Software or P9000 mainframe agent registered as information
sources. To view the flow of data when configuration information is refreshed in mainframe systems,
see “
Data flow when configuration information is refreshed in mainframe systems ” on page 269.
In open systems, configuration information is acquired from the databases of Device Manager servers
registered as information sources and from Device Manager agents. If Device Manager servers
installed at multiple sites are used as information sources, configuration information is acquired using
the Device Manager agents for each of those sites. To view the flow of data when configuration
information is refreshed in open systems, see “
Data flow when configuration information is refreshed
in open systems ” on page 268. Device Manager and Replication Manager maintain separate
databases for configuration information. The act of synchronizing these two databases is known as
a configuration refresh.
For a local instance of Device Manager, this synchonization is always performed as needed (so there
is no need for manual or scheduled refresh operations). The following events trigger synchronization
of the Replication Manager and Device Manager databases:
• Storage system updates that change the configuration
Refreshing management information 266