Skip Headers

Oracle® Secure Backup Installation and Configuration Guide Release 10.2 Part Number E05408-02 |
Home | Book List | Contents | Index | Contact Us

Previous | Next
| View PDF

# 2 Installing Oracle Secure Backup on Linux or UNIX

This chapter explains how to install Oracle Secure Backup on hosts running Linux or UNIX.

This chapter contains these sections:

- Oracle Secure Backup Linux and UNIX Installation Steps

- Prerequisites for Installing Oracle Secure Backup on Linux and UNIX

- Extracting Oracle Secure Backup from OTN Download on Linux or UNIX

- Preparing to Install Oracle Secure Backup on Linux and UNIX

- Creating the Oracle Secure Backup Home

- Loading Oracle Secure Backup Software on Linux or UNIX Using setup Script

- Configuring Installation Parameters in the obparameters File

- Installing Oracle Secure Backup on Linux or UNIX with installob

- Installing or Uninstalling Oracle Secure Backup on AIX

- Running installob Again to Create Device Special Files

- Creating Device Special Files with makedev

- Upgrade Installation on Linux or UNIX

- Uninstalling Oracle Secure Backup on Linux or UNIX

## Oracle Secure Backup Linux and UNIX Installation Steps

There are three steps to installing Oracle Secure Backup on a Linux or UNIX host:

- Loading

  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. This step is performed by a script called setup.

- Installing

  Oracle Secure Backup executables are deployed correctly for use on the host. This step is performed by a script called installob.

  Note:

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

- Device special file creation on each media server

  This step is required for the Oracle Secure Backup device driver to access tape devices. You need the SCSI device parameters to perform this task.

Note:

If you are installing Oracle Secure Backup in an Oracle Real Application Clusters (RAC) environment, then you must install Oracle Secure Backup on each node in the cluster.

## Prerequisites for Installing Oracle Secure Backup on Linux and UNIX

The prerequisites for installing Oracle Secure Backup on Linux and UNIX operating systems are:

- Each host must have a network connection with a static IP address and run TCP/IP (Transmission Control Protocol/Internet Protocol).

- The uncompress utility must be installed on your system.

  Note:

  If the uncompress utility is not installed on your system, then you can create an uncompress symbolic link pointing to the gunzip utility with the following command:

      ln -s /bin/gunzip uncompress

- You must have the Small Computer System Interface (SCSI) parameters for each tape drive and tape library attached to your Linux or UNIX media server. You can determine them using the procedures described in Appendix C, "Determining Linux and UNIX SCSI Parameters". You need this information when creating a device special file for each tape device.

- You must be able to log in to each host with `root` privileges to perform the installation.

### Prerequisites for Installation on Linux

For each Linux media server, ensure that the SCSI Generic (SG) driver is installed. It is required for Oracle Secure Backup to interact with a tape device.

Kernel modules are usually loaded directly by the facility that requires them, if the correct settings are present in the /etc/modprobe.conf file. However, it is sometimes necessary to explicitly force the loading of a module at start time.

For example, on RedHat Enterprise Linux, the module for the SCSI Generic driver is named `sg`. Red Hat Enterprise Linux checks at start time for the existence of the /etc/rc.modules file, which contains various commands to load modules.

Note:

The rc.modules file should be used, and not rc.local, because rc.modules runs earlier in the start process.

On RedHat Enterprise Linux, you can use the following commands to add the sg module to the list of modules configured to load as `root` at start time:

    # echo modprobe sg >> /etc/rc.modules
    # chmod +x /etc/rc.modules

An Oracle Secure Backup user must be mapped to a Linux or UNIX user that has read/write permissions to the /dev/sg devices. One way to accomplish this is to set the permissions to 666 for the /dev/sg devices.

### Required SCSI Tape Device Parameters on Linux and UNIX

Oracle Secure Backup supports both Small Computer System Interface (SCSI) and Fibre Channel devices for Linux and UNIX. To configure a media server to communicate with its attached tape devices, you must have the SCSI parameters for each tape device.

On Linux the required SCSI parameters are:

- The host bus adapter number for the SCSI adapter

- The SCSI bus address

- The SCSI target ID

- The SCSI logical unit number (SCSI LUN)

Note:

In the Linux operating system, SCSI bus addresses are referred to as channels.

On Solaris the required SCSI parameters are:

- The SCSI bus name-instance

- The SCSI target ID

