This is a multi-part message in MIME format.
------_=_NextPart_001_01C65E38.69E48242
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"
Ok So your saying hat if we use Veritas drives then we can use a high
setting than 64k? And I think UNIX/Solaris backup servers do not have
his issue?
=20
Greg=20
________________________________
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Paul
Keating
Sent: Wednesday, April 12, 2006 9:33 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] LTO3 maximum block size of 65536 bytes;abuffer
size of 262144 cannot be used
IP has nothing to do it it...
you can pull in 32k buffers off the IP side and write 256k blocks to
tape...in some cases this is recommended
=20
the SCSI card and driver are the keys here.
In the past, default "Windows" SCSI drivers will not work over 64k,
which is why Veritas recommends using their tape drivers.
=20
Paul
--=20
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Scott
Jacobson
Sent: April 5, 2006 4:18 PM
To: veritas-bu AT mailman.eng.auburn DOT edu; Sekhon S.
Subject: Re: [Veritas-bu] LTO3 maximum block size of 65536
bytes; abuffer size of 262144 cannot be used
=09
=09
Simrat,
=20
I've seen many discussions in this forum about using 262144 for
a buffer sizes on Windows, and most of those discussions talk about it
not being recommend or successful based on Windows TCP/IP Stack size
limitation. Others have indicated they have been able to get buffers
sizes like this to work if your able "tweek" SCSI card parameters or
registry settings as you've mentioned.
=20
Based on your error message, I'd say the registry may have
changed, but again, your fighting a fixed block size between the device
and OS IP Stack communications that changes it back to 64K.
=20
I've also read here that there is a unsupported Windows OS
parameter change that can be made as well, but again, I don't recall
from anyone in this forum indicating they've been able to make it work
successfully.
=20
I abandoned my effort two years ago to get this to work and now
use Linux Media and Master servers to resolve this issue.
=20
Scott
>>> This e-mail and any attachments are confidential, may contain legal, pr=
ofessional or other privileged information, and are intended solely for the=
addressee. If you are not the intended recipient, do not use the informat=
ion in this e-mail in any way, delete this e-mail and notify the sender. CE=
G-IP1
------_=_NextPart_001_01C65E38.69E48242
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="us-ascii"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office"><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D979075213-12042006>Ok So your say=
ing hat if=20
we use Veritas drives then we can use a high setting than 64k? And I =
think=20
UNIX/Solaris backup servers do not have his issue?</SPAN></DIV>
<DIV> </DIV><!-- Converted from text/rtf format --><BR>
<P><SPAN lang=3Den-us><FONT face=3D"Times New Roman">Greg </FONT></SPAN></P=
><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma><B>From:</B> veritas-bu-admin AT mailman.eng.auburn DOT
edu=20
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of
</B>Paul=20
Keating<BR><B>Sent:</B> Wednesday, April 12, 2006 9:33 AM<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu]
LTO3=20
maximum block size of 65536 bytes;abuffer size of 262144 cannot be=20
used<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=3D184482113-12042006>IP has nothing to do it it...</SPAN><=
/DIV>
<DIV><SPAN class=3D184482113-12042006>you can pull in 32k buffers off the I=
P side=20
and write 256k blocks to tape...in some cases this is recommended</SPAN></D=
IV>
<DIV><SPAN class=3D184482113-12042006></SPAN> </DIV>
<DIV><SPAN class=3D184482113-12042006>the SCSI card and driver are the keys=20
here.</SPAN></DIV>
<DIV><SPAN class=3D184482113-12042006>In the past, default "Windows" SCSI d=
rivers=20
will not work over 64k, which is why Veritas recommends using their tape=20
drivers.</SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=3D184482113-12042006>Paul</SPAN></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D1>-- </FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px soli=
d; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft><FO=
NT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
veritas-bu-admin AT mailman.eng.auburn DOT edu=20
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of
</B>Scot=
t=20
Jacobson<BR><B>Sent:</B> April 5, 2006 4:18 PM<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu; Sekhon S.<BR><B>Subject:</B> Re:=20
[Veritas-bu] LTO3 maximum block size of 65536 bytes; abuffer size of 2621=
44=20
cannot be used<BR><BR></FONT></DIV>
<DIV>Simrat,</DIV>
<DIV> </DIV>
<DIV>I've seen many discussions in this forum about using 262144 for a bu=
ffer=20
sizes on Windows, and most of those discussions talk about it not be=
ing=20
recommend or successful based on Windows TCP/IP Stack size limitation.&nb=
sp;=20
Others have indicated they have been able to get buffers sizes like=20
this to work if your able "tweek" SCSI card parameters or regis=
try=20
settings as you've mentioned.</DIV>
<DIV> </DIV>
<DIV>Based on your error message, I'd say the registry may have changed, =
but=20
again, your fighting a fixed block size between the device and =
OS IP=20
Stack communications that changes it back to 64K.</DIV>
<DIV> </DIV>
<DIV>I've also read here that there is a unsupported Windows OS parameter=20
change that can be made as well, but again, I don't recall from anyone in=
this=20
forum indicating they've been able to make it work=20
successfully.</DIV>
<DIV> </DIV>
<DIV>I abandoned my effort two years ago to get this to work and now=
use=20
Linux Media and Master servers to resolve this issue.</DIV>
<DIV> </DIV>
<DIV>Scott</DIV></BLOCKQUOTE><pre>>>> This e-mail and any attach=
ments are confidential, may contain legal, professional or other privileged=
information, and are intended solely for the addressee. If you are not th=
e intended recipient, do not use the information in this e-mail in any way,=
delete this e-mail and notify the sender. CEG-IP1
</pre></BODY></HTML>
------_=_NextPart_001_01C65E38.69E48242--
|
