Azure Repository
editAzure Repository
editTo enable Azure repositories, you have first to define your azure storage settings as secured settings:
bin/elasticsearch-keystore add azure.client.default.account bin/elasticsearch-keystore add azure.client.default.key
Where account is the azure account name and key the azure secret key.
Note that you can also define more than one account:
bin/elasticsearch-keystore add azure.client.default.account bin/elasticsearch-keystore add azure.client.default.key bin/elasticsearch-keystore add azure.client.secondary.account bin/elasticsearch-keystore add azure.client.secondary.key
default is the default account name which will be used by a repository unless you set an explicit one.
You can set the client side timeout to use when making any single request. It can be defined globally, per account or both. It’s not set by default which means that Elasticsearch is using the default value set by the azure client (known as 5 minutes).
max_retries can help to control the exponential backoff policy. It will fix the number of retries
in case of failures before considering the snapshot is failing. Defaults to 3 retries.
The initial backoff period is defined by Azure SDK as 30s. Which means 30s of wait time
before retrying after a first timeout or failure. The maximum backoff period is defined by Azure SDK as
90s.
endpoint_suffix can be used to specify Azure endpoint suffix explicitly. Defaults to core.windows.net.
cloud.azure.storage.timeout: 10s azure.client.default.max_retries: 7 azure.client.default.endpoint_suffix: core.chinacloudapi.cn azure.client.secondary.timeout: 30s
In this example, timeout will be 10s per try for default with 7 retries before failing
and endpoint suffix will be core.chinacloudapi.cn and 30s per try for secondary with 3 retries.
Supported Azure Storage Account types
The Azure Repository plugin works with all Standard storage accounts
-
Standard Locally Redundant Storage -
Standard_LRS -
Standard Zone-Redundant Storage -
Standard_ZRS -
Standard Geo-Redundant Storage -
Standard_GRS -
Standard Read Access Geo-Redundant Storage -
Standard_RAGRS
Premium Locally Redundant Storage (Premium_LRS) is not supported as it is only usable as VM disk storage, not as general storage.
You can register a proxy per client using the following settings:
azure.client.default.proxy.host: proxy.host azure.client.default.proxy.port: 8888 azure.client.default.proxy.type: http
Supported values for proxy.type are direct (default), http or socks.
When proxy.type is set to http or socks, proxy.host and proxy.port must be provided.
Repository settings
editThe Azure repository supports following settings:
-
client -
Azure named client to use. Defaults to
default. -
container -
Container name. You must create the azure container before creating the repository.
Defaults to
elasticsearch-snapshots. -
base_path - Specifies the path within container to repository data. Defaults to empty (root directory).
-
chunk_size -
Big files can be broken down into chunks during snapshotting if needed.
The chunk size can be specified in bytes or by using size value notation,
i.e.
1g,10m,5k. Defaults to64m(64m max) -
compress -
When set to
truemetadata files are stored in compressed format. This setting doesn’t affect index files that are already compressed by default. Defaults tofalse. -
readonly -
Makes repository read-only. Defaults to
false. -
location_mode -
primary_onlyorsecondary_only. Defaults toprimary_only. Note that if you set it tosecondary_only, it will forcereadonlyto true.
Some examples, using scripts:
# The simpliest one
PUT _snapshot/my_backup1
{
"type": "azure"
}
# With some settings
PUT _snapshot/my_backup2
{
"type": "azure",
"settings": {
"container": "backup-container",
"base_path": "backups",
"chunk_size": "32m",
"compress": true
}
}
# With two accounts defined in elasticsearch.yml (my_account1 and my_account2)
PUT _snapshot/my_backup3
{
"type": "azure",
"settings": {
"client": "secondary"
}
}
PUT _snapshot/my_backup4
{
"type": "azure",
"settings": {
"client": "secondary",
"location_mode": "primary_only"
}
}
Example using Java:
client.admin().cluster().preparePutRepository("my_backup_java1")
.setType("azure").setSettings(Settings.builder()
.put(Storage.CONTAINER, "backup-container")
.put(Storage.CHUNK_SIZE, new ByteSizeValue(32, ByteSizeUnit.MB))
).get();
Repository validation rules
editAccording to the containers naming guide, a container name must be a valid DNS name, conforming to the following naming rules:
- Container names must start with a letter or number, and can contain only letters, numbers, and the dash (-) character.
- Every dash (-) character must be immediately preceded and followed by a letter or number; consecutive dashes are not permitted in container names.
- All letters in a container name must be lowercase.
- Container names must be from 3 through 63 characters long.