The "TSM for UNIX Using the Backup-Archive Clients" manual states:

Your default domain is set with the domain option in your client user
options file (see Domain). If you do not have the domain option set, the
default domain is all local file systems.

If domain is not used to specify file systems in your client options file,
TSM uses the
all-local parameter as the default.

When performing a backup with domain=all-local, files handled by automounter
and
loopback file systems are not 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
and all previously backed up data from automounted file systems is expired;
if it runs via the scheduler, auto-mounted file systems get backed up again.
Can anyone help?  We don't want this stuff backed up from where it is
automounted; only from the file servers that own the data.

I'm running TSM server 4.1 on AIX 4.3.3 and TSM client 3.7 on Solaris 2.7 (I
tried upgrading the client to 4.1, but despite the fact that the Tivoli
on-line readme for this version states:  "The backup/archive client requires
the following software in order to run:  Sun Solaris 2.6, Solaris 7 in both
32bit and 64bit kernel mode or Solaris 8/64bit", I guess they were really
just kidding because 4.1 will not install on Solaris 7 unless the kernel
mode is 64 bit, which we are not.)

Anne Short
Lockheed Martin Enterprise Information Systems
Gaithersburg, Maryland
301-240-6184
CODA/I Storage Management

Reply via email to