6.5 HP StoreAll OS User Guide

Issues with enabling a custom metadata replication task
Enabling custom metadata replication is a multi-step process and could fail during any of these
steps if the corresponding processes are already running or are in an inconsistent state. Some
examples of common issues that could lead to failure are:
• The archiving daemon was stopped or restarted on the source cluster.
• The archiving daemon was stopped or restarted on the target cluster.
• Express Query is in a state other than OK on either the source or target cluster.
• The active Fusion Manager fails over to another node on the source cluster.
• The active Fusion Manager fails over to another node on the target cluster.
To resolve the issue:
1. Disable the custom metadata replication task using the crr_cmd_replication.sh command
with the -d option.
2. Resolve the underlying issue as reported in the log file.
3. Re-initiate the custom metadata replication task using the crr_cmd_replication.sh
command with the -e option.
Active Fusion Manager on source cluster reboots before custom metadata
replication task has been enabled or disabled successfully
If this issue occurs, do the following:
1. Log in to the new, active Fusion Manager on the source cluster.
2. Execute the crr_cmd_replication.sh command with the -d option to disable the custom
metadata replication task. This ensures that any residual tasks running in the background are
cleared on both clusters.
3. Execute the crr_cmd_replication.sh command with the -e option to restart the custom
metadata replication task.
Active Fusion Manager on the target cluster reboots or fails over to another
node before the custom metadata replication task has been enabled or
disabled successfully
If this issue occurs, do the following:
1. Execute the crr_cmd_replication.sh command with the -d option to disable the custom
metadata replication task. This ensures that any residual tasks running in the background are
cleared on both clusters.
2. Execute the crr_cmd_replication.sh command with the -e option and using the new
IP address of the active Fusion Manager node on the target cluster to restart the custom
metadata replication task.
Express Query still processing on the target file system when the entire source
cluster goes down and the CRR task has been stopped
During an inter-cluster custom metadata replication task, if the entire source cluster goes down
when the custom metadata replication is in progress, the CRR task is stopped. However, the Express
Query processing on the target file system would still be in progress. So, execute the following
commands on the active Fusion Manager node of the target cluster to turn off the Express Query
processing on the target file system:
ibrix_crreq -f <TARGET_FSNAME> -P off
ibrix_crreq -f <TARGET_NAME> -T off -t 0
Troubleshooting custom metadata replication 273