Migrate encrypted tables from earlier versions

Steps to migrate encrypted tables from earlier versions to the latest version of Hyper-Converged Database (HCD).

Procedure

  1. Back up the entire keyspace that has a hcd_system.encrypted_keys table.

  2. Back up all system keys.

  3. Upgrade the cluster to HCD 1.2.

  4. Perform a rolling restart of all nodes in the cluster.

  5. Check that the hcd_system.encrypted_keys table was created using the cqlsh DESCRIBE KEYSPACE command.

    If you need to restore the hcd_system.encrypted_keys table, load the table. Do not truncate or delete anything.

  6. If the hcd_system.encrypted_keys table was created, go to the next step; otherwise, create the table manually:

    CREATE KEYSPACE hcd_system WITH replication = {'class': 'EverywhereStrategy'};
    
    USE hcd_system;
    
    CREATE TABLE encrypted_keys (
      key_file text,
      cipher text,
      strength int,
      key_id timeuuid,
      key text,
      PRIMARY KEY (key_file, cipher, strength, key_id)
    );

    EverywhereStrategy is the default replication strategy for the hcd_system and solr_admin keyspaces. Do not use or alter any other instances of EverywhereStrategy.

  7. Rewrite all SSTables.

    nodetool upgradesstables --include-all-sstables

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2025 DataStax | Privacy policy | Terms of use | Manage Privacy Choices

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000, info@datastax.com