| ping.interval |
The interval that the management node pings
backup storages. Default: 60. Unit: second. If a ping succeeds, the
target backup storage is connected to the management node. |
60 |
(0,+∞) |
| ping.parallelismDegree |
The maximum number of backup storages that the
management node can simultaneously ping. Default: 50. |
50 |
(0,+∞) |
| reservedCapacity |
The reserved storage space of a backup storage.
Default: 1 GB. Unit: byte, KB, MB, GB, and TB. |
1 GB |
(0,+∞) |
| ping.maxFailure |
The maximum number of failed connection attempts
that are required to determine that a backup storage and local
backup server is disconnected. Default: 3. If the failed connection
attempts exceeds 3, the backup storage or local backup server is
determined disconnected. |
3 |
[0,+∞) |
| ping.sleepPeriodAfterFailure |
- The interval at which the management node re-pings the
backup storage and local backup server if the previous ping
fails. Default value: 1. Unit: second.
- If set to -1, the management node does not re-ping the
backup storage and local backup server if the previous ping
fails.
|
1 |
[-1,+∞) |
| connection.autoReconnectOnError |
Specifies whether to enable automatic
reconnection if a backup storage or local backup server is
disconnected. Default: true. This value indicates that the
management node auto reconnects a backup storage or local backup
server if the server is disconnected. |
true |
|
| backupStorage.connection.autoReconnectOnError.maxAttemptsNum |
The maximum number of failed attempts of the
management node to automatically reconnect backup storages or local
backup servers. If the number of attempts exceeds the threshold, the
management node stops reconnecting the backup storages or local
backup servers. Default: 0. This value indicates that the management
nodes keeps auto-reconnecting disconnected backup storages or local
backup servers. |
0 |
[0,+∞) |
| blob.upload.concurrency |
- Specify the blob upload concurrency when you upload an
image. Default: 1. Valid values: 1 to 16. Increasing blob
download concurrency increases the efficiency of cloning VM
instances, creating VM backups, and creating images in
certain scenarios.
- To set a blob upload concurrency, take the network
bandwidth, storage medium, and CPU cores into consideration.
A higher concurrency does not necessarily equal a higher
image upload speed in some scenarios. We recommend that you
set the concurrency to 2 if you use a gigabit network and
4-8 if you use a 10-gigabit network. If you use a tape
library as the backup storage medium, we recommend that you
set the concurrency as 1.
|
1 |
[1,16] |
| blob.download.concurrency |
- Specify the blob download concurrency when you download an
image. Default: 1. Valid values: 1 to 16. Increasing blob
download concurrency increases the efficiency of creating VM
instances and recovering backup data on no-Ceph primary
storage in certain scenarios.
- To set a blob download concurrency, take the network
bandwidth, storage medium, and CPU cores into consideration.
A higher concurrency does not necessarily equal a higher
image download speed in some scenarios. We recommend that
you set the concurrency to 2 if you use a gigabit network
and 4-8 if you use a 10-gigabit network. If you use a tape
library as the backup storage medium, we recommend that you
set the concurrency as 1.
|
1 |
[1,16] |
