HP StorageWorks Reference Information Storage System V1.4 Administrator Guide (T3559-96027, March 2006)

Table 23 Replication view features
Feature
Description
Domain Information For each domain configured for replication:
• Domain Name: DNS n ame of domain.
• Service: Whether replication is in progress (Running) or not (Stopped).
• Between: Names of local and replication systems. First system n amed is the
domain location. Second system named is the remote system where domain is
being replicated.
• Current Transfer Rate: How many messages and documents are being
duplicated per second.
• Current Percentage of D ata Replicated: How much data currently stored in
domain has been duplicated.
Table 24 Links to Replication view
Origin
Link
left menu
Replication
Links from Replication view: none
Displaying replication statuses for gr oups in a domain and replication performance over time
Click Details.
For each group in domain, detail view shows:
• Status, name, and total messages of group on local system. A check icon (
) indicates normal
operation, an X icon (
) indicates replication failed last time it was tried, and an ! icon
(
) indicates replication is being retried.
• An arrow showing direction of data between groups. Normally, direction is left to right, from
group on local host to group on remote host. In a failover situation, direction is right to left, as
data replicated on remote host is b eing used to restore group on local host.
• Name and total messages of replication group.
• Howmuchdatainsourcegrouphasbeencopiedtodestinationgroup.
A graph shows the number of messages stored per second on local and replication (remote) systems for
selected domain. You can select last year, last month, last 24 hours,orlast hour to graph.
Starting replication for specific domains
Click START NO W below domain information. Replication will replicate batch that was next when
it stopped.
Stopping replication for specificdomains
Click ST OP NOW below domain information. Replication will stop after current batch is replicated.
Reprocessing
Most reprocessing occurs as a n automated and transparent background process that does not require
ongoing operational effort other than passive monitoring. In most cases, messages are reprocessed to
reapply routing rules that have been recently added and are applied to a short time period before the
change has occurred. The Reprocessing view allows you to schedule and enable reprocessing based
on new routing rules.
Reference Information Storage System
49