Back Up and Restore Essbase

Periodically, you may need to restore your instance from a backup. The topics below explain how to do this for stack deployments on Oracle Cloud Infrastructure where you have a single Essbase instance and have deployed using Autonomous Transaction Processing Database.

Topics:

Required Policies

A policy is a document that specifies who can access which Oracle Cloud Infrastructure resources that your company has, and how.

See Set Up Policies and How Policies Work.

allow dynamic-group group_name to use autonomous-database in compartment compartment_name
allow dynamic-group group_name to read buckets in compartment compartment_name
allow dynamic-group group_name to manage objects in compartment compartment_name
allow dynamic-group group_name to manage autonomous-backups in compartment compartment_name
allow dynamic-group group_name to manage volume-backups in compartment compartment_name
allow dynamic-group group_name to manage volume-group-backups in compartment compartment_name
allow dynamic-group group_name to manage volumes in compartment compartment_name
allow dynamic-group group_name to inspect volume-groups in compartment compartment_name
allow dynamic-group group_name to manage buckets in compartment compartment_name

Set Up a Bucket to Store Manual Backups

This is a one-time action.

You are not required to set up a bucket to store manual backups if your instance is configured using Autonomous Transaction Processing - Dedicated (ATP-D).

  1. If you have not already done so, generate an auth token for the Oracle Cloud Infrastructure Object Storage user to access the bucket you create in the next step. See create an auth token to learn how to do this. You will need this auth token for the database credential you create in step 5.
  2. SSH to the Essbase host. See Access Oracle Essbase Using SSH.
  3. Become user oracle.

    sudo su - oracle

  4. Change directory to /u01/vmtools.

    cd /u01/vmtools

  5. Run script ./configure-backup-storage.sh and input the required fields:
    • Database Admin Password
    • Oracle Cloud Infrastructure Admin User Name
    • Oracle Cloud Infrastructure Admin Token – this is the token you created in step 1.

Create a Manual Backup

Create a manual backup of Essbase.

  1. SSH to the Essbase host. See Access Oracle Essbase Using SSH.
  2. Become user oracle.

    sudo su - oracle

  3. Run this command:

    crontab -e

  4. Add cron entry. For example, to run every day at 00:01, as the host timezone of the computer instance, enter:

    1 0 * * * /u01/vmtools/backup.sh > /dev/null

    Note that the backup script should be run in background mode or cronjob. In interactive mode, the script may time out and the instance may not start up.

  5. Save the file.

Restore from Backup

Restore Essbase from backup in the Oracle Cloud Infrastructure console.

  1. Choose the date and time you want to restore.
  2. Check block storage backup and Autonomous Transaction Processing backup exist with the same creation time stamp.
  3. Navigate to the block storage backups:
    1. Open the navigation menu.
    2. Under Core Infrastructure, go to Block Storage and click on Block Volume Backups.
  4. Create two new block storage volumes (Data and Config) from the selected backups.
  5. Add newly created block volumes to the instance's Volume Group.
  6. Stop the service.
  7. Restore Autonomous Transaction Processing.
  8. Navigate to the compute on the Oracle Cloud Infrastructure console.
  9. On the Resources tab, click Attached Block Volumes.
  10. For each disk:
    1. Click on the menu Image of the OCI block volume menu icon. next to the disk.
    2. Click Detach.
    3. Click Continue Detachment and Okay.
    4. Wait for the old disk to be detached.
  11. After both disks are detached, attach the newly created volumes to the instance, keeping the same device path.
  12. Wait for the disks to be attached.
  13. Wait for Autonomous Transaction Processing to be restored.
  14. After Autonomous Transaction Processing is restored, and the status is AVAILABLE NEED ATTENTION, stop and then restart it.
  15. Restart the instance.
What’s Not Recovered in Disaster Recovery or Restore to New Instance

An Essbase connection to an Essbase instance created in a source stack doesn’t work after disaster recovery or backup/restore is made to a new Essbase Marketplace instance.

For example, let’s say an Essbase connection is created to an Essbase instance (Stack A) and a block backup is run. Later, a disaster occurs and Stack A no longer works. We create another Essbase instance (Stack B) and restore to it the blocks backed up from Stack A. After the restore/recovery to the new instance, the connection to stack A no longer works.