You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After validation, Scylla Manager must copy SSTables of the source node to the corresponding /keyspace/column_family/upload data directory on the destination node.
If the corresponding /keyspace/column_family/upload data directory doesn't exist, it means that schema is not restored.
Service must stop the restore with the meaningful error message.
To download files from the backup location, SM is using RClone.
It's OK to copy all the data from the source_node node/keyspace/column_family location with one call and then monitor the rclone job progress.
The text was updated successfully, but these errors were encountered:
feat(1-1-restore): adds copy data stage + loadSStables call
This adds copy data stage for the 1-1-restore with simple integration
test. Data is copied by each node, table by table and after each table
loadSStables is called.
Note: integration tests with TABLETS=enabled will be skipped as 1-1-restore should only
work with v-nodes.
Refs: #4202#4203
After validation, Scylla Manager must copy SSTables of the source node to the corresponding /keyspace/column_family/upload data directory on the destination node.
If the corresponding /keyspace/column_family/upload data directory doesn't exist, it means that schema is not restored.
Service must stop the restore with the meaningful error message.
To download files from the backup location, SM is using RClone.
It's OK to copy all the data from the source_node node/keyspace/column_family location with one call and then monitor the rclone job progress.
The text was updated successfully, but these errors were encountered: