Unsolved
This post is more than 5 years old
9 Posts
0
1409
January 29th, 2009 19:00
Slow Replication Using Replication Manager
These are 500gb VMFS LUN's, replicating from an NS20 to an NX4. Currently, the Celerras are sitting right next to each other behind routers (NS20 is production, NX4 will be a portable DR site). The replication manager servers are VM's running Replication Manager 5.2.x on ESX servers. Each site has gig routers and switches, but the replication is taking very long. I have successfully replicated and mounted a 1gb VMFS LUN, but am having difficulty with the larger LUN's.
I can imagine that this would be slow over a WAN link, but when monitoring the router interfaces, there is hardly any traffic going over the line (consistently 30Kb/s, up to a few MB/s rarely). I don't currently have any data mover throttling setup.
Is there something that I am missing? Thanks!
I can imagine that this would be slow over a WAN link, but when monitoring the router interfaces, there is hardly any traffic going over the line (consistently 30Kb/s, up to a few MB/s rarely). I don't currently have any data mover throttling setup.
Is there something that I am missing? Thanks!
No Events found!
JamesBEMC
257 Posts
0
January 29th, 2009 23:00
Can you tell me a bit more about how the job is configured in terms of Celerra replicator?
Also, have you tried to manually configure a Celerra replicator job and see how that performs as opposed to one under RM's control? I suspect the issue would be the same (that is of course without knowing more).
You also say you managed to replication a 1GB VMFS Lun, but are having difficulty with larger LUNs. Did the 1GB LUN replicate with the desired speed (much faster) or as it was much smaller, it was replicated slowly but got there in time?
Thanks
James
marksoho
9 Posts
0
February 1st, 2009 19:00
In the DR site Repman Server, I received this error:
000024 ERROR:An unexpected internal error occurred: bad allocation.
The XML message for above-mentioned error is as follows:
final
2009 02 01 09:30:01
InternalError
bad allocation
Are there any specific items that I need to take care of when the Rep Manager servers are VM's? Thanks again! The replication still is very slow, only bursting up to 25mb/s rarely and briefly.
JamesBEMC
257 Posts
0
February 5th, 2009 00:00
I dont think VMs are an issue here.
Can I suggest as part of a troubleshooting/isolation test, can you run a manual (outside of RM) replicator test of the same LUNs and see if the performance / stability is the same or if it is significantly better?
Thanks
James
marksoho
9 Posts
0
February 9th, 2009 18:00
JamesBEMC
257 Posts
0
February 9th, 2009 23:00
You ask, I retrieve
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-004-184.pdf
Page 22 - System requirements for Celerra Replicator
IP addresses configured for the source and destination Data Movers
(ports 8888 and 8887 used by replication for transferring data and internal
operations - contact Customer Service to change this setting).
¿ HTTPS connection between the Control Station on the source site and the
Control Station on the destination site (port 443 - cannot be changed).
Note: ICMP (Internet Control Message Protocol) ensures a destination
Celerra Network Server is accessible from a source Celerra Network Server.The
ICMP protocol reports errors and provides control data about IP packet
processing.
Also
EMC KB emc171144
8887 TCP RCP Yes Used by Celerra Replicator during a target to source resync. This port must be open between the source and target Data Movers.
8888 TCP RCP Yes Used by Celerra Replicator. This port must be open between Data Movers on both sides of a replication session.
Cheers
James.