OracleEPMDisasterRecoveryBestPractice.pptVIP

Insert Picture Here Oracle EPM Disaster Recovery Best Practice For Release Agenda DR Approach Asymmetric Deployment Database Recommendations Application Configuration and Failover Existing Documentations Disaster Recovery ApproachActive/Standby Solution Primary Site Standby Site DNS switch/Geo LBR Application Application LDAP Data Storage Application Data Storage Security Information Storage Metadata Storage LDAP Data Storage Application Data Storage Security Information Storage Metadata Storage Disk Replication NAS/SAN Mounted Data Guard BINARIES CONFIGURATION BINARIES CONFIGURATION NAS/SAN Mounted WAN Planning Web Tier Firewall RAC Global Router Foundation Essbase Firewall Firewall Planning Web Tier Firewall RAC Foundation Essbase Firewall Standby Site Production Site Firewall Data Guard Disk Replication Average Latency and Bandwidth WAN Asymmetric Deployment Financial Management Financial Management Hostname Requirement Production and standby sites are in completely separate networks and the fully qualified hostnames can be the same in both sites Or, production and standby sites have different DNS that resolves the hostnames to the right IP in their network The standby site can have standby DNS that is activated on a disaster event Or, production hostnames are resolved to local IP address in standby site via /etc/hosts file Configure DR Environment Install and Configure Primary Site Binaries and Data should be on a replicated partition Do not distribute services between servers that are not clustered If hostnames are to be different in standby site, setup hostname aliases in Standby Site Install and Configure Standby Site Setup Database Replication Backup restore is ok Setup Disk Replication Backup restore is ok Enable Standby Site Install and Configure Standby Site Install and configure in both production standby site HyperionHome for each server is in a separate directory; it should be a network share or