ADSM-L

Re: Message from Brett Walker

1993-10-25 09:24:18
Subject: Re: Message from Brett Walker
From: Leonard Boyle <SNOLEN AT VM.SAS DOT COM>
Date: Mon, 25 Oct 1993 09:24:18 EDT
On Wed, 20 Oct  1993 13:04:07 PDT Brett Walker said: Leonard,  I will also try
>to one of these...
>
>>(4)  Can  someone elaborate  on  how  ADDSM  works  with file  servers?  The
>>    following question From Rick Chang's survey would suggest that there are
>>    some changes that are needed.
>>
>>> 11. Would you like  a client to be able to restore  files that were backed
>>      up(to an ADSM sever) by a file server?
>>>
>>>      __ 1.A must __ 2.Very helpful __ 3.Nice to have
>>
>>    Can the root user restore any  object to any location? Is there security
>>    provided to prevent one user  from restoring another's files (unless the
>>    restoring id  has read permission)?  Are timestamp and  file permissions
>>    preserved when an object is restored? ACL lists?
>>
>>    Is there any support for system or group administrators. If not can this
>>    be handled  with an exit.  For example one could  have an MIS  person in
>>    charge of accounts payable.  You would want them to be able  to act as a
>>    surrogate for  the end  users of  the accounts  payable software.  Or an
>>    instructor over a set of students.
>>
>>    In an environment where workstations are not personal and people can log
>>    onto one of n machines, how does one handle backups and restores. assume
>>    the end-user  file directories are stored  on a set of  file servers. Do
>>    you have a  separate backup for each user directory  tree on the server.
>>    Or is the server  backed up as a separate unit. If  the server is backed
>>    up as a separate unit can the end-user still request restores of her/his
>>    file(s)?
>
>      Basically, with the  Unix clients, root can restore  anything backed up
>      under his machine id, including ACLs, etc (Unix guys, correct me if I'm
>      wrong).
>
>      As for group administrators, do you  mean someone who can restore files
>      to someone  else's workstation for  them? We don't really  provide that
>      capability. If  the files  are on  a file server,  then you  could have
>      someone in charge of backing up/restoring certain directories.
>
>      Currently  with the  Netware client,  when you  backup the  server, the
>      supervisor backs the  server up, and only a supervisor  can restore the
>      files. So  the question becomes, when  user files exists on  the server
>      and are backed up,  do you want the end users to  be able restore those
>      files themselves (either back to the  server or to their local machine)
>      or simply let the supervisor do it? I understand this is
> a desirable function,  but is it a must have requirement,  and are there any
>      other backup products that allow this level of granularity?
>
>Brett Walker

VMBACKUP is a VM backup product that  has this level of granularity. Of course
it is  not that way right  out of the box,  but they do provide  an exit which
allows a site to code as needed.

For  some of  these lan/server  setups you  have to  think of  them more  as a
mainframe from an administrative point of view.

You can  have a number of  Unix workstations which  may or may not  have local
files and/or files on  one or more central file servers.  The end-users do not
have  root  authority  for their  machine.  An  end  user  can sign  onto  any
workstation and  her/his files will be  linked to their session.  The files on
the central file server  might be owned by an individual or  they may be owned
by a group or project.

For example in an  University the user might have a  home directory with their
personal files, but they might also use  files that are associated with an EE
course. They might  use other files associated with a  chemistry course. Since
the chemistry or EE course files are not owned by an individual but by a group
of people who support  the course, you might want the  course instructor or TA
to be an administrator for those files.  That is with out having to maintain a
dummy id for that purpose or granting full root authority.

In a business setting  you might have a group of  people working in Personnel.
You might want to  let the manager of the group restore  any file from her/his
group without given  them root authority. Since the file  server may be shared
with 10 other departments. One might also want to allow the mis-programmer who
handles the personnel  programs to restore or archive for  the personnel users
but not for the other users of the file server(s).

You  might want  to allow  Help desk  staffers to  restore all  end-user files
without also granting full root or supervisor privileges

I would assume the  same principals would be in effect  for other file servers
such as novell.
<Prev in Thread] Current Thread [Next in Thread>