I'd tend to look at it the other way around, ideally (for restores) you 
want 1 saveset per drive but as backups often go slower than the drives 
streaming speed you may need to increase the number of seesions to keep 
the drive streaming, this is independent of the drive type. Having said 
that I've found that going from DLT7000 to LTO-1 the impact on restore 
speeds from interleaved savesets seems to have lessened, I've not 
investigated this but wondered if it is perhaps due to the large buffer on 
the LTO-1 drives.
We still use the default targets sessions of 4 that we used when using DLT.

On Thu, 20 Jul 2006 22:27:15 -0400, George Sinclair 
<George.Sinclair AT NOAA DOT GOV> wrote:

>Hi,
>
>We're using SDLT 600 drives. NetWorker sets the default target sessions
>to 4. Seems this is always the case regardless of the drive type.
>Obviously, mileage will vary, and experimentation will determine best
>balance between backup/recover time. However, our older SDLT 220 drives
>have always been between 4-5 and we found that to be adequate for backup
>time without any major impact on recover speeds. Seems that if the 600
>drives are so much faster, though, then we ought to be able to increase
>the target sessions, assuming this increases backup speed, and still
>recover just as fast as we would have with the slower 220 drives with
>target sessions set to 4. Maybe it doesn't work that way, so just
>curious what kind of values others are using or have found to be the
>best for these drives.
>
>George

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER