--VGt7.44JlZln4S.1q5gn4.ZSp2oV
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C65E35.AC88DEE3"
content-class: urn:content-classes:message
------_=_NextPart_001_01C65E35.AC88DEE3
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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
------_=_NextPart_001_01C65E35.AC88DEE3
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!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.2800.1170" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<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 IP side=20
and write 256k blocks to tape...in some cases this is =
recommended</SPAN></DIV>
<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 drivers=20
will not work over 64k, which is why Veritas recommends using their tape =
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 =
solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=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>Scott=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 =
262144=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 =
buffer=20
sizes on Windows, and most of those discussions talk about it not =
being=20
recommend or successful based on Windows TCP/IP Stack size =
limitation. =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 =
registry=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></BODY></HTML>
=00
------_=_NextPart_001_01C65E35.AC88DEE3--
--VGt7.44JlZln4S.1q5gn4.ZSp2oV
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
La version fran=C3=A7aise suit le texte anglais.
---------------------------------------------------------------------------=
---------
This email may contain privileged and/or confidential information, and the =
Bank of
Canada does not waive any related rights. Any distribution, use, or copying=
of this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediat=
ely from
your system and notify the sender promptly by email that you have done so.=20
---------------------------------------------------------------------------=
---------
Le pr=C3=A9sent courriel peut contenir de l'information privil=C3=A9gi=C3=
=A9e ou confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute dif=
fusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient pa=
r une
personne autre que le ou les destinataires d=C3=A9sign=C3=A9s est interdite=
Si vous recevez
ce courriel par erreur, veuillez le supprimer imm=C3=A9diatement et envoyer=
sans d=C3=A9lai =C3=A0
l'exp=C3=A9diteur un message =C3=A9lectronique pour l'aviser que vous avez =
=C3=A9limin=C3=A9 de votre
ordinateur toute copie du courriel re=C3=A7u.
--VGt7.44JlZln4S.1q5gn4.ZSp2oV--
|