- The SCSI LUN

You must also assign each tape drive and tape library an Oracle Secure Backup logical unit number, as described in "Assigning Oracle Secure Backup Logical Unit Numbers to Devices".

Note:

Do not confuse the SCSI logical unit number with the Oracle Secure Backup logical unit number. The Oracle Secure Backup logical unit number is a number you assign that is used in generating a device special file name.

See Also:

Appendix C, "Determining Linux and UNIX SCSI Parameters" for details on how to collect this information

#### Assigning Oracle Secure Backup Logical Unit Numbers to Devices

Each tape drive and tape library must be assigned an Oracle Secure Backup logical unit number during the configuration process. This number is used to generate unique device names during device configuration. Oracle Secure Backup logical unit numbers are assigned as needed automatically on Windows. For each UNIX or Linux media server, however, you must select Oracle Secure Backup logical unit numbers for each device as part of planning your administrative domain.

There is no required order for assigning Oracle Secure Backup logical unit numbers. They are typically assigned sequentially, starting at 0, for each tape device of a given type, whether tape library or tape drive. That is, tape libraries are typically numbered 0, 1, 2 and so on, and tape drives are also numbered 0, 1, 2 and so on. The maximum value for an Oracle Secure Backup logical unit number is 31.

On Linux or UNIX, the resulting device special file names for tape libraries are /dev/obl1, /dev/obl2, /dev/obl3 and so on, and the names for tape drives are /dev/obt1, /dev/obt2, /dev/obt3 and so on. On Windows, the resulting tape library names are //./obl1, //./obl2, //./obl3 and so on, and the names for tape drives are //./obt1, //./obt2, //./obt3 and so on, where these names are assigned automatically during the installation of Oracle Secure Backup on Windows.

See Also:

"Linux Attach Points"

Note:

The Oracle Secure Backup logical unit number should not be confused with the SCSI logical unit number (SCSI LUN). The latter is part of the hardware address of the tape device, while the Oracle Secure Backup logical unit number is part of the device special filename.

## Extracting Oracle Secure Backup from OTN Download on Linux or UNIX

To download and extract the Oracle Secure Backup installation software:

1. Log in to your host as a user with `root` privileges.

2. Create a directory called osbdownload on a file system with enough free space to hold the downloaded installation file:

       mkdir /tmp/osbdownload

3. Open a Web browser and go to the Oracle Secure Backup Web site on Oracle Technology Network (OTN):

   `http://www.oracle.com/technology/products/secure-backup`

4. Click Free Download.

   The Oracle Technology Network Developer License Terms page appears.

5. Read Export Controls on the Programs and select the Yes, I accept... option.

   Read the Oracle Technology Network Development License Agreement and click I Accept.

   The Oracle Secure Backup Downloads page appears.

6. Select the Accept License Agreement option, and click the link for the version of Oracle Secure Backup release 10.2 specific to your operating system.

   Note:

   If you have more than one operating system in your environment, then you must perform multiple downloads of the Oracle Secure Backup release 10.2 software.

7. The Oracle Secure Backup release 10.2 installation software is compressed. Save it to a temporary directory, and expand it to the osbdownload directory you created in step 2.

You now have all of the files required to install Oracle Secure Backup release 10.2.

## Preparing to Install Oracle Secure Backup on Linux and UNIX

Perform the following actions before installing Oracle Secure Backup:

- Select hosts for the administrative server, media server and client roles, as described in "Installation and Configuration Overview".

- Collect the Small Computer System Interface (SCSI) parameters for each tape drive and tape library attached to your Linux and UNIX media servers. You need this information when creating device special file for each tape device.

- Disable any system software that scans and opens arbitrary SCSI targets before adding Oracle Secure Backup tape devices to an administrative domain. If Oracle Secure Backup has to contend with other system software (such as monitoring software) for access to tape libraries and drives, then unexpected behavior can result.

- If you are installing Oracle Secure Backup in an Oracle Real Application Clusters (RAC) environment, then you must install Oracle Secure Backup on each node in the cluster.

## Creating the Oracle Secure Backup Home

You must create an Oracle Secure Backup home on each host before beginning the process of loading and installing the software. The Oracle Secure Backup setup program uses this directory to store installation files specific to your host.

Note:

Oracle recommends that you use /usr/local/oracle/backup as your Oracle Secure Backup home. If you use a different directory, then the setup program prompts you to confirm your selected directory.

