Strongly encourage use of the scheduler and the scheduler deamon.  The scheduler
honors the default domain of all-local on all platforms.

If the gui will be used, educate them to use the action pulldown and
"backup domain".  You should be able educate the students, that's why they are
there, right?, but good luck with the professors!

Sadly, there isn't any fool proof method if the gui is used.

My clients are mostly endusers and I haven't had a lot of trouble
with backing up non-local systems.

--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
In <199902101713.MAA73004 AT rigel.dartmouth DOT edu>, on 02/10/99
In <199902101713.MAA73004 AT rigel.dartmouth DOT edu>, on 02/10/99
   at 12:13 PM, Pat Wilson <paw AT NORTHSTAR.DARTMOUTH DOT EDU> said:

>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 this,
>>  but that didn't appear to create any fixes - as several folks pointed out,
>>  in my world it is _never_ acceptable for a user to back up something that
>>  doesn't reside on the local harddrive.
>>
>>  Has anyone come up with anything?  Domains (to my naive eye) aren't going
>>  to work, since the users can call things whatever they want.
>>
>>  Thanks.
>>
>>  Pat Wilson
>>  paw AT dartmouth DOT edu