This topic lists common troubleshooting scenarios and their solutions when using BOSH Backup and Restore (BBR) to back up and restore deployments.
This section provides solutions for errors that occur during a restore.
While running the BBR restore command, restoring the job
mysql-restore fails with the following error:
1 error occurred: * restore script for job mysql-restore failed on mysql/0. ... "Monit start failed: Timed out waiting for monit": 2m0s
This happens when the MySQL job fails to start within the timeout period. It ends up in an Execution Failed state and
monit never tries to start it again.
Ensure that your MySQL Server cluster has only one instance. If there is more than one instances of MySQL Server, the restore fails with a
monit start timeout. Scale down to one instance and retry.
If your MySQL Server cluster is already scaled down to one node, it might have taken longer than normal to restart the cluster. To manually verify and retry:
List the VMs in your deployment by running:
bosh -e BOSH-DIRECTOR-IP --ca-cert /var/tempest/workspaces/default/root_ca_certificate \ -d DEPLOYMENT-NAME \ ssh
BOSH-DIRECTOR-IPis the BOSH Director IP. To retrieve this IP address, see Retrieve BOSH Director Address in Restoring Deployments from Backup with BBR.
DEPLOYMENT-NAMEis the deployment name. To retrieve the deployment name, see Identify Your Deployment in Restoring Deployments from Backup with BBR.
SSH into the
To check that the MySQL job process is running, run:
ps aux | grep galera-init
For more information, see Configuring TAS for VMs.
monit reports that the MySQL job process is in an Execution Failed state by running:
sudo monit summary
If so, deactivate monitoring by running:
Enable monitoring by running:
After a few minutes, run:
The command should report that all the processes are running.
Re-attempt the restore with BBR.
The following error displays:
Deployment 'deployment-name' does not match the structure of the provided backup
The instance groups with the restore scripts in the destination environment do not match the backup metadata. For example, they might have the wrong number of instances of a particular instance group, or the metadata names an instance group that does not exist in the destination environment.
BBR only supports restoring to an environment that matches your original environment. VMware recommends altering the destination environment to match the structure of the backup.
This section provides solutions for general errors.
BBR displays an error message containing “SSH Dial Error” or another connection error.
The jumpbox and the VMs in the deployment are experiencing connection problems.
To resolve connection problems between the jumpbox and the VMs in the deployment:
Ensure your deployment is healthy by running:
Clean up the data from the failed backup on the instances by running:
bbr deployment backup-cleanup
Note: This step is required. Otherwise, further BBR commands fail.
Repeat the BBR operation.
BBR backup or restore fails with a metadata error:
1 error occurred: error 1: An error occurred while running metadata script for job redis-server on redis/0ce9f81f-1756-480b-8e3e-a4609b14b6a6: error from metadata
There is a problem with your deployment install.