You may not be able to run enough target sessions at once (because of only
few clients backing up at the same to the drive) to keep your drive busy and
prevent shoe-shining waits affecting transfer rate, max data stored on the
volumes and drive/tape wear-outs.

Though all it again depends on the drive specifications and network
environments you have as well.


On 9/21/06, Ben Harner <benjamin.harner AT marymount DOT edu> wrote:

Hey All,

I am in the works of changing our backup schema and I have a question
about pools.  Now we have maybe 20 servers in our network and was
playing with the idea of having a pool per group in order to ensure
certain servers are on certain tapes so recovery time will be minimized
and so I can recover more than one server at a time if need be (we have
more than one tape drive).  Right now we have 2 pools with our main
campus servers on one pool and our satellite campus servers on the other
pool.  Are there any issues beside needing a lot of tapes with using 6
or 7 pools in order to have certain servers on certain tapes.  Does it
degrade performance of backups, etc....

Thanks

Ben

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 [email protected] 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

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