High Availability and Disaster Recovery (sometimes also known as business continuity) address different requirements, as shown in Table 3.
Table 3. High Availability and Disaster Recovery Compared
| High Availability | Disaster Recovery |
|---|---|
| Addresses service availability, providing redundancy so that if one infrastructure component (network, servers, processes) becomes unavailable, overall service remains available. | Addresses service continuity, so that in case of disaster, service is maintained through a standby site. |
| A single system contains its own data (in the file system and database) and executables. | Two independent environments, typically in separate and distinct facilities, each contain their own data (in the file system and database) and executables. |
| Data replication is unnecessary (although data should be backed up). | Data and configuration information are replicated between the production and standby sites. |
For information on setting up Disaster Recovery for EPM System components, see Disaster Recovery. For general information on setting up Disaster Recovery, see the Oracle Fusion Middleware Disaster Recovery Guide ( http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15250/toc.htm).