See also:

"Oracle Secure Backup Home Directory" and Oracle Secure Backup Administrator's Guide for more details about the Oracle Secure Backup home.

To create the Oracle Secure Backup home:

1. Log into the host as `root`.

2. Run the following command:

       # mkdir -p /usr/local/oracle/backup

## Loading Oracle Secure Backup Software on Linux or UNIX Using setup Script

The setup script is used to perform the loading process, in which packages of files required to install Oracle Secure Backup on one or more platforms are extracted from the installation media and staged in the Oracle Secure Backup home for later use by the installob installation script.

To load Oracle Secure Backup into an Oracle Secure Backup home directory for later installation on one or more Linux or UNIX platforms:

1. Log into your Linux or UNIX operating system as `root`.

2. Change to the Oracle Secure Backup home directory created in "Creating the Oracle Secure Backup Home". For example:

       # cd /usr/local/oracle/backup

3. Run the setup script from your installation media or extracted archive directory. Enter the following command, where `/media_dir` is the CD-ROM mount point or the directory containing the files extracted from the downloaded archive:

       # /media_dir/setup

   For example, if you downloaded an archive from Oracle Technology Network (OTN) and extracted the setup software to the /tmp/osbdownload/OB directory, then you would run the setup program as follows:

       # /tmp/osbdownload/OB/setup

   The installation files are compressed, and Oracle Secure Backup expands them in a temporary directory during installation. If you want to specify a particular directory for this expansion, you can use the `-t` option to the `setup` command. The following example specifies that setup should use `directory_name` for the expansion process:

       # /media_dir/setup -t directory_name

   The setup script displays a welcome message and tells you what version of Oracle Secure Backup it contains. It then lists all packages available and asks you to enter a space-separated list of package numbers you want. If you want to load all packages, then enter `all`.

4. Each package contains the files required to install Oracle Secure Backup on that platform. Enter the number or numbers that identify the installation packages that you want to load, so that they will be staged for later installation on Linux or UNIX hosts in your administrative domain.

   Note:

   You can run setup again in the future if necessary, to load packages for more platforms into the Oracle Secure Backup home, without affecting existing installations of Oracle Secure Backup.

   The setup script displays progress messages as it loads the package or packages you selected. When it is finished, it tells you to unmount and remove the installation CD-ROM.

   Note:

   At this point the loading process is complete. The files required to install Oracle Secure Backup on the platforms you specified are stored in the Oracle Secure Backup home on this host.

5. At this point the setup script can start the installob script to install Oracle Secure Backup on the local host. You can also defer this task until later.

   Choose one of the following:

   - Enter `no` if you want to run installob later, or if you must customize some aspect of your installation process using the obparameters file, as described in "Configuring Installation Parameters in the obparameters File".

     If you enter no, then the setup script tells you how to continue installation later, and setup exits.

     See Also:

     "Installing Oracle Secure Backup on Linux or UNIX with installob" for instructions on starting installob

   - Enter `yes` to start the installob script. The steps for running installob are described in "Installing Oracle Secure Backup on Linux or UNIX with installob".

   Note:

   If the setup script is interrupted, then it is possible that some temporary files, named OBnnnn or OBnnnn.Z, remain in /usr/tmp. You can safely delete these files.

## Configuring Installation Parameters in the obparameters File

The setup script creates a file called obparameters in the install subdirectory of the Oracle Secure Backup home. For example, if the Oracle Secure Backup home is in the default location /usr/local/oracle/backup, then the obparameters file is located at /usr/local/oracle/backup/install/.

During the installation process the setup script gives you the choice of accepting the default settings in the obparameters file or customizing those settings. In most cases, it is not necessary to change the defaults in the obparameters file. However, you should review the parameters you can control in this file as part of planning your installation, and determine whether any of them should be changed.

The obparameters file is plain text that can be edited using any standard text editor.

Reasons to change the parameters in the obparameters file include:

- You can specify a different key size for enhanced security or performance

  See Also:

  "Setting the Key Size in obparameters"

- You can customize installation directories and symbolic links created during installation on different platforms.

