Scribd
Upload
199 views4 pages

Dell EMC Unity - Troubleshooting Async Replication - Dell UK

Uploaded by

604597
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
199 views4 pages

Dell EMC Unity - Troubleshooting Async Replication - Dell UK

Uploaded by

604597
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Article Number: 000010716 📠 Print

Dell EMC Unity - Troubleshooting Async Replication


Summary: How To Effectively troubleshoot replication incidents, relevant to Block & File

Audience Level: Partners

Article Content

Instructions

This article is work in progress perpetually ,


Attempting to provide tool to assist TSE with investigating unknown conditions.

Basic Replication functionalities & terminologies for break/fix and customer discussions :

1. Pause - Stop a session. [Formerly Stopped session]


2. Sync - Manually sync a session. [Formerly Manual refresh]
3. RPO - 'Max Out Of Sync Timeout' (defaults to 60 Minutes)
4. Connection - Management + Replication interface setup - formerly remote CS + interconnect setups
5. Update And Refresh - Attempt to perform local+remote connection checks and update for replication interfaces changes ,
and also attempts to validate the replication interfaces connection
6. Failover - Initiated from destination , brings remote session to RW/Enabled state disregarding current transfer states
(aka failover without sync, true DR)
7. Fail over With Sync - Initiated from Original Source Side Only - performs graceful failover.
8. Resume - Start a Paused session. If initiated on Remote side AFTER failover -
This starts copying back changes to orignal source (without failback, formerly start -reverse operation)
9. Failback - Initiates a sync of failed over session back to original source side ,
and immediately after makes original source side production again.

10. Create / Delete / Modify - Standard configuration changes

Above standard operations (1,6,7,8,9) on ThunderBird / Falcon are executed one resource at a time -on the VDM/FS/DS levels.
Group operations will be allowed in Merlin (4.2) release. (Health dependent)

TSE1 Support are expected to assist customer in basic operations and Unisphere only related troubleshooting.
Additional Information

List of Documentation and known Knowledge base articles :

Basic Configuration:

http://www.emc.com/en-us/documentation/unity-family/unity-p-replication-config/index.htm

http://www.emc.com/dam/uwaem/documentation/unity-p-replication-config.pdf

Detailed White Paper :

https://support.emc.com/docu69886_Unity:-Replication-Technologies---A-Detailed-Review.pdf?language=en_US

Knowledge Base Articles :


Unity - How to perform Target Replication Data Content check Article Number 000482672

Hung replication process (Error Codes:0x9ef4 and/or 0x6701140 )

Creating Replication Connection fails (Error Code: 0x6500128) if the proper Replication Interfaces are not configured on Local and
Remote Systems

Unity - Back to Back File Replication is unsupported


Unity replication connection setup failure : Failed to register the local system on the remote side

Unity: How To Setup Async-Replication Out-Of-Sync Alerts (User Correctable)

Unity - Async replication might stop automatic updates / Last Sync Time not updating (Dell EMC Correctable)

Partner Notes

Connectivity (IC-Validation) advanced troubleshooting:

1. Ensure management IP's can communicate ( use ping / telnet remote-ip 443 to verify)
2. Ensure replication IP's can communicate on replication ports - this is more problematic to troubleshoot ,
Use svc_networkcheck -r command to test the view and test interconnect in CLI if needed.
Alternatively , /nas/bin/nas_interconnect -validate option is still available but requires root access.
ping -I source_ip target_ip can be used to verify ICMP if not blocked.
3. See advanced connectivity script in restricted section.

Main Log:
/EMC/CEM/log/cemtracer_dataprotection.log

Internal root scripts for monitoring / troubleshooting :

/EMC/CEM/bin/clariiontool/./repcli.x [list , -h]


/EMC/Platform/bin/repl_session_list.pl ==> alternative script for listing sessions

Outputs example :

14:35:20 root@(none) spa:/cores/service> svc_networkcheck -r


=== SP status: Normal Mode, Master SP ===

======================= [spa][Mon Mar 13 14:35:33 UTC 2017] Beginning Run =======================

================ Now running nas_cel -l ... ================


id name owner mount_dev channel net_path CMU
0 spa 0 128.221.255.100 APM001614067890000
================ Now running nas_cel -interconnect -list ... ================
id name source_server destination_system destination_server
10001 loopback SVDM_A spa SVDM_A
10003 SVDM_A_0_SVDM_B SVDM_A spa SVDM_B
20001 loopback SVDM_B spa SVDM_B
20003 SVDM_B_0_SVDM_A SVDM_B spa SVDM_A
================ Now running nas_cel -interconnect -info -all ... ================
id = 10001
name = loopback
source_server = SVDM_A
source_interfaces = 128.221.255.12
destination_system = spa
destination_server = SVDM_A
destination_interfaces = 128.221.255.12
bandwidth schedule = uses available bandwidth
crc enabled = yes
number of configured replications = 1
number of replications in transfer = 0
status = The interconnect is OK.

id = 10003
name = SVDM_A_0_SVDM_B
source_server = SVDM_A
source_interfaces = 128.221.255.12
destination_system = spa
destination_server = SVDM_B
destination_interfaces = 128.221.255.13
bandwidth schedule = uses available bandwidth
crc enabled = yes
number of configured replications = 0
number of replications in transfer = 0
status = The interconnect is OK.

id = 20001
name = loopback
source_server = SVDM_B
source_interfaces = 128.221.255.13
destination_system = spa
destination_server = SVDM_B
destination_interfaces = 128.221.255.13
bandwidth schedule = uses available bandwidth
crc enabled = yes
number of configured replications = 0
number of replications in transfer = 0
status = The interconnect is OK.

id = 20003
name = SVDM_B_0_SVDM_A
source_server = SVDM_B
source_interfaces = 128.221.255.13
destination_system = spa
destination_server = SVDM_A
destination_interfaces = 128.221.255.12
bandwidth schedule = uses available bandwidth
crc enabled = yes
number of configured replications = 0
number of replications in transfer = 0
status = The interconnect is OK.

repcli.x output:

*******************************************************************************
Session 171798692045_VIRT1544BKKBLD_0000_171798691868_VIRT1648X7VMRW_0000
*******************************************************************************
Name = DS3
Session type = file
Synchronization type = auto
RPO = 1h 00m
Resource type = VMware NFS
Sync State = idle
Health state = OK (5)
Health details = "This replication session is operating normally. No action is required."
Operational status = Auto Sync Configured (0x8405)
Source status = OK
Destination status = OK
Network status = OK
Destination type = remote
Destination system = RS_5
Local role = Source
Source resource = res_6
Source SP-A interface = 10.241.253.213
Source SP-B interface = N/A
Destination resource = res_7
Destination SP-A interface = 10.241.253.209
Destination SP-B interface = N/A
Time of last sync = 2016-12-08 23:36:56
Sync status =
Sync transfer rate = N/A
Sync transfer size remaining = 0
Previous transfer rate = 12 MB/s
Average transfer rate = 21 MB/s
Element pairs = N/A

Example of graceful cleanup using internal cmd:

root@spa:/cores/service>/EMC/CEM/bin/clariiontool/repcli.x delete
103079215107_APM00162124203_0000_103079215109_APM00162103004_0000 -m destination
Deleted successfully.

Article Properties

Affected Product
Dell EMC Unity Family

Product
Dell EMC Unity Family

Last Published Date


11 Aug 2022

Version
4

Article Type
How To

You might also like