HP P6000 Replication Solutions Manager Administrator Guide (T3680-96069, June 2012)

Discovery
The replication manager automatically discovers storage resources and refreshes its database at
regular intervals. You can adjust the interval to meet specific needs. After discovering a new
resource, the replication manager needs additional time to collect all the information and add the
resource to the database. In the interval between discoveries, it can appear that a new snapclone,
for example, is in a constructing state longer than it actually is.
Between automatic discovery cycles, you can discover resources and refresh the database by
clicking the database refresh icon on the replication manager toolbar. For example, you may
want to discover a new snapclone immediately, rather than wait for the next discovery cycle. Other
reasons for using interim discovery would be after you modify resources from another application
or install a replication manager host agent. The replication manager does not automatically discover
newly enabled hosts.
Changing the discovery and refresh interval
To change the discovery and database refresh interval, edit the configuration files. For instructions,
see the HP P6000 Replication Solutions Manager online help or user guide.
You might want to increase or decrease the discovery and database refresh interval in the following
circumstances:
• If other applications are using the arrays or the management server, consider increasing the
interval to improve performance.
• If the storage configuration is large or there are delays in the environment, consider increasing
the interval to improve performance.
• If you are configuring an environment or performing testing, the default interval may not reflect
changes quickly enough. Consider temporarily setting the interval to a few minutes.
• If you are only monitoring storage, the default interval may be too short. Consider setting the
interval to several hours.
Jobs
A job is a repeatable replication-specific command or set of commands. A job can be simple (for
example, create a DR group) or complex (for example, perform cascaded replication). You can
run a job from the graphical user interface (GUI), from the command line, from a batch file, or
from a scheduler.
Events associated with job instances are recorded in job log files and displayed in the event pane.
For more information, see “Ensuring job success” (page 33).
Events
An event is a system-generated status message resulting from a:
• User-initiated action (for example, suspend DR group)
• Replication-related or array incident (for example, retrieved data for array)
• Job (for example, job complete)
The replication manager periodically retrieves event messages from the replication manager event
logs (storage.evt) and displays them in the event pane whenever a job is executing or any
action is performed on the storage or host objects. The event description includes event codes,
severity, date and time of occurrence, source component, and an explanation. This information
can help you troubleshoot issues. For more information about the event pane, see the online help.
Replication manager features 9