- If you are using Oracle Secure Backup to back up Oracle Database files to tape, then you can create an Oracle Secure Backup user named `oracle` for use in RMAN backups. You can associate this user with Linux or UNIX operating system credentials by setting parameters in obparameters.

  Note:

  - You can also configure a preauthorized `oracle` user later. Before electing to create an Oracle Secure Backup `oracle` user, be aware that this choice involves a trade-off between convenience and security.

  - If you intend to use Oracle Secure Backup to perform one-time, RMAN-initiated, or unprivileged backup operations on Windows clients, then you must modify the Oracle Secure Backup `admin` and `oracle` users to assign them Windows credentials (a domain, username and password) that are valid at the client with required privileges after you complete the Oracle Secure Backup installation. Otherwise, Oracle Secure Backup is unable to perform these types of backup operations. This requirement applies regardless of the platform that acts as the administrative server.

  See Also:

  - Oracle Secure Backup Administrator's Guide for more information about the preauthorized `oracle` user and RMAN backups.

  - Appendix B, "Oracle Secure Backup obparameters Installation Parameters"

## Installing Oracle Secure Backup on Linux or UNIX with installob

To install the Oracle Secure Backup software on Linux or UNIX:

1. Start the installob script.

   The Oracle Secure Backup setup script ends by asking if you want to start the installation process using the installob script. If you enter `yes` to this question, then the setup script runs the installob script for you.

   Otherwise, start the installob script from the command prompt. While logged in as `root`, go to the Oracle Secure Backup home and enter the following command:

       install/installob

   Note:

   Before starting the installob script on a media server, have the SCSI parameters for each tape device available. You will have the option of entering those parameters to create a device special file for each Small Computer System Interface (SCSI) device as part of the initial installation.

   The installob script displays a welcome message and tells you that most of its questions have default answers, which you can select by simply pressing Enter.

2. Confirm the settings in the obparameters file.

   This step depends upon the value of the `customized` `obparameters` parameter in the obparameters file described in "Configuring Installation Parameters in the obparameters File". The two possibilities are:

   - You have already edited the obparameters file and set `customized` `obparameters` to `yes`.

     In this case, the installob script assumes that you have made the changes you want in the obparameters file and uses those parameters during the installation. Continue to step 3.

   - The `customized` `obparameters` parameter is set to `no`, which is the default.

     In this case, the installob script asks if you have reviewed and customized the obparameters file. Choose one of the following:

     - Enter `yes` or press the Enter key to indicate that you do not want to customize the obparameters file. Continue to step 3.

     - Enter `yes` to indicate that you do want to customize the obparameters file. The installob script tells you to rerun the script after reviewing obparameters. The installob script then exits.

       See Also:

       "customized obparameters" for details about the `customize` `obparameters` parameter.

3. Specify the host role.

   You determined the roles for each host when planning your administrative domain. Choose one of the following:

   - Enter a to install the software for an administrative server.

     If you choose this option, then installob also installs the software required for the media server and client roles.

   - Enter b to install the software for a media server.

     If you choose this option, then installob also installs the software required for the client role.

   - Enter c to install the software for a client.

   You can add or remove a role later with the `chhost` command in obtool.

   Note:

   - If you choose an administrative server or media server installation, then installob installs the software necessary for the media server role. But the host does not have the media server role until the `admin` user grants that role with the `chhost` command after Oracle Secure Backup is installed.

   - To add the media server role to an administrative server or client after initial installation, you must create device special files using makedev or installob. See Oracle Secure Backup Reference for details.

   See Also:

   "Installation and Configuration Overview" to learn more about the roles of administrative server, media server and client in Oracle Secure Backup

   This procedure describes installation for an administrative server.

4. Create a password for the Oracle Secure Backup administrative server.

   The installob script asks for a password for the `admin` Oracle Secure Backup user, and then asks you to re-enter it for confirmation. Oracle recommends that you choose a password of at least 8 characters in length, containing a mixture of alphabetic and numeric characters. When you type in the password, your entry is not echoed to the display.

   Note:

   The practice of supplying a password in clear text on a command line or in a command script is not recommended by Oracle. It is a security vulnerability. The recommended procedure is to have the user be prompted for the password.

5. Create a password for the Oracle Secure Backup keystore.

   The installob script asks for a password for the Oracle Secure Backup keystore, and then asks you to re-enter it for confirmation. Oracle recommends that you choose a password of at least 8 characters in length, containing a mixture of alphabetic and numeric characters. When you type in the password, your entry is not echoed to the display.

6. Enter an e-mail address for notifications.

   The installob script asks for an e-mail address to which Oracle Secure Backup will send notifications.

   The installob script now displays informational messages as it installs and configures the Oracle Secure Backup software on this host. This process might take several minutes to complete.

