# Notes on published/cf-backup.html, every note on the page. # Written with: python3 -I checks/notes.py published/cf-backup.html --emit # Fields, separated by tabs: kind, title, holds, section, place, text caution Caution list=4 code=2 link=1 Configuring Cloud Foundry for BOSH Backup and Restore body Backup artifacts can contain secrets. Secure backup artifacts with encryption or by other means. The restore is a destructive operation. BBR is designed to restore CF after a disaster. If it fails, the environment could be left in an unusable state and require re-provisioning. For the generic method of restoring a deployment, see Restoring with BOSH Backup and Restore. Developers are unable to push apps for a few minutes during backup and restore. This is because the Cloud Foundry API (CAPI) stops sending and receiving calls between the pre-backup-lock and post-backup-unlock stages of the process. BBR does not back up any service data. Back up Service data, such as Redis or RabbitMQ data, separately. caution Caution link=1 Selective backup and restore configurations for blobstores body Selective backups increase your overall recovery time. When you use selective backup ops files, apps require extra steps to return to a running state after a restore. For more information, see the Restoring apps when using selective backups section below. note Note code=2 Applying ops files in the correct order body You can apply other component ops files before the backup and restore ops files. For example, you can apply other component ops file between use-s3-blobstore.yml and enable-backup-restore.yml.