Re: File System Mount issues

[Richard Sims]

>Although I profess no expertise in traces, it looks like the client builds a
>list of "what's mounted now" when it starts the backup session (ie: not at
>client startup time).   If there is information available contrary to this,
>I'd be happy to see it!

John - That's what I'd expect, too.  However, looking at APARs like IX89778
   suggest that this has not always been the case.  A recent posting
about 3.7 and automounted file systems makes me wonder if this issue has
been fully resolved.  We're at the mercy of whatever changes the client
programmers happen to make at any given maintenance level.
   Richard Sims, BU

File System Mount issues

[Snyder.John]

I've been working on a similar issue (aix 4.3.3 client 3.7.2.0), and have
received
assurances from Support that mounts/umounts after client scheduler startup
shouldn't be a problem.  I did find a document that indirectly sheds some light
on this, at:
http://www-1.ibm.com/servlet/support/manager?rt=0&rs=0&org=apars&doc=4A154C3286E
68E27852567C00015722A

Although I profess no expertise in traces, it looks like the client builds a
list of
"what's mounted now" when it starts the backup session (ie: not at client
startup
time).   If there is information available contrary to this, I'd be happy to
see it!


-

My particular issue was to try to understand what would happen if, some day
when I did an incremental of /home, the filesystem /home wasn't mounted and all
the backup saw was an empty /home mountpointwould it then determine that
everything previously backed up had been deleted and expire everything (except
objects valid according to verdeleted and retonly)??

I understand the answer to this, too, is "no problem", because the server
stores
not only the object name, but the "filespace" that it resided on.  There's a
(fairly
confusing, IMHO) description of this in the client user's guide at:
http://tivoli.com/support/storage_mgr/pubs/v3pubs/v1_html/aix/unixc/cp55tfrm.htm

I see the "filespaces" table on tsm, but can't figure out why some filespaces
aren't
included there.

I must confess that I don't yet understand this, nor how virtualmountpoints
might fit into
the picture.   If anyone can point me to other (better) sources of information
on these
topics, I'd appreciate the help.


Thanks.JRS(hoping to someday grok this in fullness)

-- Forwarded by John Snyder/CTF on 10/12/2000 09:56 AM
---


Richard Sims<[EMAIL PROTECTED]>@[EMAIL PROTECTED]> on 10/11/2000 11:20:18 AM
Please respond to ADSM: Dist Stor Manager<[EMAIL PROTECTED]>@INTERNET
Sent by:  ADSM: Dist Stor Manager<[EMAIL PROTECTED]>
To:  ADSM-L<[EMAIL PROTECTED]>@INTERNET
cc:
Subject:  Re: Trouble with Automounted File Systems Getting Backed Up

>So why are my auto-mounted file systems that are mounted at the time the
>backup starts getting backed up when running via the scheduler?  I've tried
>running with no domain set so that the default takes precedent; no luck.
>I've tried explicitly setting the domain to all-local; no luck.  If I run
>the backup via a command line, no auto-mounted file systems are backed up

Anne - The difference in behavior from scheduler to command line execution
   suggests that the scheduler was started before the automounting
occurred, and that the scheduled client has a problem discerning then
that they are automounted.  Automounted file systems have long been a
problem for the clients, as evident in the APARs database.  Looks like
that continues to be the case at the 3.7 level.
   Richard Sims, BU