BBR backup exception rule about bosh-backup-and-restore HOT 3 CLOSED

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/169397639

The labels on this github issue will be updated when the story is started.

from bosh-backup-and-restore.

Hello @vanillacandy,

When a bucket is versioned, bbr assumes that all blobs have a version ID (else it won't be able to back them up). To answer your question, bbr script which backs up the S3 blobstore, can not identify null version ids.

There is a step you can do which should resolve your issue. When you convert a bucket from unversioned to versioned, as you mention, the existing/old blobs do not have version ids. To overcome this, you can copy each blob on-top of itself. That will force the blob metadata to bump, and obtain a version id. You can read about this in our docs here: https://docs.cloudfoundry.org/bbr/external-blobstores.html#-enable-versioning-on-your-s3-compatible-blobstore

The command to do this is (as shown in the docs as well):

aws s3 cp s3://BUCKET-NAME/ s3://BUCKET-NAME/ --recursive --metadata bump=true

Let us know if this resolves your issue :).

from bosh-backup-and-restore.

Thank you @alamages

from bosh-backup-and-restore.