1
THE PREMIER GROUPDISASTER RECOVERY PLANUSING ORACLE VIRTUALMACHINES OVM 3.1.1 ANDJDEDWARDS TEMPLATESVERSION 9.1
2
INTRODUCTION
A proposed disaster recovery model designed to mitigate any disruption caused by a massive failure inhardware or software from an act of nature or human error.
The model takes advantage of Oracle OVM 3.1.1 Virtual Machines and JDEdwards EnterpriseOne Version9.1, Oracle Linux 5 for small and mid-size companies.
HARDWARE
Two main identical Servers were used to implement the model: Dell PowerEdge T320, 2 Raid-1 (1Terabyte HD) certified servers for Oracle VM.
No external storage (SAN Server) is used in this solution.
3
ORACLE VM ENVIRONMENT
Oracle VM is the server virtualization offering from Oracle Corporation. Oracle VM Server for x86incorporates the free and open-source Xen hypervisor technology, supports Windows, Linux, and OracleSolaris guests and includes an integrated Web based management console. Oracle VM features fullytested and certified Oracle Applications stack in an enterprise virtualization environment. Oracle VM canbe freely downloaded through Oracle Software Delivery Cloud
DISASTER RECOVERY MODEL
4
The model includes a cloned image of every JDEdwards Server including the Deployment Server.
VMENT1 – Enterprise Server (Oracle Linux 5)
VMDB1 – Database Server (Oracle Linux 5)
VMWEB1 – WebServer (Oracle Linux 5)
VMDEP1 – Deployment Server (Windows Server 2008 R2)
SAVING THE WORKING ENVIRONMENT
A. Cloning the Virtual machines
Cloning the Virtual Machines on a regular base (monthly or bi-weekly basis).
5
B. Offline Virtual Machines Backups (Optional)
Virtual machines can be backed up to external devices in one single step.
- Stop the Virtual machines- Copy the active server’s virtual disks and virtual machines directory to an external device
6
C. Oracle Database BackupsThe Oracle Backups are copied daily to the down level Server Machine from the Database Server(VMDB1 – Virtual machine). The purpose is having backups in the cross active-inactive Server.
Oracle Backups are running on a daily basis on 15 Day Retention Model
(Level 0 and Level 1)
7
ONLINE DATABASE BACKUP
1. \VMDB1\u01\backups
ONLINE 2 BACKUP OF DATABASE FILES 100% RETENTION ON SERVER 1 AND SERVER 2
2. \x.x.x.991\BK3. \x.x.x.992\BK
OFFLINE DATABASE BACKUP
4. Manual Export of /u01/backups to an offline device or external Disk (Monthly)
Script details
\VMDB1\bin\oracle_db_bk.sh
Schedule Backup
CRONTAB
Server: VMDB1
$ crontab –e
Daily 11:30pm
Crontab log:
8
\VMDB1\tmp\oracle_db_bk.log
Execution result
9
RECOVERING DATABASE IN CASE OF CATASTROPHIC EVENT
1. Start Virtual Machines that are operational. It should have a full operational Database.
2. Copy the latest backup files from \x.x.x.991\BK or \x.x.x.992\BK to \VMDB1\u01\backups
3. Catalog the Backups3.1 Logon to RMAN Rman target / Rman> catalog start with ‘/u01/backups’ Or use EM Manager, option Manage Current Backups / Catalog adittional files
10
Restore the Full Database or the Production Tablespaces to current time.
Also using recovering can be performed using RMAN Rman> Restore Database; Or recover in a point of time:
Rman> list backup of archivelog all;Review the latest archivelog sequenceRman> Recover database until sequence XXX;
Rman>Restore tablespace <name>; Rman > Recover tablespace <name> until sequence XXX;
11
ENTERPRISE SYSTEM TABLE SPACES
12
ENTERPRISE PRODUCTION CENTRAL OBJECTS
ENTERPRISEONE PRODUCTION BUSINESS DATA & CONTROL TABLES
13
Sergio Vargas
Sr. Technical ConsultantPremier Group
5201 Blue Lagoon Drive5th Floor - Suite 560
Miami, FL 33126
[email protected] +1-305-567-3188
linkedin.com/in/sergiovargascnc/