Hardware manual
Group Administration Group monitoring
15–6
Table 15-3 describes some best practices for monitoring replication between groups. The first column lists the
monitoring condition, the second column describes it,
and the third column provides a reference for more
information about addressing the issue.
Table 15-3: Replication Monitoring Best Practices
Monitor Description Reference
Incomplete replication
operations
If a repl
ication operation fails to complete, you might need to
increase replication space.
See Monitoring replication on
page 15-5
Incomplete manual
transfer operation
s or
failback operations
Some operations require multiple tasks that administrators must
co
mplete. Make sure you complete all multi-task operations.
See Monitoring replication on
page 15-5
Low free delegated
space
If delegated space is low, replica reserve space might not be able to
increase automatically to s
tore new replicas.
See Monitoring a specific
partner on page 15-10 and
Monitorin
g inbound replication
on page 15-8
Number of replicas If too many replicas exist, consider decreasing the replica res
erve
percentage. If too few replicas exist, consider increasing the replica
reserve percentage.
A low free replica reserve can indicate optimal use
of replica
reserve space, if the desired number
of replicas exist.
See Monitoring inbound
replication o
n page 15-8
Monitoring outbound replication
Outbound replication transfers volume data from the current group to a replication partner.
To monitor outbound replication, click
Monitoring and then Outbound Replication. The Outbound
Replication panel provides the following information:
• Volume and partner name
• Transfer status, start time, and amount of data transferred
See the online help for information about the data fields and options.
To see more detail about a volume in the list, move
the pointer over t
he volume name. A pop-up window appears,
listing the following:
• Volume name
• Storage pool
• Thin provisioning status (enabled or disabled)
• Reported size, volume reserve, and snapshot reserve
• Current and requested status (online or offline)
• Access type (read-write permission and whether shared for cluster access)
• Replication partner
• Description, if any