Troubleshooting installation problems

Use the following steps to troubleshoot installation problems.

Table: Steps for troubleshooting installation problems.

Step	Action	Description
Step 1	Determine if you can install the software on the primary server and the media servers by using the release media.	Some reasons for failure are as follows: Not logged on as an administrator on a Windows system (you must have permission to install services on the system) Permission denied (ensure that you have permission to use the device and to write the directories and files being installed) Bad media (contact Technical Support) Defective drive (replace the drive or refer to vendor's hardware documentation) Improperly configured drive (refer to the system and the vendor documentation)
Step 2	Determine if you can install NetBackup client software on the clients.	Note: Before you install or use NetBackup on a Linux client, verify that the bpcd -standalone and vnetd -standalone services are started on that computer. These services ensure proper communication between the NetBackup primary and the Linux client. Note: NetBackup UNIX or Linux servers can push client software to UNIX/Linux clients, and Windows servers can push to Windows clients. You can also download the client software from the NetBackup appliance, and then run the install on the client. Note: See the NetBackup Appliance Administrator's Guide. Do the following: For an install to a trusting UNIX client, verify the following: The correct client name is in your policy configuration. The correct server name is in the client `/.rhosts` file. If the installation hangs, check for problems with the shell or the environment variables for the root user on the client. The files that you check depend on the platform, operating system, and shell you use. For example, your .login on a Sun system runs an stty (such as stty ^erase) before it defines your terminal type. If this action causes the install process to hang, you can modify the .login file to define the terminal before you run the stty. Or, move the client .login to another file until the install is complete. For an installation to a secure UNIX client, check your ftp configuration. For example, you must use a user name and password that the client considers valid.
Step 3	Resolve network problems.	Determine if the problem is related to general network communications. See Resolving network communication problems with UNIX clients. See Resolving network communication problems with Windows clients.

Step

Action

Description

Step 1

Determine if you can install the software on the primary server and the media servers by using the release media.

Some reasons for failure are as follows:

Not logged on as an administrator on a Windows system (you must have permission to install services on the system)
Permission denied (ensure that you have permission to use the device and to write the directories and files being installed)
Bad media (contact Technical Support)
Defective drive (replace the drive or refer to vendor's hardware documentation)
Improperly configured drive (refer to the system and the vendor documentation)

Step 2

Determine if you can install NetBackup client software on the clients.

Note:

Before you install or use NetBackup on a Linux client, verify that the bpcd -standalone and vnetd -standalone services are started on that computer. These services ensure proper communication between the NetBackup primary and the Linux client.

Note:

NetBackup UNIX or Linux servers can push client software to UNIX/Linux clients, and Windows servers can push to Windows clients. You can also download the client software from the NetBackup appliance, and then run the install on the client.

Note:

See the NetBackup Appliance Administrator's Guide.

Do the following:

For an install to a trusting UNIX client, verify the following:
- The correct client name is in your policy configuration.
- The correct server name is in the client /.rhosts file.
If the installation hangs, check for problems with the shell or the environment variables for the root user on the client. The files that you check depend on the platform, operating system, and shell you use. For example, your .login on a Sun system runs an stty (such as stty ^erase) before it defines your terminal type. If this action causes the install process to hang, you can modify the .login file to define the terminal before you run the stty. Or, move the client .login to another file until the install is complete.
For an installation to a secure UNIX client, check your ftp configuration. For example, you must use a user name and password that the client considers valid.

Step 3

Resolve network problems.

Determine if the problem is related to general network communications.

See Resolving network communication problems with UNIX clients.

See Resolving network communication problems with Windows clients.

Troubleshooting installation problems

Feedback

Feedback