Hi Kelly. The serialization is set to "Shared static".  I understand
that if
the file or directory is modified during each backup attempt, ADSM does
not back it up.

The files in question are not opened or modified during backup. I
recently
ran a test backup of these files and the backup completed successfully
without any mount or dismounts.

Here are my assumptions(please forgive):
1.  The first backup went into a continous mount/dismount loop because
it
     attempted to fill up a tape volume which was at 100% filling. ADSM
is
     so sufficient that it will not mount another volume until it
completely
     fills up a tape to 100% FULL. So when it tried to backup another
file
     but in the current filling tape does not have enough free-space, it
dismount
     the tape attempting to mount a scratch tape.  But ADSM server said,
wait!,
     I need to fillup the filling tape, and so therefore, mount the same
tape and do
     this over and over.

2.  The test that I ran completed successfully without any
mount/dismounts
     because it used a new scratch tape.  The tape had enough free space
to
     accommodate all files.

I thought ADSM would release the 100% filling tape and mount a new
scratch
tape. But it did not.

Suggestions or comments are welcome. :-)

Aloha,
Angel Bugarin
Sprint/Hawaii

   -----Original Message-----
   From:       lipp [SMTP:lipp AT storsol DOT com]
   Sent:       Tuesday, April 13, 1999 11:29 AM
   To:         ADSM-L
   Cc:         lipp
   Subject:    Re: Loop?

   What is the serialization parameter on the copy group?  If it is
   shrstatic
   or shrdynamic, and the file is open, the client may keep trying to
   backup a
   file.

   Kelly J. Lipp
   Storage Solutions Specialists, Inc.
   www.storsol.com
   lipp AT storsol DOT com
   (719)531-5926

   -----Original Message-----
   From:   ANGEL BUGARIN
   Sent:   Tuesday, April 13, 1999 2:23 PM
   To:     ADSM-L AT VM.MARIST DOT EDU
   Subject:        Loop?

   Hello Everyone.

         Yesterday afternoon, I've completed the migration of ADSM
   Server
         Version 2 to Version 3.  I had also applied PTF to the server
   to
         bring it up to 3.1.2.20.

         This morning we've run an archive backup on a client which is
   still
         at 2.1.0.7.  There are about 30K files with the average of 476
   bytes
         each.

         At some point, the server seems to be in a loop with a
   particular
   file.
         The tape being used is 100% filling. The same tape is being
   dismounted
         and mounted.  I had to Ctrl-c to break out of that loop.

         Has anyone ever experienced the same problem and fixed it?

   Aloha,
   Angel Bugarin
   Sprint/Hawaii



--openmail-part-0bcd8321-00000001--
=========================================================================