Overview of Oracle Secure Backup Installation

After you have completed the tasks in "Planning Your Administrative Domain", you are ready to install the software and configure your administrative domain. Figure 1-3 illustrates the basic process, which can be used on any combination of Linux, UNIX and Windows hosts.

Figure 1-3 Installing Oracle Secure Backup

Description of "Figure 1-3 Installing Oracle Secure Backup"

You can perform the installation and configuration in the following steps:

Plan your administrative domain, including:
- Determine which hosts are assigned each role
- For Linux-based media servers, collect device information such as SCSI parameters for tape libraries and drives

Install the Oracle Secure Backup software on each Windows, UNIX or Linux host in your administrative domain, except for any hosts which will run NDMP daemons from other vendors, such as NDMP-enabled NAS filers.

Note:

During installation on each host, specify the roles you assigned in Step 1 when prompted.
Before installation on Windows media servers, disable existing device drivers for tape drives and libraries so that the Oracle Secure Backup device driver can manage these devices. This enables Oracle Secure Backup for Windows to determine SCSI device parameters automatically during installation.
For Linux or UNIX installation on media servers, you can enter SCSI device parameters for your tape drives and libraries during installation, or as a separate task performed immediately after installation.
During installation on a host designated as administrative server, an administrative domain is created on that host. At this point it contains no information about hosts other than the administrative server.

Overview of Installation of Oracle Secure Backup on Linux and UNIX

Oracle Secure Backup on Linux or UNIX is performed in three phases:

Loading (performed by a script called setup), in which files required for installing Oracle Secure Backup on one or more different Linux or UNIX platforms are staged on the administrative server, in a directory called the Oracle Secure Backup home.

Installing (performed by a script called installob), in which Oracle Secure Backup executables are deployed on individual Linux or UNIX hosts.

Note:

On media servers, installob also performs some device configuration tasks, including installation of a required device driver on Solaris, and, optionally, creation of device special files required for Oracle Secure Backup to access the media devices.

Optionally, SCSI device configuration on media servers, which involves creation of device special files on media servers to allow the Oracle Secure Backup device driver to access the media devices. You need the SCSI device information collected in "Collecting Device Parameters for UNIX and Linux Tape Devices" to perform this task.

Note:

This is properly speaking a configuration task, but as a convenience the installob script can prompt for the necessary information and perform the configuration process during initial Linux or UNIX installation or in a later session. Until this task is performed, Oracle Secure Backup cannot access media devices.

Remote or Push Installation of Oracle Secure Backup on Linux and UNIX

After installing on a Linux or UNIX administrative server, the installob script can be used to push software across the network directly from the administrative server to Linux or UNIX clients or media servers in what is called a remote installation or push installation. In a remote installation installob copies the installation files required for the destination platform across the network, then uses rsh to send commands to the destination host that perform the installation and configuration.

Note:

This distribution method requires that administrators be able to issue the rsh command as root without a password on the destination host. Configuring your Linux and UNIX clients to permit this form of access presents security issues.

Also, if support for rsh as root without a password is not part of your normal host configuration, you must configure each host to accept commands this way before the push installation, and then disable this capability when installation is complete.

Figure 1-4 illustrates local installation on the administrative server and media servers in an administrative domain, and push installation onto hosts that play the client role only.

Figure 1-4 Installing Oracle Secure Backup on Linux and UNIX

Description of "Figure 1-4 Installing Oracle Secure Backup on Linux and UNIX"

In this scenario the steps in the installation process are as follows:

Load and install the Oracle Secure Backup software only on the administrative server and media servers.

When running setup on the administrative server host, load the installation packages for all UNIX or Linux operating systems used in your administrative domain onto the server. Also, when running installob on the media servers, install and configure the Oracle Secure Backup device drivers and create device special files on each host.
Log in to the administrative server, and add the media servers to the administrative domain.

Perform this task directly on the administrative server, which is automatically defined during the software installation in the preceding step.
Make the administrative server aware of tape devices in your domain.

This step involves media servers only. Configure the SCSI and Fibre Channel libraries and tape drives directly attached to an Oracle Secure Backup host in your administrative domain, if you have not already done so, and configure the administrative domain with information about the tape devices attached to each media server. Also, discover the libraries and tape drives attached to a NAS filer so that the filer can communicate with Oracle Secure Backup.
Perform the push installation process from the administrative server to the Linux or UNIX clients. Run installob on the UNIX or Linux administrative server again, and follow the prompts to install Oracle Secure Backup on other hosts.
Log in to the administrative server and configure the administrative domain with information about the clients.