DOCUMENTATION: Possible reasons why the Destination Client tab is grayed out in the NetBackup Java Administration GUI

Article:TECH16924  |  Created: 2006-01-10  |  Updated: 2013-10-27  |  Article URL http://www.symantec.com/docs/TECH16924
Article Type
Technical Solution


Issue



Possible reasons why the Destination Client tab is grayed out in the NetBackup Java Administration GUI


Error



When attempting to do an Alternate Client restore via the NetBackup Java Administration console (jnbSA) or the Backup, Archive and Restore GUI (jbpSA), the Destination Client tab can be grayed out due to configuration errors.


Cause



There are several possible causes and solutions for this: 

1. The bp.conf file or Windows Registry contains formatting errors.
 
This could include tabs, comments, or missing entries.
 
2. The auth.conf file does not allow permissions for alternate client restores.
 
The JBP=<value> in the auth.conf file can affect the Destination client tab.
 
3. The hostname used in the Java Login window does not match the SERVER line in the bp.conf file.
 
The hostname used in the login window must match a valid SERVER entry.

Solution



 

Notes for file locations in UNIX and Windows:

  • UNIX systems use the /usr/openv/java/auth.conf file non-root user entries.
  • UNIX systems use the /usr/openv/netbackup/bp.conf for SERVER and CLIENT_NAME entries.
  • Windows systems use the <install_path>\VERITAS\Java\auth.conf file for non-root user entries.
  • Windows systems use the following registry keys for SERVER and CLIENT_NAME entries.

HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config\Server
HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config\Client_Name

 

The bp.conf file or Windows registry contains formatting errors

  • The existence of tabs in the SERVER entry in the bp.conf file:

The Destination client tab can be grayed out if there is a tab character in the SERVER entry in the master server's bp.conf file. Windows uses the registry to store server entries which do not use tab characters and should be unaffected by this.

Example of an incorrect bp.conf:

SERVER<tab>= <master>
SERVER<tab>= <media>
CLIENT_NAME = <client>

Tabs after the SERVER entry can cause the Java GUI to fail when comparing the login hostname to the SERVER entry. A delay may also occur when launching the Java GUI and selecting the Backup, Archive, and Restore window.

Correct the bp.conf to look as follows:

SERVER = <master>
SERVER = <media>
CLIENT_NAME = <client>


It may be necessary to restart the NetBackup daemons for NetBackup to recognize the corrected entries in the bp.conf file.

 

  • The existence of a comment entry after the SERVER entry in the bp.conf file

The Destination client tab can be grayed out if there is a comment after the SERVER entry in the master server's bp.conf file. Windows uses the registry to store server entries which do not use comments and should be unaffected by this.

Example of an incorrect bp.conf:

SERVER = <master> # Master server comments
SERVER = <media>
CLIENT_NAME = <client>

Notice the comment after the master's host name in the bp.conf file. Comments can exist in the bp.conf file but these should exist on their own line, not after valid bp.conf entries. The Java GUI may display the server name as "<master> # Master server comments" under the NetBackup Servers tab if comments exist in the SERVER entry.

Correct the bp.conf to look like:

SERVER = <master>
# Master server comments
SERVER = <media>
CLIENT_NAME = <client>

It may be necessary to restart the NetBackup daemons for NetBackup to recognize the corrected entries in the bp.conf file.

 

  • The CLIENT_NAME = <client> is missing from the bp.conf file.

The Java GUI expects to see the CLIENT_NAME set on the NetBackup master server. If this option is missing from the master server's bp.conf file or the Windows registry, the Destination Client tab can be greyed out in the Java GUI.

Example of an incorrect bp.conf:
SERVER = <master>
SERVER = <media>

Notice the CLIENT_NAME entry is missing from the file. The Client_Name registry entry will be missing if the Client name has not been set on the master server. This can be added in as a REG_SZ value to the Windows registry.

Correct the bp.conf to look like:

