|Oracle® Exalogic Elastic Cloud Backup and Recovery Guide
Release EL X2-2 and X3-2
|PDF · Mobi · ePub|
Oracle Exalogic is an integrated hardware and software system designed to provide a complete platform for a wide range of application types and a wide variety of workloads. Exalogic is intended for large-scale, performance-sensitive, mission-critical application deployments.
This chapter contains the following sections:
The Exalogic system contains many redundant components to ensure that the failure of any single component does not affect the overall availability of the system. This built-in redundancy provides protection against individual hardware component failures; however, it cannot protect against the following:
Full Exalogic system failure due to site outage and disaster
User error such as accidental deletion or updates
To recover from these types of errors, you must restore the system to either the same or new hardware. For these types of outages, Oracle recommends that critical systems be protected using disaster recovery (DR) technologies. An example of this is a similar system located off site, which is automatically kept up to date with changes made on the primary system concurrently. These systems provide hot-standby capability in the event of failure of the primary system. While hot-standby systems are extremely useful for business continuity, they are expensive to maintain and require additional infrastructure. In some circumstances, such as simple user errors, it may be quicker to fix the issue or restore the system using a backup.
Taking regular backups of a system is a part of the standard operating procedures for all production systems, and is done irrespective of existence of a DR solution. It grants the flexibility to restore individual files or the system as whole. Backups on Exalogic can be stored off site in a secure location, within the Exalogic system, disk-to-disk, and disk-to-tape. This document describes the options available when using Exalogic for all these cases. The specific combination of backup options chosen for a particular deployment depends on the requirements of the site.
Exalogic comes with a Sun ZFS Storage appliance and this document describes how to leverage the built-in features of the storage for disk-based backups. When backing up to tape, you have the option of using Network Data Management Protocol (NDMP) or backup agents deployed to the compute node. NDMP allows the tape-backup software to interact directly with the storage appliance rather than going through the operating system and, therefore, is faster. In addition, it imposes no overhead on the compute nodes of Exalogic. However, NDMP cannot be used to back up the operating system, or any other files, that exist on the local storage. If the speed of backup is the focus, then the fastest solution would be to use NDMP; however, taking the backup from the compute node offers more flexibility.
The backup and recovery solution for the Oracle Exalogic machine builds upon well-established solutions for Oracle Database and Oracle Fusion Middleware.
This document covers backing up and restoring the configuration of the Exalogic infrastructure components, and backing up and restoring the management components (the Exalogic Control Stack) of the cloud infrastructure when the Exalogic machine is deployed in a virtual configuration.
The Exalogic Control Stack consists of the Oracle VM Manager, the Oracle Enterprise Manager Ops Center and their repositories deployed to an Oracle Database.
The repository containing the disk images—for Exalogic Control vServers and for the application vServers—is located on the local ZFS storage appliance of the Exalogic machine.
This document is intended for use with the following platforms:
Physical (Linux): Exalogic Elastic Cloud Software 2.0.3.x.x and earlier
Physical (Solaris): Exalogic Elastic Cloud Software 2.0.4.x.x and earlier
Virtual (Oracle VM): Exalogic Elastic Cloud Software 2.0.4.x.x and earlier
For all later releases, Oracle recommends using the ExaBR tool to back up and recover Exalogic data. For more information, see the Backup and Recovery Guide Using ExaBR.
This section provides general backup and recovery recommendations for Exalogic.
For additional protection, it is strongly recommended that the backups be stored on an external storage appliance or on tape, depending on your current backup practices.
It is strongly recommended that regular backups of your data be scheduled. The backup schedule should be based on the nature of your data.
Schedule daily backups to the local ZFS storage appliance and weekly backups to the external ZFS Storage appliance.
It is recommended that a gold copy be created for the operating system of the compute nodes in your environment.
It is recommended that the components of the Exalogic Control stack and their repositories be backed up after lifecycle operations, such as adding and removing accounts, users, and vServers.
For more information, see the Exalogic Backup and Recovery Best Practices White Paper at