Creating backups on Azure with Elasticsearch requires a different approach, and as such, the specification of parameters is different from the usual proceedings.
Some settings are still configured on the backup-service, whereas the credentials for the Azure account itself must be specified in the deployment manifest of the service instance because the credentials have to be present on all cluster nodes.
You need access to Azure. There are three parameters you need for that (in terms of the
Configuring the Backup Service
The settings required to configure the backup-service are
Configuring Service Instances
Unfortunately, the way of how and where to specify credentials differ in version 5 and version 6. However, the way of specifying it in the deployment manifest is the same. Only the key names differ there.
Elasticsearch Version 5
Properties of an a9s Elasticsearch instance in version 5:
Elasticsearch Version 6 (+)
Properties of an a9s Elasticsearch instance in version 6:
Verify Your Setup
To check whether the backup works or not, you can use the
az CLI. You will need your deployment name, which you can find out either by having a look at your
bosh tasks or by creating a
cf service-key and having a look at the hostname. In this example the deployment name is
d13d357. Use the
az CLI like so to find backups for your service instance:
az storage blob list --account-key 'your-account-key' --account-name 'your-account-name' --container-name 'your-container-name' --prefix=d13d357
Globally Setting Default Credentials
If you want all service instances to share one set of azure credentials you can do so by modifying the properties of the template-uploader job in your a9s Elasticsearch service deployment, e.g.:
+ /elasticsearch_backup_azure_account_name: 'your-account-name'
+ /elasticsearch_backup_azure_account_key: 'your-account-key'
+ - ops/es-backup-azure-credentials.yml
+ - ops/es5-backup-azure-credentials.yml
Note: After adding those lines, the template uploader errand must be executed.