This topic describes how to use the BOSH Backup and Restore (BBR) command-line tool for backing up and restoring BOSH deployments.

BBR offers a standardized way to backup and restore the BOSH Director and BOSH Deployments that support it.
If you have already set up BBR for your PAS deployment, you might find it easier to use
BBR to back up your Redis service instances, in addition to, or instead of, using automated service backups.

Note: If you have a backup artifact (a dump.rdb file) from any source besides a BBR backup, you can also use it in this restore procedure.

Possible Inconsistent States

Because the Redis On-Demand broker is not locked during the backup process,
the backups of the PAS and service instances can be out of sync if an app developer creates or deletes an on-demand
Redis service between the PAS backup and Redis service instance backups.

No Backup Artifact for a Service Instance

If an on-demand Redis service was deleted in between the backup of the PAS and the Redis service instances,
there is no backup artifact for a deployed service instance.
Resolve this by deleting the service,
which had already been deleted during the backup process so presumably is not wanted.

Backup Artifact for a Non-Existent Service Instance

If an on-demand Redis service was created between the backup of the PAS and the Redis service
instances, there is a backup artifact which has no corresponding deployed service instance.
In this case, the only action you need to take is to skip the restore of this artifact.
The app developer who created the service can recreate it.