I'm not sure you're correct. The Mac "Using the Client" book
(1/99 edition) says, under "domain" (pg 62):
all-local
Backs up all local volumes. This is the default.
All CD-ROM drives, diskette drives, and network volumes are also
included.
Which would seem to indicate that the default is, in fact, "all".
Perhaps the book is wrong?
Pat Wilson
paw AT dartmouth DOT edu
Paul Zarnowski <vkm AT CORNELLC.CIT.CORNELL DOT EDU> writes:
> Pat; The default DOMAIN is "ALL-LOCAL". This is used by the ADSM
> Scheduler when deciding what should be backed up. ALL-LOCAL means all
> local, unmountable, hard disk volumes. I.e., not floppies, not CDROM, not
> network volumes. The DOMAIN does not prevent users from backing up
> whatever they want to - manually. But, it does help if you can train your
> users to use the Scheduler to run their backups.
>
> ..Paul
> --
> At 12:13 PM 2/10/99 +22300819, Pat Wilson wrote:
> >Oops - it's worse than that - most of these clients are Macs (no
> >nice drive letter names). :-<
> >
> >It would be _nice_ to have a "really local" Domain switch, but I
> >don't see one. "all-local" isn't local at all, apparently.
> >
> >Pat Wilson
> >paw AT dartmouth DOT edu
> >
> >
> >> Have you lost your mind?
> >>
> >> Sorry, first thing that popped into my head.
> >>
> >> Is there a domain switch no-non-local or somesuch?
> >>
> >> Perhaps an exclude in a client options set that overrides the client
> and exc
> >ludes all but specific disks like c and d.
> >>
> >> Kelly J. Lipp
> >> Storage Solutions Specialists, Inc.
> >> www.storsol.com
> >> lipp AT storsol DOT com
> >> (719)531-5926
> >>
> >> -----Original Message-----
> >> From: Pat Wilson
> >> Sent: Wednesday, February 10, 1999 7:23 AM
> >> To: ADSM-L AT VM.MARIST DOT EDU
> >> Subject: V3 backup of non-local files
> >>
> >> Ok - shoot me. I'm getting ready to put ADSM clients in the hands of
> >> students and faculty here, and am trying to figure out how to keep them
> >> from backing up everything (local and non-local) that the client can see
.
> >> I've read the discussion that took place on the list last year about thi
s,
> >> but that didn't appear to create any fixes - as several folks pointed ou
t,
> >> in my world it is _never_ acceptable for a user to back up something tha
t
> >> doesn't reside on the local harddrive.
> >>
> >> Has anyone come up with anything? Domains (to my naive eye) aren't goin
g
> >> to work, since the users can call things whatever they want.
> >>
> >> Thanks.
> >>
> >> Pat Wilson
> >> paw AT dartmouth DOT edu
> >
|
