• Glossary
  • Support
  • Downloads
  • DataStax Home
Get Live Help
Expand All
Collapse All

DataStax Enterprise Upgrade Guide

    • About upgrading
    • Supported & compatible versions
    • Upgrading DSE
      • Planning your DSE upgrade
      • Upgrades for patch releases
        • 6.8.x patch releases
        • 6.0.x patch releases
        • 5.1.x patch releases
        • 5.0.x patch releases
        • 4.8.x patch releases
      • Upgrading DSE 6.7 to 6.8
      • Upgrading DSE 6.0 to 6.8
      • Upgrading DSE 5.1 to 6.8
      • Upgrading DSE 5.0 to 6.8
      • Upgrading DSE 5.0 to 5.1
      • Upgrading from DataStax Installer
    • Upgrading to earlier versions
      • Upgrading DSE 5.1 to 6.0
      • Upgrading DSE 5.0 to 6.0
      • Upgrading to DSE 5.0
        • Upgrading from DSE 4.7 to 4.8
      • Upgrading to DSE 4.7 or 4.8
      • Upgrading to DSE 4.6
      • Upgrading to DSE 4.0 or 4.5
      • Upgrading to DSE 3.2
        • Upgrading from DSE 3.0 to 3.2
        • Upgrading from DSE 2.2 to 3.2
      • Upgrading 5.1 using the DataStax installer
    • Backing up and restoring DSE
      • Backing up a package installation
      • Backing up a tarball installation
      • Restoring a DSE package installation from backup
      • Restoring a DSE tarball installation from backup
        • Upgrading Apache Cassandra
    • Upgrading Apache Cassandra to DSE
    • Upgrading Apache Cassandra
      • Upgrading OpsCenter
    • Before upgrading OpsCenter
    • DSE OpsCenter upgrade instructions
      • Upgrading package installations
      • Upgrading tarball installations
      • Upgrading when failover is enabled
      • Upgrading DataStax Agents
        • Upgrading DataStax Studio
        • Upgrading the DataStax AMI
  • DataStax Enterprise Upgrade Guide
  • Backing up and restoring DSE
  • Backing up a tarball installation

Backing up a Tarball Installation

Backup your existing DSE tarball installation.

  1. Backup the schema to schema_filename.cql using cqlsh.

    /installation_location/resources/cassandra/bin/cqlsh host_ip_address:port  -e 'DESC SCHEMA;' \
     > /backup_path/schema_filename.cql

    A schema backup ensures that even if data is lost you can rebuild the database structure.

  2. Backup the token ranges to token_range_filename`using `nodetool.

    /installation_location/resources/cassandra/bin/nodetool  ring  > /backup_path/token_range_filename
  3. Backup your DSE configuration files.

    Add the following configuration file types to a plain text file listing, backup_file_listing.

    • *.yaml

    • *.sh

    • *.xml

    • *.properties

    • *.default

      find /<installation_location> -type f -name "*.yaml" -o -name "*.sh" -o -name "*.xml" \
      -o -name "*.properties" -o -name "*.default" -type f  >> "/backup_path/backup_file_listing"

      The prior command results in a comprehensive list of all possible customizable file types. You can customize this list depending upon your requirements.

  4. Create a full snapshot, snapshot_name, using nodetool and add the snapshot filenames to a plain text file listing, backup_file_listing.

    /<installation_location>/resources/cassandra/bin/nodetool  snapshot -t snapshot_name
    find /data_directory_location/ -path */snapshots/snapshot_name/* -type f >> "/backup_path/backup_file_listing"

    Make note of the snapshot name in case a restore is required.

  5. Add the commit logs to the plain text file listing, backup_file_listing.

    sudo find /data_directory_location/commitlog -type f >> "/backup_path/backup_file_listing"
  6. Tar up all the backup files into a single archive, backup_archive_name.tar, using the file list, backup_file_listing.

    sudo /bin/tar -pzcvf /backup_path/backup_archive_name.tar --files-from=/backup_path/backup_file_listing

    For large snapshots, consider using the nice command to reduce the load on the node:

    sudo /usr/bin/nice -10 /bin/tar -pzcvf /backup_path/backup_archive_name.tar --files-from=/backup_path/backup_file_listing
  7. Copy backup_archive_name.tar, token_range_filename, and schema_filename.cql to a secure location in case you need to restore your existing installation.

Backing up a package installation Restoring a DSE package installation from backup

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

© DataStax | Privacy policy | Terms of use

DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.

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.

landing_page landingpage