Oracle Application Server 10g, Installation Manual

Page: 189 / 258

Setting up the OracleAS Disaster Recovery Environment
Installing in High Availability Environments: OracleAS Disaster Recovery 10-5
non-authoritative requests to the external DNS servers. The external DNS servers
do not know about the existence of the internal DNS servers. See
Figure 10–2 .
Figure 10–2 Method 1: Using DNS Servers
Method 1 Details
a.
Make sure the external DNS names are defined in the external DNS zone.
Example:
prodmid1.us.oracle.com IN A 138.1.2.333
prodmid2.us.oracle.com IN A 138.1.2.444
prodinf.us.oracle.com IN A 138.1.2.111
standbymid1.us.oracle.com IN A 213.2.2.330
standbymid2.us.oracle.com IN A 213.2.2.331
standbyinf.us.oracle.com IN A 213.2.2.110
b.
At the production site, create a new zone at the production site using a
domain name different from your external domain name. To do this, populate
the zone data files with entries for each node in the OracleAS Disaster
Recovery environment.
For the infrastructure node, use the virtual name or alias.
For the middle-tier nodes, use the node name (the value in
/etc/nodename
).
The following example uses "asha" as the domain name for the new zone.
asmid1.asha IN A 138.1.2.333
asmid2.asha IN A 138.1.2.444
asinfra.asha IN A 138.1.2.111
Do the same for the standby site. Use the same domain name that you used for
the production site.
asmid1.asha IN A 213.2.2.330
asmid1.asha IN A 213.2.2.331
asinfra.asha IN A 213.2.2.110
c.
Configure the DNS resolver to point to the internal DNS servers instead of the
external DNS server.
In the
/etc/resolv.conf
file for each node on the production site, replace
the existing name server IP address with the IP address of the internal DNS
server for the production site.
Production Site Standby Site
Internal DNS Server
for the Production Site
asmid1 asmid2 asinfra
External DNS Server External DNS Server
External DNS Server
Internal DNS Server
for the Standby Site
asmid1 asmid2 asinfra