Um...there's a thread in the discussion list wherein it is
     acknowledged by IBM that an incremental *ignores* the domain
     specification.


______________________________ Reply Separator _________________________________
Subject: Re: Local/Network File Spaces
Author:  "Moir;Betsy" <Betsy.Moir AT LN.SSW.ABBOTT DOT COM> at ~Internet
Date:    3/6/98 1:45 PM


Greg -

There's an option you can put in the options file that limits the drives
(domains) that will be backed up:

DOMAIN C: D:

That would backup only the C and D drives.  If your users have access to
their own options file, then this doesn't *guarantee* they won't go in there
and change that, but if they're anything like most of our workstation
clients, they aren't much interested in how it works, just that it does.

It's my understanding, too, that ADSM defaults to backing up only locally
attached drives unless told to do otherwise.




ADSM-L AT VM.MARIST DOT EDU on 03/06/98 11:57:14 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ INTERNET
To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
cc:
Subject: Local/Network File Spaces

Hello!  Me again :-)

I am running the new 3.1 server and client on NT.  I was wondering about
local and network file spaces.  We have ADSM backing up all files on the
server, and workstations that attach to the server.  When ADSM backups a
workstation, does it backup network mapped drives as well?  I am just
concerned that files located on the server, are being backed up twice, (once
directly on the server, and through the client's drive mappings) therefore
taking up more tape space.  Is there a way to force the client to ONLY
backup local files?

Sure would appreciate any information you might have.
Thanx!

Greg Garrison
Bank of America
Credit Card Group
602-597-2611