About the NetBackup-Java Administration Console on UNIX/Linux
|Article:HOWTO33594|||||Created: 2010-10-28|||||Updated: 2011-03-10|||||Article URL http://www.symantec.com/docs/HOWTO33594|
These processes can be run on two different NetBackup hosts. This distributed application architecture holds true for the UNIX Backup, Archive, and Restore client graphical user interface (jbpSA) as well.
The administrator first starts the NetBackup-Java Administration Console interface using one of the following methods:
The application server is the host that is specified in the NetBackup Administration Console logon dialog box and authenticates the logon credentials of the user. The credentials are authenticated by using standard UNIX user account data and associated APIs.
To log in to any NetBackup Administration Console, your login credentials must be authenticated from the connecting master or media server. This is true whether or not NetBackup Access Control (NBAC) is in use.
An exception is the use of the File > Change Server capability in the NetBackup Administration Console. The Change Server capability allows administration of a remote server (a server other than the one specified in the NetBackup Administration Console logon dialog box).
Regardless of which server is administered, all administrative tasks that are performed in the NetBackup Administration Console make requests of the application server. All tasks are run on the application server host, whether the server is remote or whether the server is specified on the logon dialog box.
However, regardless of which NetBackup authorization method is configured, authorization for tasks in the Administration Console is specific to the server being administered. For example, NetBackup-Java authorization capabilities are in use on Host_A. Use Change Server to change to Host_B. The permissions are honored as configured in the auth.conf on Host_B.
Article URL http://www.symantec.com/docs/HOWTO33594