... > In my case I will have 60+ filesspaces on 6+ tapes with 8 tape drives > available and have to start from the command line (actually scripted) to > start a session for each tape drive. The real problem is preventing > more than 1 session from asking for the same tape. ...
Collocation by filespace has been suggested as a good approach. In large commercial database environments another approach may be taken. In such an environment, the physical name of the computer is not important: what is enduring and significant is the identity of an application or a database - which may move to another computer over time. In such big filespace cases it may be more natural to use the Nodename client option to group backups by a given logical identity, to flexibly keep things together or separate as best serves your needs. Richard Sims
