Backup in Azure

This article covers backup procedures that must be used for different types of data including:

  • OS and software on the cluster nodes
  • Database files
  • Files on ACFS, if used

Backing up OS and software on the cluster nodes

It is strongly recommended to back up the OS disk and software disk (LUN 0) of all cluster nodes after the initial cluster configuration and before and after applying any changes such as patch installation or security settings changes. Taking disk snapshots is the recommended method for backing up the disks.

Note that Azure Backup service is not currently supported due to its existing restrictions.

To create a backup of a cluster node VM

  1. If the node is a database node, stop all database instances.

  2. If the node is a database node, stop Oracle Clusterware services.

    # crsctl stop crs

  3. Stop FlashGrid Storage Fabric services on the node

    # flashgrid-node stop

  4. Stop the VM using Azure portal or CLI

  5. Create snapshot of the OS disk

  6. Create snapshot of the software disk (LUN 0)

Backing up database files

Standard RMAN procedures should be used for backing up and restoring database files.

Two main options for backup destination are available:

  1. A disk attached to one of the database node VMs
  2. Azure File Share

Configuring a disk attached to one of the database node VMs for database backup

  • This option allows higher performance of the backups and does not consume network bandwidth
  • The disk must be attached with a LUN number 50 through 64 (LUNs 1 through 49 are automatically shared by Storage Fabric).
  • The disk must be formatted with a local file system, such as XFS.
  • Disk snapshots can be used for exporting backup data to external locations (Make sure that RMAN backup is complete before you make snapshot of the backup disk.)

Configuring Azure File Share for database backup

  • Create Standard performance Storage Account and add a file share.

  • Install cifs-utils package on all database nodes:

    # yum install cifs-utils -y
  • Make sure port 445/TCP is not blocked:

    Azure Files uses SMB protocol, which communicates over TCP port 445. If you're having trouble mounting your Azure file share, make sure your firewall is not blocking TCP port 445.

  • Create backup mount point on each database node:

    # mkdir /db_backup
    # chown oracle:oinstall /db_backup
    # chmod 755 /db_backup
  • Create a persistent mount point for the Azure file share in /etc/fstab on each database node. Example:

    //  /db_backup cifs vers=3.0,username=mystorageaccount,password=c3N+JcWQk7bw0yTT/yAMBmDcEFcRa4AkPQp+zpaljj6e...,dir_mode=0755,file_mode=0755,gid=2000,uid=3001

    Where uid and gid options are Oracle software owner user and group ids respectively. If you have a customized user, then you need to change these parameters accordingly.

  • Mount the backup folder:

    # mount /db_backup

Backing up Grid Infrastructure configuration files

Please follow Grid Infrastructure Backup and Restore Best Practices

Backing up files on ACFS

For backing up and restoring files on ACFS use same tools and procedures that you would normally use for file-level backup and restore.