How to Backup Critical Metadata on Oracle Big Data Appliance Prior to Upgrade V2.3.1 and Higher Releases (Doc ID 1623304.1)

Last updated on AUGUST 14, 2024

Applies to:

Big Data Appliance Integrated Software - Version 2.3.1 and later
Linux x86-64

Purpose

This document provides details for backing up critical metadata the Oracle Big Data Appliance(BDA) V2.3.1, V2.4, V2.5, V2.6, V3.0.0, V3.0.1, V3.1, V4.0, V4.1, V4.2, V4.3. V4.4, V4.5, V4.6, V4.7, V4.8 and higher releases prior to a Mammoth software upgrade. You can not use the data to roll back an upgrade. The critical metadata is backed up prior to upgrade in case a particular upgrade problem might require evaluation of the previous state or might require extracting some previous state information that will be used to go forward. As such the backup is recommended prior to Mammoth software upgrade.

Note: This document does not provide guidance on a BDA backup strategy. The general recommendation for Backup strategies/Disaster Recovery strategies is using a second BDA configured to back up the first using one of the replication features built into Cloudera Manager. For this please see: Backup and Disaster Recovery (BDR) on Oracle Big Data Appliance FAQ (Doc ID 1615622.1). From that note: All Backup and Disaster Recovery features are now part of Cloudera Manager which is fully licensed with the BDA (along with all of Cloudera Enterprise 5). See the Cloudera Manager Backup and Disaster Recovery documentation for further information.

Scope

This information is intended to be used by anyone wanting to backup their critical metadata on the Oracle Big Data Appliance(BDA) Version 2.3.1, Version 2.4, Version 2.5 or Version Version 2.6 or Version 3.0.0 or Version 3.0.1 or Version 3.1 or Version 4.0 or Version 4.1 or Version 4.2-4.8 and higher.