Veeam backup Oracle DB in a VM is easy and reliable way to protect data
Download as PPTX, PDF3 likes7,557 views
The document discusses methods for protecting Oracle databases using Veeam Backup & Replication, emphasizing the importance of archivelog mode for effective backup and recovery. It outlines the differences between crash-consistent and consistent backups, the implications of snapshot technology, and recovery scenarios including point-in-time recovery. Additionally, it highlights the limitations of instant recovery and the necessity of a classic backup approach for optimal recovery time objectives.
Veeam backup Oracle DB in a VM is easy and reliable way to protect data
- 1. Aleks Yemets Veeam SE Oracle DB in a VM: easy and reliable way to protect your data with Veeam B&R test 1
- 2. • A bit of theory: Oracle’s self-protection • Crash-consistent consistent? • Universal solution – our backup+their logs • Backup process • Recovery scenarios • BUT, there are a few "buts"- ASM, pRDM, mnode RAC (?) • Instant recovery – no way… • Classic DB recovery – yes, indeed…
- 3. User Process DDL/DML, Result Sets OracleServer Process DatabaseBufferCache (Blocksbeingusedinmemory) Database writer Datafiles Blocks Changed Blocks (Dirty Buffers) Oracle Server Process LogBuffer LogWriter OnlineRedo LogFiles Archiver ArchivedRedo LogFiles ControlFiles Checkpoint Redostream–TransactionInformation Checkpoint SCN Checkpoint SCN
- 4. • At each commit • Every three seconds • When the redo log buffer is one-third full • Oracle uses write-ahead protocol • Any changes are written to Log Buffer • The Log Writer writes to the online redo files under the following circumstances: • redo log is cyclically overwritten
- 5. • Oracle uses write-ahead protocol • Any changes are written to Log Buffer • The Log Writer writes to the online redo files under the following circumstances: • redo log is cyclically overwritten • DB in archivelog mode archives redo log • archive logs allow to recover DB to any needed point in time
- 6. • In archivelog mode you can backup whole DB in any of the following ways: • Closed and consistent • Closed and inconsistent • Open and inconsistent The ability to back up a database while it is open and in use is a key benefit of running a database in archivelog mode.
- 7. & • Snapshots are OK! Oracle will officially support the Snapshot Backup and Recovery operations assuming that the third party snapshot technology can meet the prerequisites listed below • If a point-in-time copy of the database is required, the snapshot must contain all the data files, control files and online redo logs. • If full (i.e. zero data loss) recovery is required, the snapshot must contain only the data files or have the ability to restore only the data files. For detailed information refer to Metalink Note 604683.1
- 8. Crash-consistent consistent? • Begin/End backup database vs Crash-consistent • With Begin/End backup • Stops updating datafile headers • Duplicates datafile block writes to redo log Then • Snapshot whole VM…. redo log writes stopped • Crash-consistent snapshot • Just snapshot whole VM - By definition, an online backup is always inconsistent. Pros for VM: Begin/End backup can affect DB only in “physical” world – backup(copying) takes a datafile offline for a long period of time In virtual world – do not affect DB – datafile offline period is very short
- 9. RMAN – differense and benefits only on “physics” • RMAN is to backup online DB • Doesn’t stop updates to datafile headers • Backs up data up to last fixed SCN • redo log is not overloaded Is it a datafile snapshot at Oracle DB level?...
- 10. • Regular backup with fixed RPO • Veeam VM backup w/o interacting with Oracle DB • Veeam VM backup with interacting with Oracle DB • Switch current redo log • Optional – switch DB to hotbackup mode • Backup for Point-in-Time zero dataloss recovery • Veeam VM backup with/without interacting with Oracle DB • Sparately backup/mirror the following • Current Control File • Redo/archive log
- 11. • Recovery with fixed RPO Original: • data files • control files • online redo logs Backups – Restore points Recovered VM: • data files • control files • online redo logs
- 12. • Backup for Point-in-Time zero dataloss recovery Original : • data files • control files • online redo logs Backups – Recovery points Recovered VM: • data files • control files • online redo logs • control files • online redo logs • arch redo logs Restore database Restore/mount • control files • logs • arch logs Recover database
- 13. • No snapshots – no backups (Veeam point of view, and others) • No instant recovery available • Classic approach to backup needed: • Separate OS backup • Separate DB backup • Classic recovery – big(long) RTO……..