This is a multi-part message in MIME format.
------_=_NextPart_001_01C64E7C.EECEC02C
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Ok interesting on the licensing.
=20
I thought the VTL vendors licensed on a per TB basis, but in order to
use it with NBU, you had to license with Veritas for the number of
frices you are presenting to NBU.
=20
Yeah, you can still write multiple jobs to the VTL (mpx to a virtual
tape)
otherwise, you (or I) would want to create a LOT of virtual drives...and
with a lot of drive simultaneously active, an "inline" VTL (need to go
back and refresh on terminology) would write one physical tape for every
virtual tape, so you could end up with a lot more tapes "in play" on any
given day.
=20
the key reason I want to go to VTL at this point is that we have many
different business lines here with different retention policies, so even
though we mpx up to 8 for our LTO3 drives and 100Mb/s clients, we end up
with a bunch of jobs queued up waiting for that one last client in a
policy to finish....the client is pushing over 100Mb/s, the drive is
shoeshining itself to pieces, throughput sucks and it could take an hour
before this job finshes to release a free drive, while there are 20 jobs
in a different policy queued up waiting for a free drive to put in
another tape (different pool or retention or whatever.)
=20
seems DSSU would be easy in this case, to just set the max number of
jobs, and let er rip.....different policies, retentions, etc, all write
at once and get sorted, hopefully in some efficient manner, after the
fact.
=20
with a VTL, things still need to be treated as tape drives, so there's a
different way of engineering/designing things.
=20
Paul
-----Original Message-----
From: Steven L. Sesar [mailto:ssesar AT mitre DOT org]=20
Sent: March 23, 2006 8:14 AM
To: Paul Keating
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] on the subject of disk based
backups....
=09
=09
Not true about the licensing piece. VTL's are licensed on a per
TB basis. I believe that you can also write multiple jobs to VTL, as
well - I don't see why you couldn't.
=09
=09
Paul Keating wrote:=20
I'm also interested in thoughts regarding VTL vs DSSU.
DSSU interests me mostly because I can write multiple
jobs at once without any regard for tape pool, mpx or not, retention,
etc.....
...then it all gets sorted out to appropriate tapes
during the destaging
VTL still presents itself to NBU as a tape, so each
virtual tape drive must be licensed with Veritas, in additional to the
physical tape drives (unless the VTL is run inline, though there could
be issues there regarding estimated compression, etc.)=20
Just a couple things off the top of my head.
Just wondering who is using DSSU, adn who is using VTL,
adn why you made that choice....ie.what were the key requirements for
your environment that made one option better than the other.
Paul
--=20
=
=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
=09
Steven L. Sesar
Senior Operating Systems Programmer/Analyst
UNIX Application Services R101
The MITRE Corporation
202 Burlington Road - KS101
Bedford, MA 01730
tel: (781) 271-7702
fax: (781) 271-2600
mobile: (617) 893-9635
email: ssesar AT mitre DOT org
=09
=
=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=20
------_=_NextPart_001_01C64E7C.EECEC02C
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><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 text=3D#000000 bgColor=3D#ffffff>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2>Ok=20
interesting on the licensing.</FONT></SPAN></DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2>I=20
thought the VTL vendors licensed on a per TB basis, but in order to use =
it with=20
NBU, you had to license with Veritas for the number of frices you are =
presenting=20
to NBU.</FONT></SPAN></DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2>Yeah,=20
you can still write multiple jobs to the VTL (mpx to a virtual=20
tape)</FONT></SPAN></DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2>otherwise, you (or I) would want to create a LOT of virtual =
drives...and=20
with a lot of drive simultaneously active, an "inline" VTL (need to go =
back and=20
refresh on terminology) would write one physical tape for every virtual =
tape, so=20
you could end up with a lot more tapes "in play" on any given=20
day.</FONT></SPAN></DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2>the=20
key reason I want to go to VTL at this point is that we have many =
different=20
business lines here with different retention policies, so even though we =
mpx up=20
to 8 for our LTO3 drives and 100Mb/s clients, we end up with a bunch of =
jobs=20
queued up waiting for that one last client in a policy to=20
finish....the client is pushing over 100Mb/s, the drive is shoeshining =
itself to=20
pieces, throughput sucks and it could take an hour before this job =
finshes to=20
release a free drive, while there are 20 jobs in a different policy =
queued=20
up waiting for a free drive to put in another tape (different pool or =
retention=20
or whatever.)</FONT></SPAN></DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2>seems=20
DSSU would be easy in this case, to just set the max number of jobs, and =
let er=20
rip.....different policies, retentions, etc, all write at once and get =
sorted,=20
hopefully in some efficient manner, after the fact.</FONT></SPAN></DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2>with a=20
VTL, things still need to be treated as tape drives, so there's a =
different way=20
of engineering/designing things.</FONT></SPAN></DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D558191513-23032006><FONT face=3DArial color=3D#800000 =
size=3D2>Paul</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 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> =
Steven L. Sesar=20
[mailto:ssesar AT mitre DOT org] <BR><B>Sent:</B> March 23, 2006 8:14=20
AM<BR><B>To:</B> Paul Keating<BR><B>Cc:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> Re: [Veritas-bu] =
on the=20
subject of disk based backups....<BR><BR></FONT></DIV>Not true about =
the=20
licensing piece. VTL's are licensed on a per TB basis. I believe that =
you can=20
also write multiple jobs to VTL, as well - I don't see why you=20
couldn't.<BR><BR><BR>Paul Keating wrote:=20
<BLOCKQUOTE=20
=
cite=3Dmid4A14D0A1A982B04B8DFC50EBDB81D0A2045429AB AT BOC-EXMAIL1.bocad DOT
bank=
-banque-canada.ca=20
type=3D"cite">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<DIV>
<P><FONT size=3D2>I'm also interested in thoughts regarding VTL vs=20
DSSU.</FONT></P>
<P><SPAN class=3D020475812-23032006><FONT face=3DArial size=3D2>DSSU =
interests me=20
mostly because I can write multiple jobs at once without any regard =
for tape=20
pool, mpx or not, retention, etc.....</FONT></SPAN></P>
<P><SPAN class=3D020475812-23032006><FONT face=3DArial =
size=3D2>...then it all=20
gets sorted out to appropriate tapes during the =
destaging</FONT></SPAN></P>
<P><SPAN class=3D020475812-23032006><FONT face=3DArial size=3D2>VTL =
still presents=20
itself to NBU as a tape, so each virtual tape drive must be licensed =
with=20
Veritas, in additional to the physical tape drives (unless the VTL =
is run=20
inline, though there could be issues there regarding estimated =
compression,=20
etc.) </FONT></SPAN></P>
<P><SPAN class=3D020475812-23032006><FONT face=3DArial size=3D2>Just =
a couple=20
things off the top of my head.</FONT></SPAN></P>
<P><SPAN class=3D020475812-23032006><FONT face=3DArial size=3D2>Just =
wondering who=20
is using DSSU, adn who is using VTL, adn why you made that =
choice....ie.what=20
were the key requirements for your environment that made one=20
option better than the other.</FONT></SPAN></P>
<P><SPAN class=3D020475812-23032006><FONT face=3DArial=20
size=3D2>Paul</FONT></SPAN></P></DIV></BLOCKQUOTE><BR><BR><PRE =
class=3Dmoz-signature cols=3D"72">--=20
=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
Steven L. Sesar
Senior Operating Systems Programmer/Analyst
UNIX Application Services R101
The MITRE Corporation
202 Burlington Road - KS101
Bedford, MA 01730
tel: (781) 271-7702
fax: (781) 271-2600
mobile: (617) 893-9635
email: <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:ssesar AT mitre DOT org">ssesar AT mitre DOT org</A>
=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=20
</PRE></BLOCKQUOTE></BODY></HTML>
=00
------_=_NextPart_001_01C64E7C.EECEC02C--
|
