Steve,
        The buta client does lock a fileset when it is backing it up, but the 
procedure for both AFS and DFS backup assumes that you are cloning your 
original filesets, and then sending those backed up versions to tape/ADSM.  
The filesets are cloned with an "fts clone" or "fts clonesys" command, which 
we run out of cron, or theoretically it could be a bos instance too.  Once 
this happens, we run our backups, which are defined in the backup database so 
as to backup all filesets with the ".backup" extension.
        This process ensures that your production filesets are accessible at 
all times.  Hope this information is useful.

-Matt
*---------------------------------------------------------*
*---------------------------------------------------------*
Matt Bacchi                              mbacchi AT us.ibm DOT com
IBM Global Services                    v2bacchi AT btv.ibm DOT com
ADSM & AFS Backup                            


>Hi All,
>
>     Can anyone on this list confirm my colleague's question about
>backing up DFS fileset via adsm's buta?
>
>Thanks,
>
>---------- Forwarded message ----------
>Date: Wed, 19 May 1999 09:49:23 -0400 (EDT)
>From: Stephen G Comings <scomings AT acsu.buffalo DOT edu>
>To: Steven P Roder <tkssteve AT acsu.buffalo DOT edu>
>Subject: Re: TR-52602: backup prevents access (fwd)
>
>Hi Steve...
>
>I checked with our DFS developers and they were not sure if the same
>restriction (ie, filesets inaccessible during backup) applied to buta
>as it did to the DFS butc process.
>
>It would be best to contact ADSM Support on this.