This is a multipart message in MIME format.
--=_alternative 004A1DC38025713A_=
Content-Type: text/plain; charset="us-ascii"

Hi Paul,

  from my experience what you say about DSSU is incorrect, a single DSSU 
cannot stage the data off to multiple tape tape pools - if you have a 
requirement to stage to different tape pools you need to have a at least 
one DSSU per tape pool,

                cheers Andy.






"Paul Keating" <pkeating AT bank-banque-canada DOT ca>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
23/03/2006 13:05

 
        To:     <veritas-bu AT mailman.eng.auburn DOT edu>
        cc: 
        Subject:        [Veritas-bu] on the subject of disk based backups....


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.) 
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


--=_alternative 004A1DC38025713A_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Hi Paul,</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; from my experience what you say about 
DSSU is incorrect, a single DSSU cannot stage the data off to multiple tape 
tape pools - if you have a requirement to stage to different tape pools you 
need to have a at least one DSSU per tape pool,</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
&nbsp; &nbsp; cheers Andy.</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>&quot;Paul Keating&quot; &lt;pkeating AT 
bank-banque-canada DOT ca&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT 
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">23/03/2006 13:05</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; 
&nbsp; &nbsp; &nbsp;&lt;veritas-bu AT mailman.eng.auburn DOT edu&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; 
&nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; 
&nbsp; &nbsp; &nbsp;[Veritas-bu] on the subject of disk based 
backups....</font></table>
<br>
<br>
<br><font size=2 face="Times New Roman">I'm also interested in thoughts 
regarding VTL vs DSSU.</font>
<p><font size=2 face="Arial">DSSU interests me mostly because I can write 
multiple jobs at once without any regard for tape pool, mpx or not, retention, 
etc.....</font>
<p><font size=2 face="Arial">...then it all gets sorted out to appropriate 
tapes during the destaging</font>
<p><font size=2 face="Arial">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.) </font>
<p><font size=2 face="Arial">Just a couple things off the top of my head.</font>
<p><font size=2 face="Arial">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.</font>
<p><font size=2 face="Arial">Paul</font>
<p>
<p>
--=_alternative 004A1DC38025713A_=--