Crash consistent backups and database cloning with Virtual Volumes
In the first part of this series we provided a high level view of the benefits of using Virtual Volumes enabled storage for database operations. In the second part of this series we examined in more detail how Virtual Volumes can improve the backup and recovery capabilities for business critical databases, specifically Oracle.
The backups for Oracle can be Database consistent or Crash consistent. In this part we will look at Crash consistent backup and recovery and also how database cloning is simplified by the use of VVol.
The setup of the infrastructure is the same as discussed in the second part of this series. Please refer to setup section for details of the infrastructure and the database configuration.
Database Crash Consistent Recovery and cloning use case Scenarios:
Crash Database Backup & Recovery using VVol Snapshots:
Crash Consistent Backup:
A crash consistent backup is the backup of a point-in-time image of an Oracle database that is equivalent to a database crash induced by a power outage, other failures or a shutdown abort.
This is the most common backup method used for storage based backups and is fully supported by Oracle as long as the following conditions are met.
From the “Supported Backup, Restore and Recovery Operations using Third Party Snapshot Technologies (Doc ID 604683.1)”:
The third party vendor needs to guarantee and held accountable that their snapshots conform to all the following requirements:
- Integrated with Oracle’s recommended restore and recovery operations above
- Database crash consistent at the point of the snapshot
- Write ordering is preserved for each file within a snapshot