Answer
In order to begin investigation into HNAS file replication issues GSC requires all the information detailed below:
- A description of:
- How you believe the replication should be working?
- What is the perceived deviation from how you believe the replication should be working?
- What messages in the HNAS event log do you think are related to the problem (if any)?
- What messages in the HNAS debug log do you think are related to the problem (if any?)
- Details of the replication:
- What is the name of replication policy that is not working as expected?
- What is the name and ID of the replication schedule for the replication that is not working as expected?
- Are snapshot rules being used on the source or is the replication using automatically generated snapshots? If the replication is using a snapshot rule on the source please advise:
- The name of the snapshot rule on the source,
- What the intended purpose of using this snapshot rule is?
- Are snapshot rules being used on the destination or is the replication using automatically generated snapshots? If the replication is using a snapshot rule on the destination please advise:
- The name of the snapshot rule on the destination,
- What the intended purpose of using this snapshot rule is?
- Are pre or post replication scripts in use? If these are in use please advise what the intended purpose of using these scripts is?
- Are file replication rules in use? Is so please advise:
- The name of the file replication rule in use?
- What the intended purpose of using the file replication rule is?
- What is the source of the file replication?
- Source cluster name?
- Source node name?
- Source file system name?
- Source EVS number?
- What is the destination of the file replication?
- Destination cluster name?
- Destination node name?
- Destination file system name?
- Destination EVS number?
- When did the replication last successfully run, if ever? (If it has never run successfully please state.)
- What were the NDMP session numbers for the last successful replication?
- On the source HNAS?
- On the destination HNAS?
- When did the replication first fail?
- What were the NDMP session numbers for the first unsuccessful replication?
- On the source HNAS?
- On the destination HNAS?
- Collect the following diagnostic data:
- Managed NAS server diagnostics for the source cluster/node of the replication.
- Managed NAS server diagnostics for the destination cluster/node of the replication.
- SMU diagnostics for the SMU that manages the replication.
- The ndmp-session-trace (HNAS CLI command ndmp-session-trace - see CLI command man page for details) for the following captured to a text file using the session logging facility of your SSH client:
- Last successful replication:
- Source session.
- Destination session.
- First failing replication:
- Source session.
- Destination session.
- If the problem is performance related please gather a PIR targeted on the source and destination file systems covering a time period when the perceived performance problem is occurring. If the source and destination nodes are different then the PIRs on both file systems should be taken simultaneously. If the two file systems are hosted on the same node then please take the two PIRs one after the other with as little gap as possible between them. All the information provided above should be for the source and destination sessions that are captured by the provided PIRs. Please see the knowledgebase article What Information Do I Need to Gather to Allow GSC to Diagnose an HNAS Performance Problem for more information.
Once all that information has been gathered open a case and provide all the information requested and upload the requested diagnostic data to TUF against the case number.