Installing client software with the sftp method
This client installation method is based on the usage of the SunSSH and the OpenSSH products, which must be at specific version and patch levels. For more information about these patches, please refer to the NetBackup 9.1 Release Notes.
Before you perform this procedure, read the following guidelines:
SSH daemon (sshd) | To use this method, the UNIX client must have sshd enabled and configured to allow root or non-root user logins. |
Client file location | If you want to install client software to a location other than the default, you must first create and link the desired directory. Create the directory where you want the software to reside, and then create Additional information about installation folder restrictions is available. |
Backup policies | Make sure that the clients are assigned to a backup policy. |
Security configuration | The install_client_files scripts may prompt you for security information based on your environment. The information that is required is based on the master server security mode and the target host security configuration. For details on how to respond to these prompts, refer to the NetBackup Security and Encryption Guide. |
To install client software from a UNIX master server to UNIX clients with the sftp method
- To move the client software from the server to the /tmp directory on the client, run the install_client_files script on the NetBackup server.
Use one of the following commands:
To move software to one client at a time:
/usr/openv/netbackup/bin/install_client_files sftp client user
The client is the host name of the client.
The user is the login ID that SSH requires on the client.
To move software to all clients at once:
/usr/openv/netbackup/bin/install_client_files sftp ALL user
The ALL option specifies that you want to install all clients that are configured in any backup policy on the server.
The user is the login ID required by the client.
- After the script runs, the root user on each client computer must run the following script:
sh /tmp/bp.<pid>/client_config
The pid is the process ID. The client_config script installs the binaries.