Hi Patricia,

Does this APAR seem like a potential fit for your problem, then?

Unfortunately there is no way to reactivate files that are marked
INACTIVE, outside of restoring your database to a time when the files were
still ACTIVE (probably not practical). Once this issue is resolved, then
the next backup will effectively be full, at which time you will have
active versions.

I'm sorry I do not have a better answer than that for you.

Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Patricia Max <pam AT TDO-SERV.LANL DOT GOV>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/10/2002 11:57
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: adsm/tivoli on redhat linux 7.1



Andy, thanks very much for the response.  I would like to test
by increasing the timeo, but I have no idea how to get the directories
that are marked inactive active again.  That's kind of a clumsy sentence.
What's marked inactive are the /home/yyy directory and the /home/yyy/user
directory and all files in the user directory.  The /home filesystem is
fine.
So what can I do to force the /home/yyy directory to become active?

Patricia Max
Los Alamos National Laboratory

>Date:         Tue, 9 Apr 2002 20:37:33 -0400
>From: Andrew Raibeck <storman AT US.IBM DOT COM>
>Subject:      Re: adsm/tivoli on redhat linux 7.1
>To: ADSM-L AT vm.marist DOT edu
>
>Patricia,
>
>I am not familiar with the problem, but there is an APAR for the 4.2
>client, IC31314, that may apply. Here is the description from the APAR
>text:
>
>========================================
>Files may be expired because an OS automounter unmounts a
>filesystem before TSM has processed it.
>-
>During a backup, TSM processes a filesystem in two stages.
>-
>In the first stage, the TSM client compares what files are on
>client filesystems to the files on the TSM server.
>-
>In the second stage, TSM processes each filesystem to
>send changed/new files to the TSM server.
>-
>The automount option of the TSM client will mount a
>filesystem for the first stage.  If the customer has
>multiple filesystems, some filesystems that have
>completed the first stage may need to wait for the
>second stage.  The OS automounter may unmount a
>filesystem due to inactivity before the second stage
>has begun processing the filesystem.  TSM may expire
>files on filesystesms that were unmounted before the
>second stage.
>-
>The TSM client needs to verify that the filesystem is
>still available before beginning the second stage.
-
>Workaround:
>Workaround:
>The customer can increase the idle time allowed by the
>OS automounter.  The customer can also process each
>automounted filesystem independently.  This will help
>to ensure that the second stage begins as soon as the
>first stage has ended.
>========================================
>
>I would recommend that you contact IBM support about this problem so that
>you can either verify that this is the problem, or else continue to
>diagnose the trouble.
>
>Regards,
>
>Andy
>
>Andy Raibeck
>IBM Software Group
>Tivoli Storage Manager Client Development
>Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
>Internet e-mail: storman AT us.ibm DOT com
>
>The only dumb question is the one that goes unasked.
>The command line is your friend.
>"Good enough" is the enemy of excellence.


:wq