as per our network team the latency is normal because of the both SAN are located on different islands and on different ISP. However, if we have both SANs in the same ISP. the Latency is just 10ms.
but the puzzling fact is that whenever we try to copy a file on a network with 390ms latency, let's say a movie file worth 1.3 GB. it will complete in 20-30 minutes. bit in SAN replication, a 6 Gig takes up a Day.
i see.. that would also make a point.. .. i'll continue to check on the trend of the transfer and see if there will be any improvements in the next few days.
Kirld
6 Posts
0
April 5th, 2013 11:00
FW used is Cisco ASA.
as per our network team the latency is normal because of the both SAN are located on different islands and on different ISP. However, if we have both SANs in the same ISP. the Latency is just 10ms.
but the puzzling fact is that whenever we try to copy a file on a network with 390ms latency, let's say a movie file worth 1.3 GB. it will complete in 20-30 minutes. bit in SAN replication, a 6 Gig takes up a Day.
any idea?
Kirld
6 Posts
0
April 5th, 2013 11:00
the firmware is V 6.0.1 (R264419)
so.. if a larger blocksize is used for replication, then replication should be faster than a standard copy. but the other way is happening to us..
Kirld
6 Posts
0
April 5th, 2013 15:00
i see.. that would also make a point.. .. i'll continue to check on the trend of the transfer and see if there will be any improvements in the next few days.
Kirld
6 Posts
0
April 19th, 2013 16:00
Hi Donald,
We have run diagnostics with the Network team and we verified that it is an ISP Problem.
Slow Wan Replication was solved.. We can now have 16 Gig Replication in just 1 Hour!
However, the problem is that we will be more than our capping in bandwidth..
Is there a way to limit the replication bandwidth usage?
Kirld
6 Posts
0
April 20th, 2013 03:00
That is what we have discussed so far with the Network Team.. but using QoS will limit also other traffic.
Thanks anyway Don..
MarshM
1 Message
0
November 20th, 2013 16:00
Hello,
We have the same issue here. What exactly on the ISP side was causing the problem if you don't mind?
Thanks!