• 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
        • Converting to Yum installation on RHEL-based systems
        • Converting to APT installation on Debian-based systems
        • Converting to binary tarball installation
      • 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
  • Upgrading OpsCenter
  • DSE OpsCenter upgrade instructions
  • Upgrading tarball installations

Upgrading DSE OpsCenter Tarball Installations

About This Task

These steps provide information on upgrading to OpsCenter 6.8.0 using the OpsCenter tarball and restarting the opscenterd daemon.

Upgrading from OpsCenter 6.1 to 6.8 requires an interim upgrade to OpsCenter 6.5. Upgrade from OpsCenter 6.1 to the most current release of OpsCenter 6.5 before upgrading to OpsCenter 6.8.

Prerequisites

Review Product Compatibility for information on OpsCenter compatibility with DSE.

Before upgrading, backup your OpsCenter keyspace, 6.8, if you anticipate, plan, or need to downgrade to an earlier version of OpsCenter. Downgrading OpsCenter is a very manual and case-specific process. If you require a downgrade, contact DataStax Support for assistance before proceeding.

Additionally, view the folowing compatibility table to ensure that OpsCenter is compatible with your version of DataStax Enterprise.

OpsCenter version DSE version

6.8

6.8, 6.7, 6.0, 5.1

6.7

DSE 6.0

6.5

6.0, 5.1, 5.0 (EOL)

6.1

5.1, 5.0, 5.0 (EOL)

6.0

5.0 (EOL), 4.8 (EOSL), 4.7 (EOSL)

Procedure

  1. Locate the cluster_name.conf file. The location of this file depends on the type of installation:

    • Package installations: /etc/opscenter/clusters/cluster_name.conf

    • Tarball installations: <install_location>/conf/clusters/cluster_name.conf

  2. If you previously configured the api_port (6.8) under the [cassandra] or [storage_cassandra] headers in cluster_name.conf, then delete the entries.

    If this entry still exists under the [cassandra] or [storage_cassandra] headers, OpsCenter will not start.

  3. Download and extract the new tarball: 6.8.

  4. Copy the following files and directories from the old tarball installation directory to the new one:

    conf/clusters/*
    conf/event-plugins/*
    conf/install_id
    conf/logback.xml
    conf/opscenterd.conf
    ./passwd.db
    ./lcm.db
    ./keys/lcm.key

    For example, the following command copies the files in the /conf/clusters/* directory from the old tarball location to the new one, after substituting the location paths:

    scp -r <old_tarball_directory>/conf/clusters/* <new_tarball_directory>/conf/clusters/*
  5. If SSL is enabled, copy the contents of the SSL configuration directory: install_location/ssl/*.

  6. If opscenterd is running, stop the instance, 6.8, and start it from the new tarball installation directory.

What is Next

Upgrade DataStax Agents manually from tarballs.

Upgrading package installations Upgrading when failover is enabled

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