Curtis Preston wrote:

The reason we multiplex is we have to. We are backing up over 400 clients per night in a 12 hour window. Also as I mentioned in a previous post, we are limited in the number of devices we can use with Networker "Network Edition". We have room for 16 virtual

drives, and without multiplexing, we would never complete our
nightly schedule.>

If I may be so bold, I would suggest that someone with 400 clients should probably upgrade to power edition.

Agreed. In our case this type of issue always comes down to funding

Target Sessions is not an absolute limit.

You are correct in your interpretation of how target sessions works. Prior to 7.3, the best you could do was to set server parallelism to <desired mpx number> times <number of drives>. It was a hack at

best.

However, with 7.3, you have the maximum jobs setting right next to target sessions. If you set that value, it will limit the number of jobs that are sent to that device.

What I would really like to see is an improvement to the VTL software. I
don't see why they have to read all the data on a virtual tape to
migrate one multiplexed saveset. After all, it is really just data on
disk. With some clever programming, I believe the VTL software could
eliminate the throughput problem with reading a multiplexed saveset.

Thanks for your help.

Mark

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 with 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