Re: Moving DR site from 30miles to 1600miles

I guess when it comes to the network, I am a user.

The TCP layer (layer 4) belongs to the networking team in my opinion.

If TCP is an issue, they should be able to tell you where the delays are and suggest a remedy.

Jared

On Wed, Apr 9, 2008 at 11:42 AM, Ravi Gaur <ravigaur1_at_gmail.com> wrote:

> Thanks Jared,
> The networking team says that it was already done in the initial
> troubleshooting and that it is not a network issue. TCP seems to be the
> likely bottleneck here.
>
> - Ravi
>
> On Wed, Apr 9, 2008 at 1:25 PM, Jared Still <jkstill_at_gmail.com> wrote:
>
> > It might be a good idea to ask your network folks to trace an scp with
> > wire shark or
> > some similar tool, and see if they can spot any network delays.
> >
> >
> > Jared
> >
> >
> >
> > On Wed, Apr 9, 2008 at 8:39 AM, Ravi Gaur <ravigaur1_at_gmail.com> wrote:
> >
> > > In our testing, we are hitting issues in network transfer rates to the
> > > 1600-miles site -- a simple "scp" of 1GB file takes about 21 minutes. We
> > > generate archives at the rate of approx 1GB/8minutes. The network folks tell
> > > me that the TCP setting is a constraint here (currently set to 64k
> > > window-size which Sysadmins here say is the max setting). We have an Oc3
> > > link that can transfer @ 150Mbps (that is what the networking team tells
> > > me).
> > >
> > >
> >
>

-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

--
http://www.freelists.org/webpage/oracle-l