[CloudStorage]
Eon Mode only
Important
The [CloudStorage] section replaces the now-deprecated [S3] section of earlier releases. Likewise, cloud storage-specific configuration variables replace the equivalent S3 configuration variables.
Do not include [S3] and [CloudStorage] sections in the same configuration file; otherwise, vbr will use [S3] configuration settings and ignore [CloudStorage] settings, which can yield unexpected results.
Sets options for storing backup data on in a supported cloud storage location.
Note
The [CloudStorage] and [Mapping] configuration sections are mutually exclusive. If you include both, the backup fails with this error message:
Config has conflicting sections (Mapping, CloudStorage), specify only one of them.
Parameter | Description |
---|---|
cloud_storage_backup_file_system_path |
Specifies the host and path that you are using to handle file locking during the backup process. vbr must be able to create a passwordless ssh connection to the location that you specify here. To use a local NFS file system, specify a value of:
To use a host, specify a value of:
|
cloud_storage_backup_path |
Specifies the backup location. For S3-compatible or cloud locations, provide the bucket name and backup path. For HDFS locations, provide the appropriate protocol and backup path. When you back up to cloud storage, all nodes back up to same cloud storage bucket. You must create the backup location in the cloud storage before performing a backup. The following example specifies the backup path for S3 storage:
When you back up to an HDFS location, use the
|
cloud_storage_ca_bundle |
Specifies the path to an SSL server certificate bundle. NoteThe key ( For example:
|
cloud_storage_concurrency_backup |
The maximum number of concurrent backup threads for backup to cloud storage. For very large data volumes (greater than 10TB), you might need to reduce this value to avoid vbr failures. Default: 10 |
cloud_storage_concurrency_delete |
The maximum number of concurrent delete threads for deleting files from cloud storage. If the vbr configuration file contains a [CloudStorage] section, this value is set to 10 by default. Default: 10 |
cloud_storage_concurrency_restore |
The maximum number of concurrent restore threads for restoring from cloud storage. For very large data volumes (>10TB), you might need to reduce this value to avoid vbr failures. Default: 10 |
cloud_storage_encrypt_at_rest |
S3 storage only. To enable at-rest encryption of your backups to S3, specify a value of This value takes the following form:
|
cloud_storage_encrypt_transport |
Boolean, if set to true uses SSL encryption to encrypt data moving between your Vertica cluster and your cloud storage instance. You must set this parameter to true if backing up or restoring from:
Default: true |
cloud_storage_sse_kms_key_id |
S3 storage only. If you use Amazon Key Management Security, use this parameter to provide your key ID. If you enable encryption and do not include this parameter, vbr uses SSE-S3 encryption. This value takes the following form:
|