This post is more than 5 years old
6 Posts
0
2033
November 25th, 2013 05:00
NS480 VNX data replication
We have a new VNX and are trying to migrate the data from our current NS480 over to it.
I started with this guide
http://www.emc.com/collateral/hardware/white-papers/h8174-migrating-celerra-vnx-replicator-wp.pdf
The steps failed at data mover interconnect. Reading other discussions, several people recommended the command line versus the replication wizard.
Although I have got a little more with the CLI it's still failing at the data mover interconnect.
The following just sits at 1% progress
$ nas_replicate -create NS480VNX -source -vdm vdm1 -destination -vdm vdm1 -interconnect NS480-VNX -max_time_out_of_sync 10
$ nas_task -i 6761780
Task Id = 6761780
Celerra Network Server = NS480-NN-Control
Task State = Running
Current Activity = Info 26045317578: Creating checkpoints for Create task
Movers = server_2
Percent Complete = 1
Description = Create Replication NS480VNX.
Start Time = Sun Nov 24 22:17:12 EST 2013
Estimated End Time = Tue Jan 07 09:38:52 EST 2014
Schedule = n/a
I maybe missing something simple which needed to be done with the new VNX... Any input would be appreciated!
Thanks
Caroline
crasmussen
6 Posts
0
December 2nd, 2013 11:00
And the problem was....
Turns out the interface(IP) we used on the NS480 had been used for NDMP. A bit odd to me that this was the cause. And that the behavior was reproduced without any NDMP backups running.
We created a new interface on the NS480 and the rest worked fine.
Thanks for the replies!!
Caroline
Rainer_EMC
4 Operator
•
8.6K Posts
0
November 25th, 2013 07:00
Check the data mover log
crasmussen
6 Posts
0
November 25th, 2013 11:00
From what I see it looks like I have a network issue.
2013-11-25 14:01:13: CMD: 3: DicEvent::HandleFinalResponse() taskId: APM001017007530000_2_3002622:0 final response CCMD_Id: 13422034977
2013-11-25 14:01:13: CMD: 6: DicEvent::DeleteDicEventDatabase() caller: 0x000163c110 globalTaskId (APM001017007530000_2_3002622) with CmdStatus: CmdContextReferenceTooHigh
2013-11-25 14:01:18: HTTP_CLIENT: 3: Connection failed to address through interface error: 'Connection timed out '
2013-11-25 14:01:18: HTTP_CLIENT: 3: The IP address is unavailable
2013-11-25 14:01:18: CIC: 3: Sending Cmd to failed (41=Disconnected)
2013-11-25 14:01:18: CMD: 3: DicXmlSyncRequest::sendMessage sendCmd failed:41
There is no firewall between these, they are on the same network, and server ping works
I also noticed when I run the replicate command it appears to run the CPU on server_2 really high and the interconnect goes down.
Rainer_EMC
4 Operator
•
8.6K Posts
0
November 25th, 2013 12:00
Could be
Make sure that both the CS’s can see each other as well as the DM’s
Server_ping checks the DM network – you need to test regular ping between CS as well
Check nas_cel working properly (see Replicator manual)
crasmussen
6 Posts
0
November 25th, 2013 12:00
The CS's can ping each other.
nas_cel -interconnect -validate NS480-VNX
works from the source to the destination.
I checked the other way and it fails. "Unable to connect to destination interface via DIC service"
When I run the one on the source it's now fails too. I also see the same behavior where the CPU spikes and it take a reboot to get the first nas_cel to work again.
Jeffey1
4 Operator
•
2.8K Posts
0
November 30th, 2013 08:00
Did you create a static route so the box know which interface to be use for replication?