bosh backup should only export database contents
- It is not practical to export the blobstore due to its potential large size
- user can cancel deploy while the Director is waiting for new VMs to come up
- Useful to be able to cancel deploy if you know that Director will not be able to access VMs; new VMs will be deleted
This release does not include stemcells.
Reference BOSH release in the deployment manifest used with
releases: - name: bosh version: "220" url: https://bosh.io/d/github.com/cloudfoundry/bosh?v=220 sha1: b565f4f935940fb42186558c8877181000634f41
Finally add needed deployment jobs and specify values for required properties.
Optionally download sha1: b565f4f935940fb42186558c8877181000634f41 release tarball locally:
# ...or download it directly using curl $ curl -L -J -O https://bosh.io/d/github.com/cloudfoundry/bosh?v=220 # or with wget... $ wget --content-disposition https://bosh.io/d/github.com/cloudfoundry/bosh?v=220