Unsolved
This post is more than 5 years old
8 Posts
0
1294
Replication on Vnxe stucked
Hello Team,
When checked replication status though unisphere replication tab showing below error
"The replication session encountered an error that halted progress" And not showing last sync time.
So i stopped session and after that i started replication session.
But in background it shwoing in running state.
can please help me to trouble shoot on this.
Rainer_EMC
8.6K Posts
0
November 6th, 2017 05:00
depends an your model and OE version - there are 3 generations of VNXe on the market
check if you have service command (svc_*) available
If not please open a service request with support and they can help you
amya1
8 Posts
0
November 6th, 2017 09:00
Hello Rainer_Emc,
Thanks For reply. Find below snap. In that both start and stop replication running and still replication is in stopped
state. It not allowing to abort session. Souce side have 95 percentage data and destination side have 79 percentage data , it shows data not replicated to destination side.
Can you plz help us to troubleshoot this issue.
Rainer_EMC
8.6K Posts
0
November 7th, 2017 09:00
please open a service request or use customer service live chat
amya1
8 Posts
0
November 13th, 2017 05:00
THANKS for reply
That box not in suppot with EMC. Need your help in this case
As in previous sanp those running task deleted from DM memory.
As have similar kind of issue, Replication saying ok Status but below paramenter value not changing. Aslo data not replicationg to destination side.
Current Transfer Size (KB) = 1358030560
Current Transfer Remain (KB) = 1351070560
Estimated Completion Time = Sun Mar 04 17:21:48 EST 2012
Current Transfer is Full Copy = Yes
Current Transfer Rate (KB/s) = 814
Current Read Rate (KB/s) = 4059
Current Write Rate (KB/s) = 1242
So can you help me to sort out this issue. that box not in support
Rainer_EMC
8.6K Posts
0
November 13th, 2017 16:00
if the system is not under a support then I would suggest to search the knowledgebase if there are solutions or troubleshooting tips
First step will be to find out which VNXe model *exactly* you are using