// Module included in the following assembly:
//
// * hosted_control_planes/hcp_high_availability/hcp-disaster-recovery-oadp.adoc

:_mod-docs-content-type: PROCEDURE
[id="hcp-prepare-bm-oadp_{context}"]
= Preparing bare metal to use {oadp-short} for disaster recovery

[role="_abstract"]
Before you can perform disaster recovery for {hcp} on bare metal, you need to meet a few prerequisites and configure the {oadp-first} with Multicloud Object Gateway. 

.Prerequisites

* You installed the {oadp-short} Operator on the management cluster. For more information, see "About installing {oadp-short}".
* You created a storage class for the management cluster.
* You have access to the management cluster with `cluster-admin` privileges.
* You have access to the {oadp-short} subscription through a catalog source.
* You have access to a cloud storage provider that is compatible with {oadp-short}, such as S3, {azure-full}, {gcp-full}, or MinIO.
* In a disconnected environment, you have access to a self-hosted storage provider that is compatible with {oadp-short}, such as link:https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/[{odf-full}] or link:https://min.io/[MinIO].
* Your {hcp} pods are up and running.
* You are using a supported version of {oadp-short} for your management cluster. For example, if your management cluster is on {product-title} 4.20, you must use {oadp-short} version 1.5. For more information, see "Support for {oadp-first}".

.Procedure

* To prepare bare metal to use {oadp-short}, complete the steps in "Configuring the {oadp-full} with Multicloud Object Gateway".
+
After you create the `DataProtectionApplication` object, new `velero` deployment and `node-agent` pods are created in the `openshift-adp` namespace.

.Next steps

* Back up the data plane workload and the control plane workload.
