We’re in a situation where we want to temporarily prevent our users from ever writing directly to our tape drives. In the event that our primary random access stgpools hit 100% utilization, we want client backups to fail rather than failover over to the next, sequential access stgpool. As far as I can see, there are two ways to accomplish this:
1) Set maxnummp for all nodes to 0. This should prevent them from access a tape drive when backing up, but would also prevent them from access a tape drive to do a restore. Clearly not a good option. 2) Set the Next Storage Pool value for the primary random access stgpools to null. With this method, migrations would no longer work, but we could still move data to tape using the “move data” command on the random access volumes. I’m leaning towards option 2, but I would like to know if anyone cam think of another way to prevent client backups from going directly to the tape drives. Thanks, -- Brian Kunst Storage Administrator Large Scale Storage & Systems UW Information Technology
