HP XP P9000 Command View Advanced Edition Software - Manual (Page 246)

TIP:
If copy pairs have been defined using storage system operation management software such as Remote
Web Console, there is no configuration definition file, since copy pairs that are not managed by pair
management servers exist. In this case, copy pair information is acquired from the databases of Device
Manager servers registered as information sources, after the databases have been refreshed by
executing the Device Manager refresh function from Replication Manager.
Performance-related information, copy progress, and the copy pair state for the secondary volume
cannot be acquired. For details on the Device Manager refresh function, see theHP StorageWorks
P9000 Command View Advanced Edition Suite Software Help or HP StorageWorks P9000 Command
View Advanced Edition Suite Software CLI Reference Guide. To view the flow of data in open systems,
see “
Refreshing copy pair statuses data flow (open systems) ” on page 247.
In mainframe systems, the copy pair statuses are 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 in mainframe systems, see “
Refreshing copy pair statuses data flow
(mainframe systems) ” on page 247.
Copy pair statuses can be refreshed manually at any time from a subwindow or automatically at an
interval preset in the refresh settings. Normally, refreshing takes anywhere from a few to tens of
minutes. However, if the Device Manager refresh function is used because there are copy pairs that
are not managed by pair management servers in open systems, refreshing requires anywhere from
a few to tens of minutes for each storage system. If all copy pairs are managed by pair management
servers, disable the Device Manager refresh function. For details, see “
Disabling the Device Manager
refresh function ” on page 248.
When you determine the interval for refreshing copy pair statuses, for open systems use the number
of monitored copy pairs on each pair management server. To determine the interval for refreshing
copy pair statuses for mainframe systems, use the number of monitored copy pairs on each information
source as a guideline. The following table provides guidelines for determining the interval for refreshing
copy pair statuses.
Guideline for determining the interval for refreshing copy pair statuses
Guideline interval
Number of copy pairs on pair management
server or information source
3 minutes 0 to 1,000
5 minutes 1,001 to 2,000
10 minutes 2,001 to 3,000
15 minutes 3,001 to 5,000
Related topics
• Refreshing the copy pair status automatically for each information source , page 250
• Refreshing copy pair status automatically for each pair management server , page 251
• Refreshing copy pair statuses manually for each copy group , page 250
• Refreshing copy pair statuses manually for each host , page 249
• Refreshing copy pair statuses manually for My Copy Groups , page 250
Refreshing management information 246