Clone cluster data from one DSE cluster to another using the Restore Backup feature in OpsCenter. This workflow requires
the source and target clusters to both be managed by the same OpsCenter instance.

Clone cluster data from one DSE cluster to another using the Restore Backup feature in OpsCenter. This workflow requires
the source and target clusters to both be managed by the same OpsCenter instance.

Configure Backup Service options in the OpsCenter UI such as commit log backup location, available disk space thresholds,
and encryption key storage. Configure custom scripts to run before or after backups. Configure continuing restores after
a download failure.

Using trend analysis and forecasting, the Capacity Service helps you understand cluster performance within its current environment
and workload, and gain a better sense of how time affects those trends, both past and future.

The OpsCenter Performance Service combines OpsCenter metrics with CQL-based diagnostic tables populated by the DSE Performance
Service to help understand, tune, and optimize cluster performance. Visually enable the performance objects and analyze
the results within OpsCenter.

Cloning cluster data from clusters managed by the same OpsCenter
instance

Clone cluster data from one DSE cluster to another using the Restore Backup feature
in OpsCenter. This workflow requires the source and target clusters to both be managed by
the same OpsCenter instance.

Clone cluster data from one DSE cluster to another using the Restore Backup feature
in OpsCenter. This workflow requires the source and target clusters to both be managed
by the same OpsCenter instance.

Prerequisites

Note: Cloning encrypted tables
to a different cluster does not work unless the encryption keys are identical, which
is typically not the case.

Important: The Backup Service requires control
over the data and structure of its destination locations. The backup destinations
must be dedicated for use only by OpsCenter. Any additional directories or
files in those destinations can prevent the Backup Service from properly conducting
a Backup or Restore operation.

Procedure

Click cluster name > Services.

Click the Details link
for the Backup Service.

In the Activity tab, click Restore
Backup.

The Restore from Backup dialog
appears.

In the Backups tab, select the backup that contains the
data you want to clone and click Next.

Note: On Server backups are not eligible for cloning.

The Restore from Backup: Step 2 of 2 dialog
appears.

In Keyspaces and Graphs, select the tables or graphs you
want to restore.

Click All Keyspaces or All
Graphs to restore all keyspaces or all graphs.

Click the keyspace name or graph name to include all tables or all
graphs in the keyspace.

To select specific tables or graphs, expand the keyspace name or graph
name and select the specific tables or graphs to back up.

Note: For DSE 6.0.0-6.0.4, when restoring a DSE
Graph backup without selecting Use sstableloader, DSE
must be restarted to ensure all data is available.

Under Location, select the target cluster for the
restored data. Select a different cluster than the one that was backed up to
clone the data to the cluster.

The Location list is only available when there are
multiple clusters and both clusters are managed by the same instance of
OpsCenter.

When cloning data, it is not necessary to select the Truncate/delete
existing data before restore option because it is a not
operational 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.

To prevent overloading the network, set a maximum
transfer rate for the restore using the Throttle DSE stream
throughput at ____ MB option.

Note: To enter a value for this option, you must select Use
sstableloader. Otherwise, the transfer rate value is
ignored.

Optional: If necessary, change the staging directory by setting the
backup_staging_directory configuration option in address.yaml.

Required: 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 using LCM to
manage DSE cluster configuration, update Cluster Communication settings
in cassandra.yaml in the configuration profile
for the cluster and run a
configuration job. Stream throughput (not inter-dc) is set to
200 in LCM defaults.

Click Start Restore to confirm the restore.

If the pre-restore checks detected schema differences that could not
automatically be validated, the Restore Schema Validation dialog appears.
Possible issues are listed and a comparison of the backup and current schema
are presented side-by-side.

Review the information to determine if adjustments or corrections to the
current schema are required :

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.

Results

The details and progress of the restore operation are displayed in a progress
dialog, and also appear in the Backup Activity of the target
cluster. If you close the progress dialog, track the progress and status of the
restore in the target cluster's Backup Activity
section.

The progress and details of the restore
operation are displayed in the Restore Report.