B Oracle Secure Backup obparameters Installation Parameters

B.1 customized obparameters

If you customize any of the parameters in the obparameters file, then set the customized obparameters parameter to yes.

B.2 start daemons at boot

The installation tools can update each host's control files to automatically start Oracle Secure Backup each time you boot the system.

B.3 create pre-authorized oracle user

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.

B.4 default UNIX user

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.

B.5 default UNIX group

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.

B.6 identity certificate key size

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.

B.7 <os-name> ob dir

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.

B.8 <os-name> db dir

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.

B.9 <os-name> temp dir

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.

B.10 <os-name> links

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:

1. The name of the directory in which to create the bin link.

2. The name of the directory in which to create the etc link.

3. The name of the directory in which to create the lib link.

os-name is a placeholder for linux or solaris64.

B.11 ask about ob dir

The installation notifies you when you are about to install Oracle Secure Backup into a directory other than the default Oracle Secure Backup home.

B.12 default protection

Specifies directory and file protection information that is in effect when the Oracle Secure Backup installation is complete.

Values

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

B.13 run obopenssl

The installation prompts you to create the certificates for the Apache Web server.