Was this page helpful?
Caution
You're viewing documentation for a previous version of Scylla Manager. Switch to the latest stable version.
Restore¶
The sctool restore command allows you to run a restore of backed-up data (identified by its snapshot-tag) into a cluster. Restore and backups are scheduled in the same manner: you can start, stop, resume, and track task progress on demand.
Note
If you are using ScyllaDB Manager deployed by ScyllaDB Operator, see dedicated ScyllaDB Operator documentation.
Warning
Restore works only when ScyllaDB version of backed-up cluster is the same or older than ScyllaDB version of restore destination cluster.
Mixing ScyllaDB Enterprise and ScyllaDB Open Source versions could lead to unexpected results.
Restore types¶
Restore task has to be one of two types:
restore tables - restores the content of the tables (rows)
restore schema - restores the ScyllaDB cluster schema
If both the schema and the content of the tables need to be restored, you must start with restoring the schema. Only after the schema is successfully restored can you proceed with restoring the content of the tables.
Features¶
ScyllaDB Manager Restore command supports the following features:
Glob patterns to select keyspaces or tables to restore
Control over the restore speed and granularity
Dry run - Test restore before live execution
Progress tracking (sctool progress, Prometheus metrics, Scylla Monitoring Manager dashboard)
Restore speed and granularity¶
Restore speed is controlled by two parameters: --parallel and --batch-size.
Parallel specifies how many nodes can be used in restore procedure at the same time.
Batch size specifies how many SSTable bundles can be restored from backup location in a single job.
Note that increasing the default batch size might significantly increase restore performance,
as only one shard can work on restoring a single SSTable bundle.
Those parameters can be set when you:
Schedule a restore with sctool restore
Update a restore specification with sctool restore update