You are exactly right - it is way too easy, and has serious system integrity
issues in my mind.  Based on this one issue, I will not distribute V3 clients
until it is fixed, unless there is some very excruciating reason to do so.
Unfortunately, in the Macintosh area, OS8 support might be that reason......

ADSM development has agreed to change this design.  Unfortunately, there is
not an expectation on when we will see it.

I've beaten this horse enough here before.  If you want to talk about it
more, please feel free to email me directly.

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: Re: It's too easy !
Author:  owner-adsm-l (INTERNET.OWNERAD) at SNADGATE
Date:    4/1/98 1:28 PM


     You didn't miss a thing.  This is being marketed as a FEATURE!  The
     gui ignores the domain parm in dsm.opt, but I've been told that the
     command line and scheduler do not (I'm not willing to try).

     If the gui's stay this way, then they're useless "cow droppings"

     I'm hoping someday the ADSM developers will recognize and admit this
     to be the major FLAW that it is, as opposed to adding menu bar items
     to do what the client is supposed to be doing in the first place!

     :-(

     Not just my opinions....


______________________________ Reply Separator _________________________________

Subject: It's too easy !
Author:  Bob Matthews <Robert.Matthews AT SEINF.UNIGE DOT CH> at ~Internet
Date:    4/1/98 4:38 PM


We've been looking at the implications of migrating our PC and Mac clients to
ADSM Version 3 and have come to the conclusion that it's far too easy for users
to backup all accessed disks, both local and remote. When you start the Mac gui,

for example, a window opens containing the client's name or address which
represents the top of the filespace tree. It is sufficient to check this and
start the backup to have all visible files, both local and remote, backed up. If

the client is accessing disks on a remote server or a cd juke box the entire
contents will be backed up! In order to avoid this the user must do something,
namely expand the filespace tree and deselect the remote filespaces. In a
university environment, where anarchy reigns, this is not an acceptable
scenario. In their haste on Friday afternoon users will simply take the easy
option and backup the entire universe by checking the top of the tree.

Are we missing something or have others experienced and/or solved this problem?

Bob Matthews,
University of Geneva.