yc managed-clickhouse cluster restore
Restore a ClickHouse cluster from a backup.
Command Usage
Syntax:
yc managed-clickhouse cluster restore [Flags...] [Global Flags...]
Flags
|
Flag |
Description |
|
|
IDs of the backup to use for restoring a cluster. |
|
|
Name for the restored cluster. |
|
|
Description for the restored cluster. |
|
|
ID of folder where restored cluster will be created. |
|
|
Environment for the restored cluster. Supported values: 'production', 'prestable'. |
|
|
Network id. |
|
|
Network name. |
|
|
Configurations of the shards that should be created in the cluster. Their number, names and order should match those in the backups whose ids you provide in the flags. Possible property names:
|
|
|
Individual configurations for hosts that should be created for the ClickHouse cluster being restored. Possible property names:
|
|
|
Resource preset for computational resources available to a ClickHouse host (CPU, RAM etc.). |
|
|
Storage type for a ClickHouse host. |
|
|
Storage volume available to a ClickHouse host in GB |
|
|
Resource preset for computational resources available to a ZooKeeper host (CPU, RAM etc.). |
|
|
Storage type for the host. |
|
|
Storage volume available to a ZooKeeper host in GB |
|
|
Allow access for DataLens |
|
|
Allow access for Web SQL |
|
|
Allow access for Yandex Metrika |
|
|
Allow access for Serverless |
|
|
Allow access for DataTransfer |
|
|
Allow access for Yandex Query |
|
|
Version of the ClickHouse server software. |
|
|
Start time for the daily backup in UTC timezone. Format: HH:MM:SS |
|
|
When to move data to Yandex Object Storage. |
|
|
Whether to use cache for data on Yandex Object Storage. |
|
|
Limit for cache for data on Yandex Object Storage. |
|
|
Disable merge of data parts stored in Yandex Object Storage. |
|
|
Whether database management through SQL commands is enabled. |
|
|
Whether user management through SQL commands is enabled. |
|
|
Whether cluster should use embedded Keeper instead of Zookeeper. |
|
|
Auto backups retain period in days. |
|
|
A list of labels as key-value pairs to add for the cluster being restored. |
|
|
Service account for the ClickHouse cluster being restored. |
|
|
A list of security groups for the ClickHouse cluster. |
|
|
Whether to use Yandex Object Storage for storing ClickHouse data. |
|
|
Deletion Protection inhibits deletion of the cluster. |
|
|
ID of the KMS key for cluster disk encryption. Empty input will remove the use of encryption. |
|
|
Password for entity. Usage of --read-admin-password is more secure |
|
|
Read password for entity from input |
|
|
Generate random password |
|
|
Display information about the operation in progress, without waiting for the operation to complete. |
|
|
Disk size autoscaling settings Possible property names:
|
|
|
Maintenance window settings Possible property names:
|
Global Flags
|
Flag |
Description |
|
|
Set the custom configuration file. |
|
|
Debug logging. |
|
|
Debug gRPC logging. Very verbose, used for debugging connection problems. |
|
|
Disable printing user intended output to stderr. |
|
|
Enable gRPC retries. By default, retries are enabled with maximum 5 attempts. |
|
|
Set the ID of the cloud to use. |
|
|
Set the name of the folder to use (will be resolved to id). |
|
|
Set the Cloud API endpoint (host:port). |
|
|
Set the OAuth token to use. |
|
|
Set the ID of the service account to impersonate. |
|
|
Disable opening browser for authentication. |
|
|
Set the output format: text (default), yaml, json, json-rest. |
|
|
Query to select values from the response using jq syntax |
|
|
Display help for the command. |