Restoring data on the standby site

Before you begin

Make sure that you have configured disaster recovery. For configuration steps, see Configuring-disaster-recovery.

Make sure you restore BMC Discovery data.
For more information, see "To failover to the secondary cluster" section in the Creating a disaster recovery cluster for Discovery topic in the BMC Discovery documentation.

To scale up the standby site

If you had scaled down the application pods on your standby site, perform the following steps to scale it up:

1. Go to helix-on-prem-deployment-manager/utilities/disaster-recovery/dr-scale

2. Run the following command:

    ./product_scale.sh  up 

To restore data on the standby site 

1. Go to /helix-on-prem-deployment-manager/utilities/disaster-recovery/dr-configs. 

2. In the disaster-recovery.config file, specify the values of the following parameters:
   

   Parameter	Description	Example
   BUCKET_NAME	Specify the name of the bucket used to restore data on MinIO.	BUCKET_NAME=helixdr-restore
   SITE_NAME	Specify the name of the site from where you want to restore data.	SITE_NAME=India
   NAMESPACE	Specify the namespace where you have installed BMC Helix IT Operations Management.	NAMESPACE=helix-cluster3

3. To restore data, run the following command: 

   ./disaster-recovery.sh restore 

   The standby site takes over the operations until you fail back to a primary site.
   To know more about the options to fail back to the primary site, see Disaster-recovery-deployment.

4. After data restoration, if Victoria Metrics restarts it restores the older data. To prevent such unintended data restorations, run the following commands:
   

   export FORCE_DISABLE_VM=1
   
   ./disaster-recovery.sh disable victoriametrics