My Oracle Support Banner

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 JUNE 20, 2022

Applies to:

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


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.


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.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 Pre Backup Instructions
 Backing up HBase
 Backing up Spark
 Running dumpcluster BDA 4.0 and higher only (Optional)
 Entering Maintenance Mode
 Backing up NameNode Metadata
 Overview of the Steps for Backing up NameNode Metadata
 Detailed Steps for Backing up NameNode Metadata
 Backing up JobHistory and Task Logs - optional step - only for BDA V2.5 when upgrading to BDA V3.* /BDA 4.*
 Backing up Cloudera Manager Configuration (optional but recommended)
 Backing up BDR Metadata
 Backing up Navigator Metadata
 Bringing the Cluster Offline Prior to Backing up Critical Metadata 
 Prerequisite Checks
 Steps to shutdown the cluster 
 Backing up Cloudera Manager/Cloudera Management Services/Hive/Hue/Oozie/Impala Metadata
 Backing up Navigator Metadata Server
 Backing up the Sqoop2 database  when the Sqoop2 service is configured
 Backing up Kerberos
 Backing up MIT Kerberos
 Backing up AD Kerberos -  BDA V4.2 and higher
 Backing up Key Trustee Server (KTS) and Key Trustee Service (KMS) on BDA V4.4 and higher (also applies to 4.2/4.3)
 Backing up Big Data Discovery
 Bringing the Cluster Back Online after Backing up Critical Metadata
 Post Backup Actions

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.