Hi Oscar,

It is not the most elegant solution - but it is the one that will work.

I know of no other way to "force" sessions to one drive at a time when you have 
multiple drives all in one pool and a group with multiple savesets. The only 
way to direct the save streams is with your pool and group selections / 
restrictions. 

But - that does mean that you potentially have to "sacrifice" one drive ... 

You might consider doing "raw" backups on the drives with "trillions" of files. 
There are some disadvantages (such as not being able to do a file level 
recovery) - but the backups are WAY fast. Thsi will all depend on how big your 
drives are and how often you recover and what you have to recover. 

HTH,

Regards,
Riaan

--- SNIP ---
Is there any way to configure NetWorker to add new saves to one drive at a 
time, up to the number of target sessions of the drive or similar? As it 
is now, load is spread evenly among the devices. This is a problem when 
you have a few troublesome clients, that have 386 trillion files each, and 
thus hog each drive with a never-ending save for hours and hours. It would 
be good if one could somehow get all those slow saves onto one drive.

One idea that I have is to create a dedicated pool for this type of 
clients, and then locking that pool to only one drive, but that doesn't 
seem like the most elegant solution..

//Oscar
--- SNIP ---

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=