Backup and restore in Cloudera Data Warehouse on premises
The backup/restore feature saves your environment parameters, making it possible to recreate your environment with the same settings, URL, and connection strings you used in your previous environment. Learn about the different backup and restore methods, objects and configurations that are included in the backup, and the backup method to use in different scenarios.
For cluster maintenance and integrity, you can back up the Cloudera Data Warehouse cluster including its Kubernetes objects, persistent volumes, autoscaling configuration, and so on for various Cloudera Data Warehouse entities such as the environment, Database Catalog, Virtual Warehouses, and Data Visualization instance. You can recreate the deployment by restoring the backed-up configurations and settings, as part of the planned maintenance or in a disaster recovery scenario.
Available backup and restore methods
There are two ways to backup and restore the Cloudera Data Warehouse service:
- Using Data Recovery Service
- Using the Cloudera Data Warehouse’s Cloudera CLI cluster management commands
Both these methods use Cloudera CLI commands. The Cloudera Management Console also provides a graphical user interface to perform backup and restore operations. See Data Recovery Service automatic backups and Using Data Recovery Service with Cloudera Data Warehouse.
Deciding which backup method to use
Use Data Recovery Service to back up all Cloudera Data Services on premises environment configurations for an ECS or Cloudera Data Services on premises upgrade. Data Recovery Service takes a snapshot of the namespace on the Kubernetes cluster. You can also choose Data Recovery Service if some Cloudera Control Plane service fails and you need to reinstall it with a previously preserved configuration.
If you just want to back up your Database Catalog or Virtual Warehouse configurations to recreate Cloudera Data Warehouse from an earlier configuration, use Cloudera Data Warehouse’s backup and restore commands.
