#DATA BACKUP AND RESTORE FULL#

In order to have a consistent backup Cloudera recommends that no workloads are running when If you stop or restart Data Lake services fromĬloudera Manager, such as restarting all services, or restarting the HBase or Solr services,ĭata Lake backup and restore operations from the CLI will be allowed to go forward, but may Other considerationsĭo not stop or restart Data Lake services in Cloudera Manager if you are planning on They must be running during a backup or restore operation. Principal servicesīackup and restore operations are dependent on the following services: Data Lake restore replaces the existing Data Lake content withĬontent from a Data Lake backup.

Data Lake Restore vs Repairĭata Lake repair replaces the compute resources and reconnects them to the See Configuring and running Data Lake backups and Configuring and runningĭata Lake restore for more information. Process, or run the validation process without proceeding to the backup/restore operations. You can use CLI commands when you run the backup/restore operations to skip the validation The backup operation only, the validation process also checks if there are any stale RangerĪudit permissions that are over 90 days old. Required permissions are granted on the backup location with the cloud provider (AWS andĪzure) and that the required Ranger RAZ permissions are granted on the backup location. These validations include verifying that the Before a backup or restore operation begins, a validation process checks for the mostĬommon causes of a backup or restore failure. Is there any validation that occurs before the backup/restore operations? When backups are taken, there is downtime for principal services (see 'Principal services'īelow) due to the requirement to shut down HMS service on any attached Data Hubs. Information, and HMS metadata) from one environment to another.

Moving the Data Lake metadata (Atlas lineages, Ranger policies and audit.

This backup canīe used to restore the existing environment or create a new environment in case the upgradeįails in a manner that requires you to re-build the original environment.

Upgrades: a backup can be performed before performing an upgrade.

You can run backups as part of these events: The backup files are stored on AWS S3, ADLS, or Google Cloud Storage with encryption

Permissions and tags, saved in RDBMS tables.

#DATA BACKUP AND RESTORE FULL#

Edge, vertex, and full text indexes, saved in Solr collections.Lineage data, saved as Janus graph data in HBase tables.The backup operation saves a full snapshot of data from all SDX services: There isn't another backup or restore in progress. Operation from any host with connectivity to the Data Lake. Note that a Data Lake Backup includes metadata about your cluster workloads and does notĪt this time, you can trigger a Data Lake backup through a CDP command-line If the database connections are closed, Data Hub workloads will fail. If you want to keep Data Hubs running during a backup, you must keep the HMS databaseĬonnections open to the Data Lake using the no-close-db-connnections CLI However, you are not required to stop the Data Hub workloads before performingīackup. Important for migration use cases where you would like to move metadata from one environment In order to make sure there are no updates to HMS, theīackup and restore process closes all the connections to the HMS backend database. In order to have a consistent backup Cloudera recommends that no workloads are Important: Data lake backup/restore operations should be performed when the Data Lake See ConfiguringĪnd running Data Lake backups for more information. Hub workloads to continue running during the Data Lake backup process. No-close-db-connnections when you run the backup. Additionally, access to the HMS database will be blocked by defaultįor the duration of the backup, but you can optionally bypass this using the CLI option There will be a downtime when a Data Lake backup is performed, as some Data Lake to promote Data Lake content from test to production.for archiving Data Lake content for later reference.in preparation for a Data Lake upgrade.

Data backup and restore