Just a system programmer's tip in this area:
In Unix, you can quickly test for a given mount point directory name
being occupied or not occupied with a mount by performing the command
'ls -di' on it: if the inode number reported is 2, then a mount is
present there, which is to say that it is then
Thanks, we did some checking as to TSM's behavior if a file system drops
during a backup. It correctly sees that files that should exist no longer
do and puts up an error. We were concerned that our window of vulnerability
might extend past the running of the preschedulecmd. Again, thanks for
po
Write a script in your language of choice that compares the mount
list with a list of crucial filesystems like "/etc/
filesystems_crucial_to_backup"
Launch this script from the preschedulecmd, and if it returns a non-
zero code, the backup won't run.
For extra surety, you can look for files that
