Utilizing DRBD Proxy along with an IPSEC tunnel, we replicate data between Vienna, Austria and Beaverton, OR.  we're able to achieve between 20-30Mb/sec, which caps out our connection.  

I've seen similar issues before, which have been resolved by utilizing DRBD Proxy.  There are evaluation licenses available for free, so you might as well give it a shot, you've got nothing to lose. :)


-Brian

LINBIT - Your Way to High Availability
7959 SW Cirrus Dr. 
Beaverton, OR 97008 

http://www.linbit.com


Dan Lavu wrote:
Bernd,

We wrote exceptions for the two machines to be out of the VPN and permitted all traffic, it's still capped at 2MB/s. So it's not the IPsec tunnel. I've been talking to RussS, there is a program called DRBD Proxy designed for WANs, do you think it might be a software limitation? Does a network test to find out that my latency is too high and caps it, because DRBD Proxy is the proper solution? 

Does anybody on here, use DRBD without DRBD Proxy to go across a WAN? 
  

Another update, I installed the same config on two LANed machines, using ramdisks, and I was transferring at 80-120MB/s, have to love GigE and Ramdisks. Thanks in advance.

Best Regards,

Dan Lavu 

-----Original Message-----
From: Bernd Petrovitsch [mailto:[email protected]] 
Sent: Wednesday, February 17, 2010 3:57 AM
To: Dan Lavu
Cc: [email protected]
Subject: Re: [DRBD-user] DRBD - Slow Performance

Hi!

On Die, 2010-02-16 at 12:20 -0500, Dan Lavu wrote:
[...]
  
I can transfer a plain file at 20-25MB/s, using sftp. I'm talking to
    
Over the IPSEC tunnel, I assume.
  
 our network engineers to see if they can disable the IPSEC tunnel fo
    
Forget that. My theory that the "backbone" limits the 2MB/s is gone with
the test and numbers above.
With DRBD, you should get pretty much the same as above (given that the
local I/O subsystems are fast enough).

Now it gets really strange.

	Bernd
  
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user

Reply via email to