ALTMARK <[EMAIL PROTECTED]> writes:
> we're currently running a file based backup of our AFS cell using ADSM.
So are we. We plan to stick with that for the long term, too.
> Our current approach looks like this: A script descends the directory
> tree, checks whether a directory entry is an AFS mountpoint and, if so,
> hands this entry over to ADSM.
You may want to try something more like this: build a list of all the
volumes in your cell (trivial with vos listvol and the like), and then
pass that list to your ADSM backup system. Then fs mkmount mounts for
each volume in turn (or a few at a time) in a scratch directory in AFS and
back up just that volume (checking directories to see if they're mount
points and not crossing mount points). That way, you don't have to know
where any of your volumes are mounted, and you can then optimize the
checking process by storing a list of volumes that you know don't contain
any mount points and turn off the fs lsmount checking for those volumes.
> AFS provides no command that provides the opposite functionality of "fs
> lsmount", i.e. a command like e.g. "fs lsvolmount", which lists the
> mountpoint(s), where a volume is mounted.
We decided we wanted that information, so we now maintain a db file of all
the volume mount points and update it whenever we create a new volume or
move its canonical mount point. It doesn't handle the entire problem,
since volumes can be mounted in multiple locations and by any user, but it
does let us find volumes again and has proven handy for finding volumes
that are no longer being used.
--
Russ Allbery ([EMAIL PROTECTED]) <URL:http://www.eyrie.org/~eagle/>
