Jayson,
20 volume pools, man why do folks do that? What are they thinking when they run the system this way? So much work and so little time to Fish.
You have a small tape library, so I'm thinking you don't have allot of systems to backup, with that said, lets get down to business.
You have one robot one library and on master backup server.
You will only need
1: 1 volume pool
2: 2 possibly 3 Volume Pools (Spare_tapes, NetBackup and maybe one Called Oracle)
Lets say you have UNIX servers and NT servers, applications and databases....
For each O.S You will need one Policy just to backup flat Files
1: One Policy lets call it "UNIX" for the all the "flat" files you want to backup, put ALL the UNIX Clients into this Policy and set the Sched's for it.
2: Another Policy lets call it "Winders2000" stick those clients in here
3: Another Policy called "Winders2003" stick those clients in here
4: Another Policy called "NT_SERVERS" (NT4.0) stick em here
5: Another Policy called "Exchange"" stick them in here
6: Another Policy called "NAS" (ndmp) Stick dem here
7: Another Policy called "Lotus Notes" goes here
All the Policy's above get to use the NetBackup Volume Pool
Now for the Database Policy's, make one for each
1: Make one for each Database - hostname system: like
SERVERNAME_ARCHIVES
SERVERNAME_ORA_HOT
SERVERNAME_EXPORTS
SERVERNAME_SNAPS
ALL the Policy's above get to use the "Oracle" Volume Pool
Just keep in mind, Netbackup keeps track of everything that backed up, including what tapes are used, so you don't need all the Fing pools!
JD