| Oracle® Secure Backup Installation Guide Release 10.1 Part Number B14235-05 |
|
|
PDF · Mobi · ePub |
| Oracle® Secure Backup Installation Guide Release 10.1 Part Number B14235-05 |
|
|
PDF · Mobi · ePub |
This chapter explains how to install Oracle Secure Backup on hosts running Linux or UNIX.
This chapter covers the following topics:
Loading Oracle Secure Backup Software on Solaris or Linux Using setup Script
Optional: Configuring Installation Parameters in the obparameters File
Installing Oracle Secure Backup on Linux or UNIX with installob
Perform the following actions before you begin:
Select hosts for the administrative server, media server and client roles, as described in "Planning Your Administrative Domain".
For Linux media servers, ensure that the SCSI Generic (SG) driver is installed. It is required for Oracle Secure Backup to interact with media devices.
If you are running setup or installob on a Linux host, then the compress and uncompress utilities must be installed on the system.
Determine the SCSI parameters for each tape drive and library attached to your Linux and UNIX media servers, as described in "Determining SCSI Device Parameters on Linux and UNIX". You can configure these devices as part of your initial installation process or later, but you need the information in any case.
Decide whether to perform an interactive or batch-mode installation.
In interactive mode, the installob program installs the software on one host at a time, prompting for the host name, roles, SCSI device information (for media servers), and any other required information for each installation. After each installation, you are asked whether you want to install Oracle Secure Backup on another host.
In batch mode, you must create or modify a network description file, which is a text file that describes your network configuration. The installob program uses the information in this file to perform a push installation, transferring the software across the network to the designated hosts and performing required installation and configuration steps.
Examine the sample network description file ./install/obndf for information on creating a network description file. The file contains extensive comments that document the required contents. If you plan to modify the file, then save a copy of the original.
Note:
The example in "Installing Oracle Secure Backup on Linux or UNIX with installob" describes installation in interactive mode.Ensure that each host has a network connection and runs TCP/IP.
If using push installations, then configure destination hosts to allow rsh access for root from the administrative server without requiring a password. For more details on configuring rsh access for root without a password on your media servers and clients, refer to the operating system documentation for your platform.
If not using push installations, then decide how to make the installation media for Oracle Secure Backup available on each Linux or UNIX host in your administrative domain. For example, ensure that each host has a CD-ROM drive, or can mount a directory over NFS across the network containing the extracted archive of Oracle Secure Backup installation files.
Note:
Consider the security implications of configuring your hosts to permit rsh access for root without passwords when deciding whether to use remote installation.
If support for rsh access for root without passwords across your administrative domain is not part of your normal system configuration, then remember to disable it on each host in your administrative domain when the installation process is complete.
You must log in to each host with root privileges to perform the installation.
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.
You must create the Oracle Secure Backup home 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.
See also:
"Oracle Secure Backup Home Directory" and Oracle Secure Backup Administrator's Guide for more details about the Oracle Secure Backup home.The recommended location for the Oracle Secure Backup home is /usr/local/oracle/backup. You can, however, create the directory in a different location.
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.After logging in as root, create the directory for your Oracle Secure Backup home. For example:
# mkdir -p /usr/local/oracle/backup
Loading the Oracle Secure Backup software is the process by 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. The setup script is used to perform this loading process.
Note:
Network administrators may find it convenient to load Oracle Secure Backup installation files for multiple platforms on the administrative server. You can hold these binaries in reserve for installation to various hosts in their administrative domain at a later time. It is not, however, required that you load the installation files for all platforms on the administrative server. You can also extract installation files and run setup and install separately on each host.This example illustrates the loading process on a Solaris 64-bit host called dlsun1976. However, these instructions apply to all Linux and UNIX operating systems.
To load Oracle Secure Backup into an Oracle Secure Backup home directory for later installation on one or more platforms:
Log into your Linux or UNIX operating system as root.
Change to the Oracle Secure Backup home directory created in "Creating the Oracle Secure Backup Home". For example:
# cd /usr/local/oracle/backup
Run the setup script from your installation media or extracted archive directory. Enter the following command:
#/media_dir/setup
where /media_dir is the CD-ROM mount point or the directory containing the files extracted from the downloaded archive.
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 setup program displays output similar to the following for Linux x86 and Solaris Operating System (SPARC 64-Bit):
Welcome to Oracle's setup program for Oracle Secure Backup. This
program loads Oracle Secure Backup software from the CD-ROM to a filesystem
directory of your choosing.
This CD-ROM contains Oracle Secure Backup version 10.1.0.1.0.
Please wait a moment while I learn about this host... done.
- - - - - - - - - - - - - - - - - - - - - - - - - - -
You may load any of the following Oracle Secure Backup packages:
1. linux32 (RH 2.1, RHEL 3, RHEL 4, SuSE 8, SuSE 9)
administrative server, media server, client
2. solaris64 (Solaris 2.8 and later, SPARC)
administrative server, media server, client
Enter a space-separated list of packages you'd like to load. To load all
packages, enter 'all' [2]:
Note:
The output for thesetup program varies for Linux Itanium, Linux x86-64, and HP-UX PA-RISC (64-Bit).Each package contains the binaries and other 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 runsetup 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.To load the Oracle Secure Backup installation package for a single host, enter the appropriate number for that platform. For this example, enter 2 to load only the package of Oracle Secure Backup for a Solaris 64 host. The following output is displayed:
- - - - - - - - - - - - - - - - - - - - - - - - - - - Loading Oracle Secure Backup installation tools ... done. Loading solaris64 administrative server, media server, client ... done. - - - - - - - - - - - - - - - - - - - - - - - - - - -
Loading of Oracle Secure Backup software from CD-ROM is complete. You may unmount and remove the CD-ROM.
Note:
At this point the setup 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.Starting the Oracle Secure Backup installob Script From setup
setup now displays the following question:
Would you like to continue Oracle Secure Backup installation with 'installob' now? (The Oracle Secure Backup Installation Guide contains complete information about installob.) Please answer 'yes' or 'no' [yes]:
At this point the setup script can start the installob script to install Oracle Secure Backup on the local host or, using a push installation, deploy it on other Linux or UNIX hosts on your network. 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 need to customize some aspect of your installation process using the obparameters file, as described in "Optional: Configuring Installation Parameters in the obparameters File".
In this case, the following message displays:
When you are ready to continue: 1. log in as (or 'su' to) root 2. cd to /usr/local/oracle/backup 3. run install/installob
The setup script then exits.
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 thesetup script is interrupted, it is possible that some temporary files, named OBnnnn or OBnnnn.Z, remain in /usr/tmp. You can delete these files.Oracle Secure Backup uses a parameter file called obparameters to customize the operation of the installob installation script.
The setup script (described in "Loading Oracle Secure Backup Software on Solaris or Linux Using setup Script") creates the obparameters file 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, the parameter file is located at /usr/local/oracle/backup/install/obparameters.
During the installation process the setup program prompts you either to accept the default settings in the obparameters file or customize 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.
Reasons to change the parameters in the obparameters file include:
You can customize installation directories and symbolic links created during installation on different platforms.
If using Oracle Secure Backup to back up Oracle databases to tape, 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. (You can also configure a pre-authorized oracle user later.)
Note:
Before electing to create an Oracle Secure Backuporacle user, be aware that this choice involves a trade-off between convenience and security. For more information on the security issues, see Oracle Secure Backup Reference.See Also:
Oracle Secure Backup Administrator's Guide for more information about the pre-authorizedoracle user and RMAN backups.obparameters is a plain text file that can be edited using any standard UNIX text editor, such as emacs or vi. Complete reference documentation for the obparameters file is contained in Appendix B, "Oracle Secure Backup obparameters Installation Parameters".
Note:
If you intend to use Oracle Secure Backup to perform one-time, RMAN-initiated, or unprivileged backups on Windows clients, then you must modify the Oracle Secure Backupadmin 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 operation. This requirement applies regardless of the platform that acts as the administrative server.
See Oracle Secure Backup Administrator's Guide for more details on the role of the preauthorized oracle Oracle Secure Backup user in RMAN backups.
To install the Oracle Secure Backup software on Linux or UNIX, run the installob script.
Note:
Before startinginstallob on a media server, have the SCSI parameters for tape devices available. You will have the option of entering those parameters to configure SCSI devices as part of the initial installation. See "Determining SCSI Device Parameters on Linux and UNIX" for details on collecting this information.installob Step 1: Starting the installob Script
The Oracle Secure Backup setup script described in "Loading Oracle Secure Backup Software on Solaris or Linux Using setup Script" ends by asking whether to start the installation process using the installob script for you after the software is loaded. If you entered yes to this question, the setup script runs the installob script for you.
Otherwise, start installob from the shell prompt. While logged in as root, change directory to the Oracle Secure Backup home and enter the following command:
install/installob
The installob program displays the following output:
- - - - - - - - - - - - - - - - - - - - - - - - - Welcome to installob, Oracle Secure Backup's UNIX installation program. It installs Oracle Secure Backup onto one or more UNIX, Linux, or other supported open-source systems on your network. (Install Oracle Secure Backup for Windows using the CD-ROM from which you loaded this software.) For most questions, a default answer appears enclosed in square brackets. Press return to select this answer. Please wait a few seconds while I learn about this machine... done.
installob Step 2: Confirm Settings in obparameters File
The next step depends upon the value of the customized obparameters parameter in the obparameters file described in "Optional: Configuring Installation Parameters in the obparameters File".
If you have already edited obparameters and set customized obparameters to yes, then installob assumes that you have made any desired changes in the obparameters file and uses those parameters during the installation. Continue to "installob Step 3: Choosing Interactive or Batch Mode Install".
If customized obparameters is set to no (the default), then installob displays the following output:
Have you already reviewed and customized install/obparameters for your Oracle Secure Backup installation [yes]?
Select one of the following options:
Enter yes or press the Enter key to indicate that you do not want to customize the obparameters file. Continue to "installob Step 3: Choosing Interactive or Batch Mode Install".
Enter no to choose to customize the obparameters file.
The installob program displays the following output:
Would you like to do this now [yes]?
You have the following options:
Enter no to indicate that you do not want to customize the file now. Installation proceeds, based upon the current settings specified in the obparameters file. Continue to "installob Step 3: Choosing Interactive or Batch Mode Install".
Enter yes to indicate that you want to customize the file now. The installob program displays the following output:
After you've reviewed and updated install/obparameters, re-run installob.
installob then exits.
Make the desired changes in the install/obparameters file under the Oracle Secure Backup home and restart installob as described in "installob Step 1: Starting the installob Script".
installob Step 3: Choosing Interactive or Batch Mode Install
The installob program displays the following output:
- - - - - - - - - - - - - - - - - - - - - - - - -
You can choose to install Oracle Secure Backup in one of two ways:
(a) interactively, by answering questions asked by this program, or
(b) in batch mode, by preparing a network description file
Use interactive mode to install Oracle Secure Backup on a small number of
hosts. Use batch mode to install Oracle Secure Backup on any number of
hosts.
Which installation method would you like to use (a or b) [a]?
- - - - - - - - - - - - - - - - - - - - - - - - -
Choose one of the following:
When you choose this mode, the installob program installs the software on one host at a time, prompting for the host name, role and any other information required for each installation. After each installation, you are asked whether you want to install Oracle Secure Backup on another host using a push installation.
This example describes an interactive mode installation.
Choose this mode to create or modify a network description file, which is a text file that describes your network configuration. The installob program uses the information in this file to perform a push install of the software across the network to the designated host.
Examine the sample network description file ./install/obndf for information on creating a network description file.
Note:
If you plan to modify the network description file, then save a copy of the original sample network description file.Enter a (or press the Enter key to accept the default choice a).
installob Step 4: Specifying Host Role
The installob program displays the following output:
- - - - - - - - - - - - - - - - - - - - - - - - - - -
Oracle Secure Backup is not yet installed on this machine.
Oracle Secure Backup's Web server has been loaded, but is not yet configured.
You can install this host one of three ways:
(a) admininistrative server
(the host will also be able to act as a media server or client)
(b) media server
(the host will also be able to act as a client)
(c) client
If you are not sure which way to install, please refer to the Oracle
Backup Installation Guide. (a,b or c) [a]?
You determined the roles for each host when planning your administrative domain. Choose one of the following:
Enter a to install the software as an administrative server. An administrative server stores configuration information and database files for clients.
Enter b to install the software as a media server.
A media server has one or more secondary storage devices, such as a library and tape drives, connected to it.
Enter c to install the software as a client. A client contains files that Oracle Secure Backup backs up or restores.
Note:
On Linux and UNIX, an administrative server installation also includes the required components and settings for the media server and client roles. A media server installation also includes the required components for the client role.
You can add or remove a role later with the chhost command in obtool. (To add the media server role to a client after initial installation, you must create device special files using makedev or installob.) See Oracle Secure Backup Reference for details.
See Also:
"Planning Your Administrative Domain" to learn more about the roles of administrative server, media server and client in Oracle Secure BackupThis example describes installation for an administrative server.
Enter a (or press the Enter key to accept the default choice a).
The installob program displays output similar to the following:
Beginning the installation. This will take just a minute and will produce several lines of informational output. Installing Oracle Secure Backup on dlsun1976 (solaris version 5.8)
Note:
The specific output varies according to your operating system.installob Step 5: Setting Administrative User Password
If you are installing on this host as an administrative server, installob prompts for an initial password for the Oracle Secure Backup administrative user. You are prompted to enter the password, and then to re-enter it for confirmation. For example:
You must now enter a password for the Oracle Secure Backup 'admin' user. Oracle suggests you choose a password of at least 8 characters in length, containing a mixture of alphabetic and numeric characters. Please enter the admin password: Re-type password for verification:
Note:
When you type in the password, your entry is not echoed to the display.installob Step 6: installob Completes Installing Software
installob now displays informational messages as it installs and configures the Oracle Secure Backup software on this host. This process may take a few minutes, and the output may vary depending upon the roles specified for this host. For example:
generating links for admin installation with Web server
checking Oracle Secure Backup's configuration file (/etc/obconfig)
setting Oracle Secure Backup directory to /usr/local/oracle/backup in /etc/obconfig
setting local database directory to /usr/etc/ob in /etc/obconfig
setting temp directory to /usr/tmp in /etc/obconfig
setting administrative directory to /usr/local/oracle/backup/admin in /etc/obconfig
protecting the Oracle Secure Backup directory
installing /etc/init.d/oraclebackup for observiced start/kill ops at
operating system run-level transition
installing start-script (link) /etc/rc2.d/S92OracleBackup
installing kill-script (link) /etc/rc1.d/K01OracleBackup
installing kill-script (link) /etc/rc0.d/K01OracleBackup
initializing the administrative domain
NOTE: installing Oracle Secure Backup driver in order to identify SCSI
busses...
NOTE: /usr/local/oracle/backup/.drv.solaris64/ob copied to /usr/kernel/drv/ob
NOTE: /usr/local/oracle/backup/.drv.solaris64/ob.conf copied to
/usr/kernel/drv/ob.conf
NOTE: /usr/local/oracle/backup/.drv.solaris64/ob64 copied to
/usr/kernel/drv/sparcv9/ob
At this point, the Oracle Secure Backup software required for the roles you specified is installed on this host.
installob Step 7: (Optional, Media Servers Only): Configuring Tape Drives and Libraries
For a media server or administrative server installation, installob now displays the following output:
NOTE: The Oracle Secure Backup device driver has been successfully installed. Would you like to configure (or reconfigure) any Oracle Secure Backup devices that are attached to dlsun1976 [no]?
Note:
Because installob includes both the administrative and media server roles when installing an administrative server, this prompt is displayed when installing on an administrative server even if there are no attached tape libraries or drives.
Although the following example concerns SCSI libraries and tape drives, the same procedures apply to Fibre Channel devices.
Configuring Oracle Secure Backup devices in installob creates the device special files required for Oracle Secure Backup to communicate with the devices.
In general, creating device special files can be performed using the makedev tool, described in "Creating Device Special Files on Solaris and Linux". However, you can also use installob to configure several media devices attached to a host at once.
Note:
You must collect the SCSI parameter information and assign Oracle Secure Backup logical unit numbers for the media devices on this host, as described in "Determining SCSI Device Parameters on Linux and UNIX".
You can configure devices during the initial installation, or you can run installob again later, as described in "Running installob Again for Device Configuration or Push Installs".
Choose one of the following:
Enter no to not configure your devices at this time.
Note:
If you are installing on an administrative server with no attached media devices, enterno.Enter yes to configure devices now.
Device configuration can be performed separately from the initial installation process, and can be performed using either the installob or makedev tools. This task is therefore described at more length in "Creating Device Special Files with installob". Refer to that discussion if you require detailed instructions to perform this task.
In brief, installob prompts you for whether there are tape libraries connected to this host, and if so, the SCSI parameters for each, and then asks the same questions about tape drives. As described in "Preparing to Install Oracle Secure Backup on Linux and UNIX", collecting this information for each of your media servers is part of preparing for the installation process.
The installob prompts and the required parameters are slightly different on Solaris and Linux, and are shown in the following examples:
Example 4-1, "Configuring Devices During Installation on Solaris"
Example 4-2, "Configuring Devices During Installation on Linux"
Note:
If you enter the wrong parameters, device special file creation fails. To resolve the resulting errors, runinstallob again, as described in "Running installob Again for Device Configuration or Push Installs", entering the correct values.Example 4-1 Configuring Devices During Installation on Solaris
For Solaris host dlsun1976, assume there is one attached tape library and one attached drive. Based on "Determining SCSI Device Parameters on Solaris", the SCSI parameters are as follows:
| Device | Oracle Secure Backup LUN | SCSI Bus Name- Instance | SCSI Target ID | SCSI LUN |
|---|---|---|---|---|
| Exabyte library | 0 | glm1 | 1 | 0 |
| Exabyte drive | 0 | glm1 | 0 | 0 |
Enter each parameter value in response to the prompts from installob. You can press Enter to accept a default value. Note, however, that the default SCSI parameters offered by the script may not be correct. For example:
Is dlsun1976 connected to any tape libraries that you'd like to use with
Oracle Secure Backup [no]? yes
How many Oracle Secure Backup tape libraries are attached to dlsun1976 [1]?
Please describe each tape library by answering the following questions.
Oracle Secure Backup logical unit number [0]:
SCSI bus name-instance [glm1]: glm1
SCSI target ID [3]: 1
SCSI lun 0-7 [0]: 0
Is the information you entered correct [yes]? yes
How many Oracle Secure Backup tape drives are attached to dlsun1976 [1]? 1
Please describe each tape drive by answering the following questions.
Oracle Secure Backup logical unit number [0]: 0
SCSI bus name-instance [glm1]: glm1
SCSI target ID [4]: 0
SCSI lun 0-7 [0]: 0
Is the information you entered correct [yes]? yes
- - - - - - - - - - - - - - - - - - - - - - - - - - -
Beginning device driver configuration and device special file creation.
NOTE: table for devlinks...
type=ddi_pseudo;name=ob;addr=0,0;minor=glm1 obt0
/dev/obt0 created
NOTE: table for devlinks...
type=ddi_pseudo;name=ob;addr=1,0;minor=glm1 obl0
/dev/obl0 created
- - - - - - - - - - - - - - - - - - - - - - - - - - -
NOTE: You must configure the new devices via the Web interface or via
the command line using the obtool 'mkdev' command.
- - - - - - - - - - - - - - - - - - - - - - - - - - -
The device special files are created. /dev/obt0 represents the tape drive, and /dev/obl0 represents the tape library. (Note that the l character is a lower-case L, not a numeral 1.)
When this step is complete, continue to "installob Step 8: Push Installations to Other Hosts".
Example 4-2 Configuring Devices During Installation on Linux
For Linux host storabck05, assume there is one attached tape library and one attached drive. Based on "Determining SCSI Device Parameters on Linux", the SCSI parameter values are as follows:
| Device | Oracle Secure Backup LUN | Host Bus Adapter | SCSI Bus Address | Target ID | SCSI LUN |
|---|---|---|---|---|---|
| Library | 0 | 0 | 0 | 2 | 0 |
| Tape drive | 0 | 0 | 0 | 4 | 0 |
Enter these parameters as prompted by installob. You can press Enter to accept a default value. Note, however, that the default SCSI parameters offered by the script may not be correct. For example:
Is storabck05 connected to any tape libraries that you'd like to use with
Oracle Secure Backup [no]? yes
How many Oracle Secure Backup tape libraries are attached to storabck05 [1]?
Please describe each tape library by answering the following questions.
Oracle Secure Backup logical unit number [0]: 0
Host SCSI adapter number 0-15 [0]: 4
SCSI bus address [0]: 0
SCSI target ID [3]: 1
SCSI lun 0-7 [0]: 0
Is the information you entered correct [yes]?
Is storabck05 connected to any tape drives that you'd like to use with
Oracle Secure Backup [no]? yes
How many Oracle Secure Backup tape drives are attached to storabck05 [1]?
Please describe each tape drive by answering the following questions.
Oracle Secure Backup logical unit number [0]: 0
Host SCSI adapter number 0-15 [0]: 4
SCSI bus address [0]: 0
SCSI target ID [4]: 2
SCSI lun 0-7 [0]: 0
Is the information you entered correct [yes]? yes
- - - - - - - - - - - - - - - - - - - - - - - - - - -
Beginning device driver configuration and device special file creation.
NOTE: No driver installation is required for Linux.
/dev/obt0 created
/dev/obl0 created
- - - - - - - - - - - - - - - - - - - - - - - - - - -
NOTE: You must configure the new devices via the Web interface or via
the command line using the obtool 'mkdev' command.
The device special files are created. /dev/obt0 represents the tape drive, and /dev/obl0 represents the tape library. (Note that the l character is a lower-case L, not a numeral 1.)
When this step is complete, continue to "installob Step 8: Push Installations to Other Hosts".
installob Step 8: Push Installations to Other Hosts
At this point installob displays the following output:
Would you like to install Oracle Secure Backup on any other machine [yes]?
You can now perform push installs from this server to other Linux or UNIX hosts, as described in "Overview of Installation of Oracle Secure Backup on Linux and UNIX". To perform push installations, your environment must already meet the following conditions:
You have staged the proper installation files on this host for the platform of the destination host, as described in "Loading Oracle Secure Backup Software on Solaris or Linux Using setup Script". For example, you cannot perform a push install from a Solaris 64-bit administrative server to Linux 32-bit if you did not include Linux 32-bit in the set of platforms specified during setup.
You have configured permissions on the destination host so that you can use rsh as root on that host without providing a password.
Select one of the following:
Enter no to not perform push installs at this time. You can run installob again to perform push installation at a future time. Installation continues with "installob Step 9: Final Installation Summary".
For the examples in this section, enter no.
Enter yes to perform a push install to another host.
installob prompts you for the name of the destination host. For example:
Enter the name of a host onto which you'd like to install Oracle Secure Backup:
Enter the name of the destination host. installob then prompts for the host role (media server or client) and, for media servers, SCSI device information for the remote host.
installob asks repeatedly about whether to perform more installations until you enter no.
installob Step 9: Final Installation Summary
installob now displays a summary of installation activities during this session and exits. For example:
Installation summary:
Installation Host OS Driver OS Move Reboot
Mode Name Name Installed? Required? Required?
admin dlsun1976 solaris no no no
Oracle Secure Backup is now ready for your use.
#
Note:
This installation summary does not include any information about device configuration tasks performed during theinstallob session.You can run installob again on a host on which Oracle Secure Backup is already installed. Reasons to do so include:
To configure additional tape libraries or drives on a media server without using makedev to configure them individually
To perform push installations to other hosts from an administrative server
The install script detects the existing installation and asks you whether to install Oracle Secure Backup again (overwriting the previous installation), and whether you want to configure media devices (overwriting any existing device special files).
If you run the installob script on a host on which it has already been run, the script detects the existing installation and asks you whether 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. For example, log in as root, change directory to the Oracle Secure Backup home, and run installob:
# cd /usr/local/oracle/backup # install/installob Welcome to installob, Oracle Secure Backup's UNIX installation program. . . . Oracle Secure Backup is already installed on this machine (dlsun1976). Would you like to re-install it here [no]? no Would you like to configure (or reconfigure) any Oracle Secure Backup devices that are attached to dlsun1976 [no]? . . .
You can then continue to device configuration, or to installing Oracle Secure Backup on other hosts.
|
 Copyright © 2006, Oracle. All rights reserved. Legal Notices |
|