This chapter describes the procedures for installing the Recovery Appliance software. It contains the following sections:
Note:
Recovery Appliance software is supported only when installed on Recovery Appliance hardware. See the Zero Data Loss Recovery Appliance Licensing Information User Manual for information about software licensing.
The following scripts install the Recovery Appliance software:
ra_preinstall.pl: Performs initial checks and prepares the Recovery Appliance for new installations and upgrades. This script was introduced in Zero Data Loss Recovery Appliance software update 12.1.1.1.7. See Zero Data Loss Recovery Appliance Upgrade and Patching (Doc ID 2028931.1) for more information.
install.sh: Uses the files generated by Oracle Exadata Deployment Assistant to configure the networks, Oracle Database, and other software components.
The OneCommand ZIP file that contains Oracle Exadata Deployment Assistant for use in Using the Deployment Assistant also contains this script. You can run this script from any system on the same network as Recovery Appliance. Some platforms use install.cmd.
ra_install.pl: Performs additional configuration steps for the Recovery Appliance infrastructure. You must run this script while logged in to a Recovery Appliance compute server, and not from another server on the same network.
Before you begin the software installation, ensure that these procedures are complete:
You used Oracle Exadata Deployment Assistant to generate the configuration files. See Using the Deployment Assistant.
You assembled the installation files into the WorkDir directory under the OneCommand installation directory. (The OneCommand installation directory is the directory to which you extracted the OneCommand ZIP file, such as linux-x64.) See "Generating the Configuration Files" for information about the OneCommand installation directory. For the list of installation files, see My Oracle Support Doc ID 1927416.1.
The checkip script ran successfully with no remaining errors. See "Connecting Recovery Appliance to Your Networks".
All racks of a multirack installation are cabled together. See Extending Recovery Appliance with Multiple Racks.
All components of all new racks are configured. See Configuring a Recovery Appliance Rack.
Oracle Management Server is operating on the same network as Recovery Appliance.
Reclaim the disk space on all compute servers. See "Reclaiming Disk Space on the Compute Servers".
The Oracle tape library is installed and operational. A tape library is an optional component of Recovery Appliance.
When you add a new Recovery Appliance rack to an older rack, the factory installed images are typically different. You can either update the older rack to the new image, or retain the older version and reimage the new rack to match it. In either case, ensure that all servers and all Sun Datacenter InfiniBand Switch 36 switches are at the same patch level.
Additional patching considerations include the Grid Infrastructure and database home releases and bundle patch updates. If the software installation applies new patches, then Oracle recommends changing the existing servers so the new servers inherit the releases as part of the extension procedure. This way, the number of servers that require patches is lower. Apply any patches to the existing servers in advance, so that they are at the desired level when the extension work is scheduled, thereby reducing the amount of work required by the extension.
Before you install the Recovery Appliance software, you must run the reclaimdisks script on each compute server. The script checks the volume configuration and reallocates all space correctly for the Recovery Appliance. Reclaiming the disk space converts the Linux system to four disks in a RAID-5 configuration at the disk controller level.
Perform the following steps to configure the disks on a compute server:
The syntax of the install utility enables you to run one step or multiple steps, and to undo one or more steps that ran with errors. You can then fix whatever problems caused the errors and run the step again.
Table 11-1 describes the options.
Table 11-1 Options of the Install Utility
| Option | Description |
|---|---|
|
|
Identifies the XML configuration file. Required. |
|
|
Describes the script options. |
|
|
List the steps needed to install and configure the software for the configuration described in the XML file. |
|
|
Runs steps n through N, or step n. |
|
|
Runs step n. |
|
-u { |
Undoes steps n through N, or step n. |
The following examples provide examples of the syntax and sample output. The XML configuration file is named Example_Inc-ra01.xml (linux-x64/ExadataConfigurations/Example_Inc-ra01.xml).
This command displays Help for the utility:
$ ./install.sh -cf ExadataConfigurations/Example_Inc-ra01.xml -h
install.sh -cf <config.xml> -l [options]
install.sh -cf <config.xml> -s <step #> | -r <num-num>
install.sh
ARGUMENTS:
-l List all the steps that exist
-cf config file name [Full path please]
-s <step #> Run the step # at a time
-r <num-num> Run the steps one after the other as long as no errors
are encountered
-u <num-num> | <step#> Undo a range of steps or a particular step
-h Usage
Version : 14.254.04:00
This command lists the steps:
$ ./install.sh -cf ExadataConfigurations/Example_Inc-ra01.xml -l
1. Validate Configuration File
2. Setup Required Files
3. Create Users
4. Setup Cell Connectivity
5. Verify Infiniband
6. Calibrate Cells
7. Create Cell Disks
8. Create Grid Disks
9. Configure Alerting
10. Install Cluster Software
11. Initialize Cluster Software
12. Install Database Software
13. Relink Database with RDS
14. Create ASM Diskgroups
15. Create Databases
16. Apply Security Fixes
17. Install Exachk
18. Setup ASR Alerting
19. Create Installation Summary
20. Resecure Machine
The next example runs step 7:
./install.sh -cf ExadataConfigurations/Example_Inc-ra01.xml -s 7
Executing Create Cell Disks
Check physical disks for errors before creating celldisks..............
Restarting cell services..................
Initializing cells..............
Cleaning cells....................
Restarting cell services...................
Creating cell disks.........................
Creating flashlog on cells..........
Creating flashcache on cells........
Successfully completed execution of step Create Cell Disks
]
This command reverses step 15:
$ ./install.sh -cf ExadataConfigurations/Example_Inc-ra01.xml -u 15
Undoing Create Databases
Deleting databases...
Deleting database zdlra
.
.
.
The following descriptions show how each step contributes to the complete software installation. The install script lists the substeps as it performs them.
Step 1 Validate Configuration File
Runs a series of checks to ensure that the configuration file contains settings that are appropriate for the specified cluster on the current network:
Validates the host names and IP addresses
Verifies the operating system
Validates the cluster networks and network connectivity
Validates the network time protocol (NTP) setup
Validates the physical disks in the storage servers
Validates the compute servers for database readiness
Step 2 Setup Required Files
Ensures that the required files are accessible, copies them to the second compute server, unzips them as needed, and creates symbolic links.
See "Software Installation Prerequisites" if this step fails.
Step 3 Create Users
Creates the required users and groups for the cluster, updates /etc/hosts, and sets up a secure shell (SSH).
Step 4 Setup Cell Connectivity
Generates several files that are used by other steps, including cellip.ora, cellinit.ora, and cellaffinity, if required.
Step 5 Verify InfiniBand
Performs a series of checks on the InfiniBand fabric to ensure that the compute servers, storage servers, and InfiniBand switches are cabled together correctly.
If errors occur, a diagnostic ZIP file is generated. The output from this step includes the location of this file.
Step 6 Calibrate Cells
Uses the I/O calibration feature of Oracle Database to assess the I/O capability of the storage subsystem.
Step 7 Create Cell Disks
Performs a series of steps on the storage server disks that include creating the cell disks, and then creating a flash log and a flash cache on each cell.
Step 8 Create Grid Disks
Creates the grid disks for the cluster.
In this release, you must follow this step with additional manual procedures.
Step 9 Configure Alerting
Configures email on the storage servers, so that they can send alerts when problems occur.
Step 10 Install Cluster Software
Uses an Oracle Database utility to obtain the grid disk identifiers, and then runs the clusterware installer. It patches the software as needed.
Step 11 Initialize Cluster Software
If a replication network is being configured, this step creates the single client access name (SCAN) and virtual IP (VIP) for it. Then it initializes the cluster.
Step 12 Install Database Software
Installs the Oracle Database software and creates the Oracle Database home directory on both compute servers. It also patches the software as required.
In this release, you must follow this step with additional manual procedures.
Step 13 Relink Database with RDS
Relinks Oracle Database with Reliable Datagram Sockets (RDS).
Step 14 Create ASM Disk Groups
Obtains the grid disk identifiers and creates the Automatic Storage Management (ASM) disk groups.
Step 15 Create Databases
Creates the Recovery Appliance catalog on both compute servers.
Step 16 Apply Security Fixes
Restarts the cluster software to set the security parameters, and enables turbo mode if required.
Step 17 Install Exachk
Installs the exachk utility on the Recovery Appliance. See My Oracle Support Doc ID 1070954.1 for information about the utility.
Step 18 Setup ASR Alerting
Installs and configures Auto Service Request (ASR). Optional.
This step does the following:
Installs the required software packages
Configures the trap destinations
Starts the monitoring daemon
Step 19 Create Installation Summary
Obtains the system details, calibrates the storage servers, and generates a summary XML report. The output from this step includes the location of this file.
Step 20 Resecure Machine
Replaces the default passwords with custom passwords.
The postinstallation utility is located on the first compute node in the /opt/oracle.RecoveryAppliance/install directory. It has the following syntax:
./ra_install.pl --help | [--install | --uninstall] --step=STEP_NUMBER [--stdout]
Table 11-2 describes the options.
Table 11-2 Options of the Postinstallation Utility
| Option | Description |
|---|---|
|
|
Describes the utility options. |
|
|
Runs the step and installs the software. Default. |
|
|
Undoes the step and uninstalls the software. |
|
|
Runs a step. Valid values are 1 to 7. You must complete all steps in order. |
|
|
Prints all messages to the standard output instead of the log file. |
This example displays the Help topic:
# ra_install.pl --help
ra_install.pl - Recovery Appliance Installer
You must be logged in as root to run this command.
All steps should be run successfully for install.
Usage: ./ra_install.pl --help | --step=STEP_NUMBER {--install|--uninstall} [--stdout]
Options:
--help: displays this help message
--step=number: Which step to run
--stdout: Print all messages to stdout rather then the log file
--install: Installs the step rather then installing it. [Default]
--uninstall: Uninstalls the step rather then installing it.
Step Numbers:
Step 1 - Validation and Configuration Prep
Step 2 - OS Setup
Step 3 - Oracle User Setup
Step 4 - DBFS Setup
Step 5 - Tape Backup configuration
Step 6 - ZDLRA DB Backup Setup
Step 7 - Enable ZDLRA Services
This example runs step 2:
# ./ra_install.pl --step=2
Created log file /opt/oracle.RecoveryAppliance/log/ra_install.step1.20140823.1959.log
Start: Configuring OS for ZDLRA - Successful: OK
Start: Running on node: ra06adm07 - Successful: OK
End: Running on node: ra06adm07 - Successful: OK
Start: Running on node: ra06adm08 - Successful: OK
End: Configured OS for ZDLRA - Successful: OK
This section describes the postinstallation steps. Each step generates a log file in /opt/oracle.RecoveryAppliance/log. The output from a step includes the path to its log file.
Step 1 Validation and Configuration Prep
Creates the ra_xml configuration file, validates the configuration, and sets up the installer wallet.
Step 2 OS Setup
Configures the operating system. Starts the portmap and nscd daemon, and creates various operating system users and groups.
Step 3 Oracle User Setup
Configures the oracle operating system user.
Step 4 DBFS Setup
Creates the database file system (DBFS) mounts.
Step 5 Tape Backup Configuration
Determines whether a tape backup system is present, and makes the applicable configuration changes based on the details that were specified on the Tape Library Connectivity Page in the Oracle Exadata Deployment Assistant.
Step 6 ZDLRA DB Backup Setup
Configures backup of the Recovery Appliance catalog database and creates credentials for performing the backups. The catalog is backed up to a Recovery Appliance disk on an automated schedule.
Step 7 Enables ZDLRA Services
Starts all services installed in the previous steps.
To enable Enterprise Manager to administer Recovery Appliance, you must deploy the management agents to each compute server, then discover the targets for the Recovery Appliance. The targets include the cluster, database, listeners, Automatic Storage Management (ASM), and the appliance itself.
Work with your Oracle support engineer to perform the tasks in this section.
Note:
See Doc ID 1929507.1 for information about the plug-ins and patches required for Zero Data Loss Recovery Appliance management, monitoring, and protected database management.
Perform the following steps to deploy a management agent to each Recovery Appliance compute server:
Perform the following steps to discover the Recovery Appliance cluster:
Before you discover the Recovery Appliance itself, perform the following steps to discover the Recovery Appliance cluster database, listener, and ASM targets:
After discovering the Recovery Appliance cluster and cluster database targets, the Recovery Appliance target itself can be discovered. As part of discovering the top-level Recovery Appliance target that will include all Enterprise Manager Recovery Appliance software and hardware management functionality, a separate Recovery Appliance hardware target will also be discovered.
Perform the following steps to manually discover the Recovery Appliance target: