Setting Up and Managing Disaster Recovery Sites 4-43
4.1.2 Storage Replication
Follow these steps to set up storage replication for the Oracle Fusion Middleware Disaster Recovery topology:
1.
On the standby site, ensure that aliases host names are created that are the same as the physical host names used for the peer hosts at the production site.
2.
On the shared storage at the standby site, create the same volumes as were created on the shared storage at the production site.
3.
On the standby site, create the same mount points and symbolic links that you created at the production site note that symbolic links only need to be set up on
the standby site if you set up symbolic links at the production site. Note that symbolic links are required only in cases where the storage system does not
guarantee consistent replication across multiple volumes; see
Section 3.2.3, Storage Replication
for more details about symbolic links.
4.
It is not necessary to install the same Oracle Fusion Middleware instances at the standby site as were installed at the production site. When the production site
storage is replicated to the standby site storage, the Oracle software installed on the production site volumes will be replicated at the standby site volumes.
5.
Perform any other necessary configuration required by the shared storage vendor to enable storage replication between the production site shared storage and the
standby site shared storage.
6.
Create the baseline snapshot copy of the production site shared storage that sets up the replication between the production site and standby site shared storage.
Create the initial baseline copy and subsequent snapshot copies using asynchronous replication mode. After the baseline snapshot copy is performed,
validate that all the directories inside the standby site volumes have the same contents as the directories inside the production site volumes.
7.
Set up the frequency of subsequent copies of the production site shared storage, which will be replicated at the standby site. When asynchronous replication mode
is used, then at the requested frequency the changed data blocks at the production site shared storage based on comparison to the previous snapshot copy become
the new snapshot copy, and the snapshot copy is transferred to the standby site shared storage.
Application FMWHOMEGROUP
VOLFMW1 VOLFMW2
Consistency group for the Middleware homes
Web WEBHOMEGROUP
VOLWEB1 VOLWEB2
Consistency group for the Oracle HTTP Server Oracle
homes Web
WEBINSTANCEGROUP VOLWEBINST1
VOLWEBINST2 VOLSTATIC1
1
VOLSTATIC2
2
Consistency group for the Oracle HTTP Server Oracle
instances
1
This volume for static HTML data is optional. Oracle Fusion Middleware will operate normally without it.
2
This volume for static HTML data is optional. Oracle Fusion Middleware will operate normally without it.
Table 4–13 Cont. Consistency Groups for Oracle Enterprise Content Management
Tier Group Name
Members Comments
4-44 Oracle Fusion Middleware Disaster Recovery Guide
8.
Ensure that disaster protection for any database that is included in the Oracle Fusion Middleware Disaster Recovery production site is provided by Oracle Data
Guard. Do not use storage replication technology to provide disaster protection for Oracle databases.
9.
The standby site shared storage receives snapshots transferred on a periodic basis from the production site shared storage. After the snapshots are applied, the
standby site shared storage will include all the data up to and including the data contained in the last snapshot transferred from the production site before the
failover or switchover.
10.
It is strongly recommended to manually force a synchronization operation whenever a change is made to the middle tier at the production site for example,
when a new application is deployed at the production site. Follow the vendor-specific instructions for forcing a synchronization using storage replication
technology.
4.1.3 Database
Kategori