John,

We do this, but not via buta.

We run a scheduled ADSM backup of our AFS DB files, daily, from one of
our AFS dbservers (where we have an ADSM client running). Since we
use collocation, we ultimately have one easily identifiable tape
associated with this client. Because of the way we handle offsite tapes,
and since we know we want a copy of this tape to be part of the regular
offsite storage, we have associated this client with a unique management
class (and storage pool) set up for this purpose. This is done within the
client's inclexcl file (include * mgmtclass). We use an 'absolute' copy mode,
and 'shared static' copy serialization in the copygroup (type=backup). The
client's DOMAIN is '/usr'.

On the server, the client schedule contains the following parameters of
interest:
                Action: Selective
                Objects: /usr/afs/db/*
So, backups of this client are limited to these specific files.

Hope this helps.

--Ruth
On Jan 11,  4:24pm, "J. O'Neall" wrote:
On Jan 11,  4:24pm, "J. O'Neall" wrote:
}
} The title about says it:  I'm using the buta ADSM client to backup AFS
} volume sets into ADSM.  But the AFS backup DB needs to be backed up.  I'd
} like to back it up into ADSM, too.  (Don't like attributing a tape drive to
} one machine just to back up a DB once a day.)
}
} How do other folks handle this?
}
} ------------
} John O'Neall                 tel. +33 (0)4 78 93 08 80
} Centre de Calcul de l'IN2P3  fax. +33 (0)4 72 69 41 70
} Villeurbanne, France         email:  jon AT in2p3 DOT fr