When using the native backup-archive client or the Web client you can logon using a nodename and password or administrative user ID and password. TSM asks for your user ID and compares it to the configured nodename. If they match, TSM attempts to authenticate the user ID as a nodename. If the authentication fails or if the user ID does not match the configured nodename, an error message does not display. Instead, the client attempts to authenticate the user ID as an administrative user ID.
To use an administrative user ID with any of the TSM backup-archive clients the user ID must have one of the following TSM authorities:
For UNIX, Windows, and NetWare: The TSM Web GUI allows access if the administrative user ID has client access over the configured nodename. This permits you to back up and restore files on a remote machine but you are unable to restore files to your own machine. With client access authority you do not have physical access to the data. If you want to use the Web GUI but wish to prevent administrators with client access authority from accessing your machine remotely, specify the revokeremoteaccess option in your options file. See Revokeremoteaccess for more information
Client access authority is not sufficient to access the backup-archive client, command line client, and native GUI. You must possess at least client owner authority.
You can use the virtualnodename option to temporarily access your node's data from another machine. This option differs from the nodename option in that, if passwordaccess=generate is specified along with the virtualnodename option the password is not stored on the local machine. If you specify the nodename option the password is stored on the local machine. See Virtualnodename for more information about the virtualnodename option.