SERVER = <master>
SERVER = <media>
CLIENT_NAME = <client>

It may be necessary to restart the NetBackup daemons for NetBackup to recognize the corrected entries in the bp.conf file.


The auth.conf file does not allow permissions for alternate client restores.

  • Non-root users must have a JBP=<value> entry in the auth.conf file.

When creating the username entry in the auth.conf file, it is required to add the JBP=<value> to set the capabilities for the Backup, Archive, Restore interface. If this entry is missing, the Specify NetBackup Machine and Policy Type menu option and icon will be greyed out.

Example of an incorrect auth.conf:

<username> ADMIN=ALL

Correct the auth.conf to look like:

<username> ADMIN=ALL JBP=ALL

This will allow the user access to Specify NetBackup Machine and Policy Type which includes the Destination client tab. It will be necessary to log out and back into the Java GUI after making this change.

  • Non-root users configured with ADMIN=JBP must have JBP=ALL

When using the ADMIN=JBP setting for a user in the auth.conf, there are additional restrictions for the JBP=<value> setting. If the auth.conf on the master server does not use JBP=ALL or JBP=<value>+RAWPART, then the Destination Client tab will be greyed out.

Example of an incorrect auth.conf:

<username> ADMIN=JBP JBP=ENDUSER

Correct the auth.conf to be one of the following:

<username> ADMIN=JBP JBP=ALL
<username> ADMIN=JBP JBP=ENDUSER+RAWPART

It will be necessary to log out and back into the Java GUI after making this change.

 

The hostname used in the Java Login window does not match the SERVER line in the bp.conf file.

  • The hostname entered in the Java Login window is for a different network interface.

The Java login window expects that the hostname entered will be an exact match for a SERVER entry in the master server's bp.conf or Windows registry.

For example:

The first network interface on the master is called "myhost."
The second network interface is called "myhost-bkup."
The master server is defined only as "SERVER = myhost-bkup" in the bp.conf or Windows registry.

The operator logging into the Java console with the hostname "myhost" will experience the Destination client tab being grayed out. If the operator logs into "myhost-bkup" the Destination client tab will be available.

Verify that the hostname being entered in the Java GUI login window is also a valid server name in the bp.conf file or the Windows registry. If not, then add the hostname as a SERVER entry. A restart of the NetBackup daemons will be necessary to get NetBackup to recognize the corrected entries in the master's bp.conf file.

  • The hostname entered in the Java Login window is an alias for the master.

The same rules apply when logging in using an alias for the master server. The Java login window expects that the hostname entered will be an exact match for a SERVER entry in the master server's bp.conf file or Windows registry.

To correct this, add the alias as a SERVER entry to the bp.conf file or Windows registry.

A restart of the NetBackup daemons is necessary to get NetBackup to recognize the corrected entries in the master's bp.conf file.

 

  • The IP address was entered in the Java Login window.

The same rules apply when logging in via IP address. The Java login window expects that the hostname entered will be an exact match for a SERVER entry in the master server's bp.conf or Windows registry.

To allow login via the IP address of the master, add the IP address as a SERVER entry. It is not recommended to log into the Java GUI using the IP address of the master. The Java GUI expects to use a hostname when running the underlying commands in the GUI. This can cause problems with inventorying the robot and other sections of the Java GUI.

  • The hostname entered in the Java Login window is case-sensitive.

The hostname that is used on the Java GUI login screen is case-sensitive. When a hostname is used in the Login window that does not match the SERVER = <master> entry in the bp.conf file or Windows registry, the Destination client tab will be grayed out.

For example:

The master server is defined as "master01" in the bp.conf or Windows registry.
The user logs into the Java GUI using "Master01" as the hostname.

The solution for this problem is to use the correct case when logging into the Java GUI.

 



Legacy ID



241668


Article URL http://www.symantec.com/docs/TECH16924


Terms of use for this information are found in Legal Notices