7. If you are installing Oracle Secure Backup on an administrative server or media server, then the installob script asks if you want to configure a tape drive or tape library.

   Note:

   In installob, the term configuring refers to creating the device special files required for Oracle Secure Backup to communicate with the tape devices. Do not confuse this step with configuring the administrative domain with information about tape devices and media servers, as described in Chapter 5, "Administrative Domain Configuration and Management".

   The installob script includes software required for both the administrative server and media server roles in an administrative server installation. Therefore, this prompt is displayed when installing on an administrative server even if there are no attached tape drives or tape libraries.

   Although this procedure discusses SCSI tape libraries and tape drives, it also applies to a Fibre Channel tape device.

   Choose one of the following:

   - Enter `no` if you do not want to create device special files for your tape devices at this time, or if you are installing on an administrative server with no tape devices attached.

     Note:

     On Linux systems Oracle recommends that you enter `no` when asked if you want to configure tape libraries or tape drives during installation. The preferred mode of operation on Linux systems is to use the /dev/sg devices for attach points, as described in "Linux Attach Points".

     If you choose to create device special files later, or if you add a tape device to a media server in the future, then see "Running installob Again to Create Device Special Files" or "Creating Device Special Files with makedev" for two alternative methods of completing this task.

   - Enter `yes` to configure tape devices now.

     To create device special files, the installob script asks if there are tape libraries connected to this host, and if so, what the SCSI parameters are for each tape library. After you have entered the tape library SCSI parameters, the installob script asks you to confirm your entries.

     When you have completed entering information about tape libraries attached to this host, the installob script asks the same questions about standalone tape drives.

     The SCSI parameters requested by the installob script differ somewhat between Linux and UNIX hosts. On Linux hosts, the installob script asks for:

     - Oracle Secure Backup LUN

     - Host bus adapter

     - SCSI bus address

     - Target ID

     - SCSI logical unit number (SCSI LUN)

     Note:

     In the Linux operating system, SCSI bus addresses are referred to as channels.

     On UNIX hosts, the installob script asks for:

     - Oracle Secure Backup LUN

     - SCSI bus name-instance

     - SCSI Target ID

     - SCSI LUN

     Enter each parameter value in response to the prompts from the installob script. You can press Enter to accept a default value, but the default SCSI parameters offered by the script might not be correct.

     When you have entered the SCSI parameters for all tape libraries and tape drives attached to this host, the installob script begins device driver configuration and device special file creation.

     Record the name of the device special file created for each tape device. The filename is needed when you configure the attachment for the tape device, as part of configuring the Oracle Secure Backup domain. The filename should be /dev/obtn for tape drives, and /dev/obln for tape libraries, where n is the Oracle Secure Backup LUN you entered for the tape device.

     If you enter the wrong parameters, then device special file creation fails. To resolve the resulting errors, run installob again, as described in "Running installob Again to Create Device Special Files", entering the correct values, or use the makedev script described in "Creating Device Special Files with makedev".

     When the installob script has created device special files for all tape devices attached to this host, it reminds you that you must configure the new tape devices through the Oracle Secure Backup Web interface or the command line using the obtool `mkdev` command.

8. The installob script displays a summary of installation activities during this session and exits. This installation summary does not include any information about device special file creation performed during the installob session.

## Installing or Uninstalling Oracle Secure Backup on AIX

The current release of Oracle Secure Backup supports only the client role on an AIX platform. The Oracle Secure Backup Administrative Server and Media Server roles are not supported. The previous version of Oracle Secure Backup must be uninstalled prior to installing the current release of Oracle Secure Backup.

The installation and uninstallation procedures for AIX and Linux/UNIX are identical.

See Also:

- "Installing Oracle Secure Backup on Linux or UNIX with installob"

- "Uninstalling Oracle Secure Backup on Linux or UNIX"

During Oracle Secure Backup installation, the Oracle Secure Backup `admin` user is mapped by default to UNIX user `root` and UNIX group `root`. In this configuration, Oracle Secure Backup requires that the user `root` be a member of the group `root` to back up the file system successfully. AIX does not define a group `root` by default. If the group `root` does not exist on your AIX system, then you must create it and make user `root` a member of it.

Note:

This mapping of the Oracle Secure Backup `admin` user can be changed post-installation.

## Running installob Again to Create Device Special Files

