This appendix describes the installation parameters for Oracle Secure Backup on Linux or UNIX. You can set these parameters in the obparameters file, which is a plain text file located in the install subdirectory of the Solaris or Linux Oracle Secure Backup home.
Note:
Theobparameters file is not used in Windows installations.The following installation parameters are described in this appendix:
If you customize any of the parameters in the obparameters file, then set the customized obparameters parameter to yes.
The installation tools can update each host's control files to automatically start Oracle Secure Backup each time you boot the system.
This parameter controls whether or not the Oracle Secure Backup installation process creates an Oracle Secure Backup user named oracle which has been pre-authorized to perform database backup and restore operations.
Table B-3 create pre-authorized oracle user: Values
| Value | Meaning |
|---|---|
|
|
An Oracle Secure Backup user is created during installation. The parameters |
|
|
No Oracle user is created. |
After the Oracle Secure Backup installation is successfully completed and the administrative domain has been initialized, you can create a default Oracle Secure Backup user named oracle if requested (see create pre-authorized oracle user). By setting this parameter, you specify the Linux or UNIX operating system user to which the Oracle Secure Backup user named oracle will be mapped. Note that you can also perform this task through the Web tool.
After the installation is successfully completed and the administrative domain has been initialized, a default group will be created on Linux or UNIX if requested (see create pre-authorized oracle user). The user specified by the default UNIX user parameter is a member of this group.
This option configures the key size in bits, and thus the level of security, associated with the host identity certificates issued by the administrative service daemon.
The default is 1024.
Note:
Certificate key sizes smaller than 1024 are not considered secure. Certificate key sizes of 3072 or more are considered very secure.Table B-6 identity certificate key size: Values
| Value | Meaning |
|---|---|
|
|
Specifies a 512-bit long certificate key size. |
|
|
Specifies a 768-bit long certificate key size. |
|
|
Specifies a 1024-bit key length. This is the minimum required value for adequate security. |
|
|
Specifies a 2048-bit key length. This value offers adequate security. |
|
|
Specifies a 3072-bit key length. This value offers a very high level of security. |
|
|
Specifies a 4096-bit key length. This value offers a very high level of security. |
To keep the installation and administration of Oracle Secure Backup as straightforward as possible, Oracle provides a mechanism for you to identify the name of the Oracle Secure Backup home directory for each platform in your network. This directory must be private to each platform and not shared through NFS or a similar remote file system.
When the installation programs install Oracle Secure Backup software, they choose these home directories for the installation or verify that these are the directories you have used. These defaults may be changed based on the availability of disk space on your machine.
os-name is a placeholder for linux or solaris64.
Table B-7 os-name ob dir: Parameters and Values
| Parameter | Meaning |
|---|---|
|
|
Specifies Oracle Secure Backup home location for Linux hosts. The default is |
|
|
Specifies Oracle Secure Backup home location for Solaris 64-bit hosts. The default is |
Each platform has a discrete directory in which Oracle Secure Backup retains host-specific information. This directory must be private to each platform and not shared through NFS or a similar remote file system.
os-name is a placeholder for linux or solaris64 platforms.
Table B-8 os-name db dir: Parameters and Values
| Parameter | Meaning |
|---|---|
|
|
Specifies the directory where host-specific information is retained for Linux hosts. The default directory is |
|
|
Specifies the directory where host-specific information is retained for Solaris 64-bit hosts. The default directory is |
Oracle Secure Backup typically uses the /usr/tmp directory on each host for storage of transient files. Oracle Secure Backup requires that the temporary directory be able to contain lockable files and that it be accessible during the beginning of the reboot process. The directory must be on the local disk. You can specify a different directory for each platform by modifying any of these <os-name> temp dir parameters.
os-name is a placeholder for linux or solaris64.
Table B-9 os-name temp dir: Parameters and Values
| Parameter | Meaning |
|---|---|
|
|
Specifies the directory where transient files are stored for Linux hosts. The default directory is |
|
|
Specifies the directory where transient files are stored for Solaris 64-bit hosts. The default directory is |
During installation, symbolic links are created, typically in /usr/bin and /etc, so that Oracle Secure Backup users do not need to change their search paths. You can modify this behavior as follows:
Comment out or delete these parameters if you do not want the installation programs to create any links.
Change the value of these parameters if you want the installation programs to create links in another directory for a specific platform.
These parameters are particular to each supported platform. On some systems, it may be more appropriate to place links in /bin instead of /usr/bin or in /usr/etc instead of /etc.
This parameter must be followed by three values, in the order shown:
The name of the directory in which to create the bin link.
The name of the directory in which to create the etc link.
The name of the directory in which to create the lib link.
os-name is a placeholder for linux or solaris64.
Note:
Oracle recommends using the defaults provided for this parameter.Table B-10 os-name links: Parameters and Values
| Parameter | Meaning |
|---|---|
|
|
Specifies the directories where symbolic links are created for Linux hosts. The default directory list is |
|
|
Specifies the directories where symbolic links are created for Solaris 64-bit hosts. The default directory list is |
Note:
If theobparameters file specifies a lib directory for the operating system type of the current installation, then installob creates a libobk.so symbolic link in that directory. That symbolic link points to the actual libobk.so file in a platform-specific lib directory in the Oracle Secure Backup home (such as .lib.linux32).The installation notifies you when you are about to install Oracle Secure Backup into a directory other than the default Oracle Secure Backup home.
Specifies directory and file protection information that is in effect when the Oracle Secure Backup installation is complete.
Caution:
The file protection information is provided for reference only. Oracle strongly recommends using the defaults provided because changing them can prevent the product from functioning.Each line in the default protection section of the obparameters file indicates the file owner, group number and permissions for the file or files specified by name, or by wildcard pattern. The default values are as follows:
default protection:
root.0 755 ./.wrapper
root.0 644 ./device/*
root.0 755 ./install/*
root.0 644 ./help/*
root.0 755 ./man/*
root.0 644 ./man/man1/*
root.0 644 ./man/man8/*
root.0 644 ./samples/*
root.0 755 ./samples/autoobtar
root.0 755 ./samples/bdf2ds
root.0 755 ./samples/*.sh
root.0 700 ./admin
root.0 700 ./admin/*
root.0 700 ./admin/config/*
root.0 755 ./.bin.*/*
root.0 4755 ./.bin.*/obtar
root.0 4755 ./.bin.*/obt
root.0 4755 ./.bin.*/obtool
root.0 755 ./.etc.*/*
root.0 4755 ./.etc.*/obixd
root.0 4755 ./.etc.*/observiced
root.0 4755 ./.etc.*/obscheduled
root.0 4755 ./.etc.*/obrobotd
root.0 755 ./.etc.*/
root.0 4755 ./.etc.*/doswitch
root.0 644 ./.drv.*/*
root.0 755 ./.lib.*/*
root.0 755 ./*
root.0 755 /usr/etc/ob
root.0 644 /usr/etc/ob/.hostid
root.0 755 /usr/etc/ob/xcr
root.0 644 /etc/obconfig