Previous Chapter : Next Chapter : Top
Access to BACKUP.UNET functions depends on whether you are a user,an operator, or an administrator.
For specific instructions on how to add, delete, and change user privileges, refer to the BACKUP.UNET Getting Started Guide for information on managing privileges using your interface.
Privileges are hierarchically organized; that is, users have the most restrictions while users with Administrator privilege have the most privileges. There are three basic levels of privileges:
Table 3-1 shows the functions associated with each privilege.
TABLE 1. 3-1 BACKUP.UNET Privileges
------------------------------------------------------------------
AUTHORIZATION LEVEL
FUNCTION User Operator Administrator Operator/
Administrator
------------------------------------------------------------------
Backup Files 4* 4 4
Restore Files 4 4 4** 4
List Backed-Up Files 4 4 4 4
Update Network 4 4
Configuration
Edit Admin Files 4 4
Manage Media 4 4
Answer Requests 4 4
View Audit Trail 4 4 4 4
Recycle Dumps 4* 4 4
------------------------------------------------------------------
A BACKUP.UNET user is anyone on a participating system who can log in to the BACKUP.UNET system. Users can initiate their own restore requests, thus eliminating the need for administrators to find archived files.
A BACKUP.UNET operator is responsible for managing the backup media, including mounting and unmounting backup media and answering system requests.
A BACKUP.UNET administrator is authorized to set up the various system parameters for backups and restores, and to start backups.
Generally the operator and administrator functions are performed by different individuals, but one person may be given both areas of responsibility.
Information about users and their privileges is stored in the Operator table on each BACKUP.UNET host. The Operator table includes records for all users authorized to access the current host as operators, administrators or operator/ administrators. These three categories allow for varying host requirements.
Users not designated as operators, administrators, or operator/administrators do not have a record in the Operator table.
Each record specifies what privileges a user has on the local host when working from (that is, logged into) the named host, which may be a remote host.
For example, Figure 3 1 illustrates three systems that are part of a network.
Each of these situations requires a separate record in the Operator table on each host.
Graphic:* Configurable using message number 18 in the 'nbkMSGS' file
Figure 3-1. Sample Operator Table Records
(Refer to User
Operator
Administrator
Operator/Administrator
How Privileges Work
A user assigned to an ALL host is given the specified privileges on the local host from every remote host on the BACKUP.UNET network. A record for that user on a specific host is also valid. In this instance, user permission is granted based upon the combination of both records.
For example, user melvin has an ALL host record on host loki with administrator privileges. He also has a record on loki that is specific to host loki with administrator and operator privileges. Permission for melvin is granted based on a combination of the two host records:
Note: You must have operator privileges on the poolmaster from the host you are using to add a volume to a pool on a remote host. For example, the poolmaster is host loki and you are on host thor that has a device associated with the pool. If, on host loki, you do not have either an ALL host record or a host thor record with operator privileges, you cannot add volumes to the pool.