You can run the installob script again on a host on which Oracle Secure Backup is already installed. The chief reason to do so is to create device special files for several additional tape libraries or drives on a media server, instead of invoking makedev repeatedly to create one device special file at a time.

If you run the installob script on a host on which it has already been run, then the script detects the existing installation and asks if you want to perform each installation stage again. You can skip tasks that were correctly completed before by entering `no` when asked whether you want to perform them again.

You can then continue to enter the device special file configuration information, as described in "Installing Oracle Secure Backup on Linux or UNIX with installob".

## Creating Device Special Files with makedev

The makedev script in Oracle Secure Backup is used to create a device special file for a single tape device. Internally, the installob script calls makedev once for each tape device specified during installation. You can also run makedev directly from the command line if you must create device special files for a single tape device.

The makedev script can also replace an old device special file, rather than adding a new one. If you reuse an Oracle Secure Backup logical unit number for a tape library or tape drive, then the device special files for the old tape device are overwritten.

If you must create device special files for several tape devices, then it might be more convenient to use the installob script as described in "Running installob Again to Create Device Special Files".

See Also:

Oracle Secure Backup Reference for makedev syntax

Note:

On a Linux or other UNIX host, the parameters prompted for are different.

To use the makedev script to create device special files for a tape device:

1. Log on as `root`.

2. Go to the install directory in your Oracle Secure Backup home. For example:

       # cd /usr/local/oracle/backup/install

3. Enter the `makedev` command at the shell prompt:

       # makedev

4. The makedev script asks for information about the tape device.

   The Small Computer System Interface (SCSI) parameters requested by the script differ somewhat between Linux and UNIX hosts. On Linux hosts, the script asks for:

   - Oracle Secure Backup logical unit number

     Do not confuse the Oracle Secure Backup logical unit number with the SCSI logical unit number (SCSI LUN).

   - Device type

     Enter `d` for a tape drive or `l` (lowercase L) for a tape library.

   - Host bus adapter

   - SCSI bus address

   - Target ID

   - SCSI logical unit number

   Note:

   In the Linux operating system, SCSI bus addresses are referred to as channels.

   On UNIX hosts, the makedev script asks for:

   - Oracle Secure Backup logical unit number

     Do not confuse the Oracle Secure Backup logical unit number with the SCSI logical unit number.

   - Device type

     Enter `d` for a tape drive or `l` (lowercase L) for a tape library.

   - SCSI bus name-instance

   - SCSI target ID

   - SCSI logical unit number

5. The makedev script creates the device special file, displaying messages indicating its progress. When it is finished, the makedev script displays the name of the new device special file and exits.

### Linux Attach Points

Oracle recommends that for Linux systems the /dev/sg devices be used as attach points with Oracle Secure Backup. The use of the Oracle Secure Backup /dev/ob devices has certain limitations that some users might find unacceptable in their environments. For example the logical unit number cannot be greater than 7, and the Small Computer System Interface (SCSI) bus number cannot be greater than 1. The existing method of using /dev/ob* devices continues to work for a tape device that does not fall into the limitation category.

To identify the /dev/sg that corresponds to the tape device you are interested in, you can use the `sg_map` command. The following example shows a system that has five tape drives and four tape libraries available:

    sg_map -i -x
    /dev/sg0   0 0 0 0  0  /dev/sda  DELL      PERC Stripe       V1.0
    /dev/sg1   0 0 1 0  0  /dev/sdb  DELL      PERC Stripe       V1.0
    /dev/sg2   0 0 2 0  0  /dev/sdc  DELL      PERC Volume       V1.0
    /dev/sg3   1 0 1 0  8  ADIC      FastStor 2        G12r
    /dev/sg4   1 0 2 0  1  /dev/nst0  HP        Ultrium 2-SCSI    F53A
    /dev/sg5   2 0 0 0  1  /dev/nst1  IBM       ULTRIUM-TD2       5AT0
    /dev/sg6   2 0 0 1  8  ADIC      Scalar 24         310A
    /dev/sg7   2 0 1 0  1  /dev/nst2  IBM       ULTRIUM-TD2       5AT0
    /dev/sg8   2 0 1 1  8  ADIC      Scalar 24         310A
    /dev/sg9   2 0 2 0  1  /dev/nst3  IBM       ULTRIUM-TD3       54K1
    /dev/sg10  2 0 3 0  1  /dev/nst4  IBM       ULTRIUM-TD3       54K1
    /dev/sg11  2 0 3 1  8  ADIC      Scalar 24         310A

