Skip Headers
Oracle® Secure Backup Installation Guide
Release 10.1

Part Number B14235-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

Optional: Configuring Installation Parameters in the obparameters File

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:

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 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 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.