1.2.8
Improvement:
bbr backup
with BOSH_ALL_PROXY
was still occasionally failing with connection reset by peer
errors. We changed approach in how we handle SSH connection which should make bbr backup
more stable when used with a SOCKS5 proxy. Pivotal Tracker Story and GitHub Issue #21
Improvement:
BBR commands now print the job name in drain logs:
OLD
[bbr] XXXX INFO - Copying backup -- 2.6M uncompressed -- from backup-prepare/XXXX...
NEW
[bbr] XXXX INFO - Copying backup -- 2.6M uncompressed -- for job bbr-usage-servicedb on backup-prepare/XXXX...
This should help users understand where backup artifacts are coming from. Pivotal Tracker Story
Fixed:
Backup metadata were wrongly reporting the job index for backup artifacts. Consider the following example, a multi-master CFCR cluster. The backup artifact is always coming from master/0
while master/1
and master/2
provide no backup artifact. However, previously it was not always reported (in the backup metdatata) that the artifact was coming from master/0
.
This makes no noticeable difference but it fixes the accuracy of the metadata file. Pivotal Tracker Story