1.8.1

Features

• Add specific error message if network drops during SSH.

Fixes

• Update all golang dependencies.

Other

• Add the S3 config validator's source code.

1.8.0

This version introduces the bbr S3 configuration validator. A tool you can install on your BBR VM in order to test your configuration and connectivity to an external blobstore.

1.7.2

Bump dependencies

1.7.0

Features

Progress indication for restore files when BBR transfer files from the BBR client to the restored component.

1.6.0

Stories

• https://www.pivotaltracker.com/story/show/163736175

Features

• Progress indication for backup files when BBR transfer files to the BBR client

1.5.2

Release Date: August 29, 2019

Features

• Add short version of the --artifact-path flag: -a.

Improvements

• BBR will not log that the backup was successful if it draining fails.
• Bump Golang Crypto and Golang Sys libraries.

1.5.1

Release Date: May 3, 2019

Features

• Added the ability to gracefully skip BOSH jobs. In order to use this feature, add the following property to the <job-dir>/bbr/bin/metadata file:

skip_bbr_scripts: true

Improvements

• Improved error messages when BBR fails while processing a metadata file.
  • Error messages used to, unnecessarily, be repeated.

Bug Fixes

• bbr will not hang if the SSH key passed via the BOSH_ALL_PROXY is invalid.
• BOSH_ALL_PROXY now sets a server keep-alive interval which ensures it will not timeout during long-running processes such as the backup checksum step.

1.5.0

Release Date: March 27, 2019

Features

• Release authors can now specify job dependencies for BOSH director jobs using the metadata hook. For example:

  #!/usr/bin/env bash
  
  echo "---
  restore_should_be_locked_before:
  - job_name: uaa
    release: uaa"
  

• Release authors can now tell BBR to backup from one instance of a job (bootstrap node) and restore to all instances by using the BOSH property bbr.backup_one_restore_all.

Deprecation

• Backwards incompatible: Dropped support for backup_name and restore_name properties in the metadata hook.
  • Action required: if you are using these properties, see if the bbr.backup_one_restore_all BOSH property can be used to replace this functionality (see cloudfoundry-incubator/cfcr-etcd-release#11 as an example).

1.4.0

Release Date: February 21, 2019

Features

• Release authors are now able to check the BBR version by testing the $BBR_VERSION variable in metadata:

  #!/usr/bin/env bash
  if [ -z "$BBR_VERSION" ]; then
    # This message will be printed if using BBR 1.3.x or earlier
    >&2 echo "BBR_VERSION is not set, unsupported bbr cli, I am out of here"
    exit 1
  fi
  
  # This message will be printed if using BBR 1.4+
  echo "I am ok"
  

• Job dependencies are now supported for bbr director backup and bbr director restore.

  • Earlier versions of BBR will fail if a director job declares a dependency.

Improvements

• A reminder to run bbr backup-cleanup will be printed when the pre-backup check fails.

  • This can happen if you try to run backup, it fails, and then try to run backup again without cleaning up.
  • Before this change, the reminder to run bbr backup-cleanup would only be printed once, after the first failed backup.

• The size of backup artifacts that are transferred to the BOSH deployment will now be printed during restore.

  • Prior to this change, the artifact size was only printed during backup.

1.3.2

Release Date: January 2, 2019

Improvements

• Log files created when using BBR to do a multi-deployment backup can now be read while BBR is running:

   # run BBR in the background
   bbr deployment --all-deployments backup &
  
   # monitor BBR's progress by reading the log files while BBR is running
   tail *.log