After you have identified the /dev/sg that corresponds to the tape device you are interested in, you can use the obtool `mkdev` command to create attach points for it. For example, to create the attach points for an ADIC Fastor 2 tape library that has one tape drive, you would enter the following:

    ob> mkdev -t library -o -a node1:/dev/sg3 lib1
    ob> mkdev -t tape -o -a node1:/dev/sg4 -l lib1 -d 1 tape1

## Upgrade Installation on Linux or UNIX

To upgrade a Linux or UNIX installation of Oracle Secure Backup, follow the setup and installation process described in "Installing Oracle Secure Backup on Linux or UNIX with installob". During the upgrade process, the installer displays the following prompt:

    Oracle Secure Backup is already installed on this machine (myhostname-sun2).
    Would you like to re-install it preserving current configuration data[no]?

Enter `yes` to perform the upgrade installation, retaining your previous configuration.

## Uninstalling Oracle Secure Backup on Linux or UNIX

This section explains how to uninstall Oracle Secure Backup from a Linux or UNIX host. In this procedure Oracle Secure Backup is uninstalled from the administrative server. The procedure is the same when using the administrative server to uninstall Oracle Secure Backup from other hosts.

1. Log on as `root` to the administrative server.

2. Shut down processes related to Oracle Secure Backup, such as the http processes for the Oracle Secure Backup Web tool. Use the following command to identify processes related to Oracle Secure Backup:

       # /bin/ps -ef |grep ob

   Use the following command to kill each process in the list associated with Oracle Secure Backup, where `pid` is the process ID:

       kill -9 pid

3. Change directory to the parent directory of the Oracle Secure Backup home directory. For example:

       # cd /usr/local/oracle

   Note:

   If you uninstall Oracle Secure Backup from the administrative server, then the uninstallob script removes the Oracle Secure Backup home directory at the end of the uninstall process.

4. Run the uninstallob script:

       # backup/install/uninstallob

   The uninstallob script displays a welcome message and then asks for the name of the host from which you want to remove Oracle Secure Backup.

5. Enter the name of a host from which you want to uninstall Oracle Secure Backup.

6. The uninstallob script asks for the name of the obparameters file used for installation.

   If you created an obparameters file in a location other than the default, then enter the correct path information. Otherwise, press the Enter key to accept the default value `install/obparameters`.

7. The uninstallob script asks if you want to remove the Oracle Secure Backup home directory. Select one of the following:

   - `no`

     Select this option if you do not want to remove the Oracle Secure Backup home directory.

   - `yes`

     Select this option if you want to remove the Oracle Secure Backup home directory. All files in the home directory will be deleted. The only exception is the admin directory, which you can elect to retain by answering `yes` at the next prompt.

   This procedure assumes you are saving the Oracle Secure Backup home directory.

8. The uninstallob script asks if you want to save the Oracle Secure Backup admin directory, even if you have chosen not to save the entire Oracle Secure Backup home directory. Select one of the following:

   - `no`

     Select this option to remove the admin directory.

   - `yes`

     Select this option to save the admin directory. If you keep the admin directory, then you can reinstall the Oracle Secure Backup software later without destroying your administrative domain.

   This procedure assumes you are saving the Oracle Secure Backup admin directory.

9. The uninstallob script displays the choices you have made and asks if you want to continue with the uninstallation on this host. Select one of the following:

   - `yes`

     If you select this option, then the uninstallob script displays progress messages as it uninstalls Oracle Secure Backup. When it is finished, it displays the following message:

         Oracle Secure Backup has been successfully removed from host_name.

   - `no`

     If you select this option, then the uninstallob script does not uninstall Oracle Secure Backup from this host.

10. If you entered `no` in the previous step, then the uninstallob script asks if you want to uninstall Oracle Secure Backup from another host. Select one of the following:

    - `yes`

      If you select this option, then the uninstallob script repeats steps 5 through 9 for a different host

    - `no`

      If you select this option, then the uninstallob script exits.

Note:

- If you uninstall Oracle Secure Backup from the local computer, then the uninstallob script removes the directory /usr/local/oracle/backup when it completes.

- On UNIX it might be necessary to remove the driver for Oracle Secure Backup manually from each media server after uninstalling the rest of the product. See "Uninstalling the Oracle Secure Backup Device Driver Manually" for details.