Azure shared files is recommended over other storage options due to the backup design, ensuring that they can easily be recovered if needed from an automated storage backup.Īzure Backup Volume Snapshots for Oracle provides a recovery solution option for Oracle to secondary or primary VMs to restore the snapshot, then apply the archive logs via RMAN, post the restoration. As with other snapshot solutions, this doesn’t work for Ultra Disk, but as we recommend using Ultra for redo logs, (it’s too often limited in features and cost prohibitive to put datafiles in Ultra) It’s easy to limit the use of Ultra Disk to RMAN for backing up the redo logs and then use these subsequent archive logs, stored on a secondary storage, such as Azure shared files standard share mounted to the VM to provide the Point in Time recovery after a volume snapshot has been recovered.

Having a volume snapshot solution native to Azure for Oracle was an important option for Oracle to Azure in Infrastructure as a Service (IaaS.) For many of our high IO storage solutions, the vendor includes a volume snapshot solution with the storage, but with managed disk from Azure, we were often left to use RMAN, (Oracle’s Recovery Manager) which for smaller databases, (commonly under 1TB in size) is an option, but for larger databases, becomes IO and time inhibitive.ĭue to this, the Azure Backup product team and the Oracle CAE team banded together to design, code and finalize a solution that provides volume snapshots for an Oracle database running on managed disk or Azure NetApp Files, (ANF) in any Azure VM. I previously posted about the importance of volume snapshots and Azure Backup’s private preview for Oracle a number of months back and now it’s generally available!

Data Architecture Blog > Azure Backup Volume Snapshots for Oracle is Now GA!

Azure restore snapshot