Cloning cluster data from a defined other location

Clone cluster data from one DSE cluster to another using the Restore Backup feature in OpsCenter. This workflow does not require the source and target clusters to both be managed by the same OpsCenter instance. This workflow does not necessarily even require another existing cluster instance. The data can be cloned providing it was backed up to an available Local FS or an Amazon S3 location.

1. Click the target cluster name > Services.
2. Click the Details link for the Backup Service.
3. In the Activity tab, click Restore Backup.
4. Click the Other Location tab.
   The Step 1 of 3: Select Backup Restore from Backup dialog appears.

   

5. Select the Location. Available options are:
   • Amazon S3 (default): Go to 6.
   • Local FS: Go to 7.
6. If the location is Amazon S3:
   1. Enter the S3 Bucket name.
   2. Enter your AWS credentials in AWS Key and AWS Secret.
7. If the location is Local FS, enter the Path to the backups.
8. Click Next.
   The Step 2 of 3: Select Backup Version dialog appears populated with the available backups at the selected location. For more, see Adding an Amazon S3 backup location.

   

9. Select the backup to restore and click Next.
   The Step 3 of 3: Configure and Restore dialog appears.

   

10. In Keyspaces and Graphs, select the tables or graphs included in the backup you want to restore.
    1. Click the keyspace name to include all the tables in the keyspace. Click All Keyspaces to restore all the keyspaces. To select only specific tables, expand the keyspace name and select the tables.
    2. Click the graph name to include all the graphs in the keyspace. Click All Graphs to restore all the keyspaces. To select only specific graphs, expand All Graphs and select the graph keyspaces.
11. In the Location list, select the cluster to clone the data to.
12. When cloning data, it is not necessary to select the Truncate/delete existing data before restore option because it is a no-op for a cloning workflow. The truncate option purges data on a target before a restore runs. When using the restore feature to clone, the truncate option does not do anything because there is no data to purge before the restore runs.
13. To prevent overloading the network, set a maximum transfer rate for the restore. Select Throttle DSE stream throughput at ____ MB and set the maximum MB per second.
14. Optional: Change the staging directory if necessary by setting the backup_staging_directory configuration option in address.yaml.
15. Click Restore Backup.
    The Confirm Restore dialog appears.

    

    Warning: If a value was not set for throttling stream output, a warning message indicates the consequences of unthrottled restores. Take one of the following actions:

    • Click Cancel and set the throttle value in the Restore from Backup dialog.
    • Set the stream_throughput_outbound_megabits_per_sec and inter_dc_stream_throughput_outbound_megabits_per_sec values in cassandra.yaml.
    • Proceed anyway at the risk of creating network bottlenecks.

    Tip: If you are using LCM to manage DSE cluster configuration, update Cluster Communication settings in cassandra.yaml in the config profile for the cluster and run a configuration job. Stream throughput (not inter-dc) is already set to 200 in LCM defaults.

    

16. Review the information to determine what adjustments if any need to be made to the current schema:
    • To rectify the schema issues and try the restore again afterward, click Cancel.
    • To proceed despite the schema mismatch, click Continue Restore.
      Warning: Attempting to restore a backup with an incompatible schema might result in corrupt or inaccessible data. Before forcing the restore, back up your current data.