Dash Enterprise Administration
4.1.0
4.1.0
  • v4.1.0 Changelog
  • Installation
    • Before you install
    • Dash Enterprise Single Server
      • Installation on cloud provider
      • On-premise installation on own server
      • Fully offline installation
      • VMware Edition installation
    • Dash Enterprise Kubernetes
      • Amazon Web Services resource prerequisites
      • Google Cloud Platform resource prerequisites
      • Microsoft Azure resource prerequisites
  • Configuration
    • Set up your Server Manager
    • Run preflight checks
    • Configure basic settings
    • Authentication settings
      • Built-in local authentication
      • LDAP authentication
      • SAML authentication
    • Dash Enterprise Kubernetes additional required configuration
    • Configure optional settings
    • Other options and customizations
    • Using Snapshots & Backups
    • Running and logging into Dash Enterprise
    • Next steps
  • Advanced Configuration
    • General troubleshooting and problem solving
    • Load balancer configuration
    • Reverse proxy setup instructions
    • Docker storage driver requirements and considerations
    • Import an LDAPS certificate from Active Directory into Dash Enterprise
    • Transfer Dash Enterprise to a new server
    • Sync license changes
    • Change channels for an upgrade
    • Admin panel reference
    • Configure Dash Enterprise to use common SAML IdPs
      • Active Directory Federation Services (AD FS)
      • PingFederate
      • Okta
  • Upgrade
    • Prepare for the upgrade
    • Upgrade
      • Dash Enterprise only instance
      • Dash Enterprise and Chart Studio Enterprise instance
    • After the Upgrade
Powered by GitBook
On this page
  • On the existing Dash Enterprise instance:
  • On the new Chart Studio Enterprise server

Was this helpful?

  1. Upgrade
  2. Upgrade

Dash Enterprise and Chart Studio Enterprise instance

PreviousDash Enterprise only instanceNextAfter the Upgrade

Last updated 3 years ago

Was this helpful?

Make sure the server is stopped as instructed before continuing.

Dash Enterprise can remain on the existing server, but Chart Studio Enterprise will require a new, separate server to be ready for a total of two servers. If you will continue to use Chart Studio Enterprise, you must set up your Chart Studio Enterprise server before proceeding with the Dash Enterprise upgrade.

If SAML authentication was enabled, and since the base domain name changes here, IdP and SP metadata will need to be resync’ed following the upgrade.

If you need to change channels to upgrade, consult

Create a new Chart Studio server and install Replicated on the new server following the installation guide starting from the .

On the existing Dash Enterprise instance:

  • Export the Replicated Server Manager settings to a file.

replicatedctl app-config export > cs-app_settings.json
  • Click on Check for updates in the server manager.

  • Select View Update to see a list of available updates, then click Install Update.

Upgrading Replicated

Check the changelogs to see if Replicated has been updated by the release you’re upgrading to (or any intermediate release you will be installing).

  • If so, on an internet-capable machine, download the latest version mentioned using (replace all 2.45.0 with the version you will need).

  • Upload the resulting file to your server and extract it with the following command

tar xzvf replicated-2.45+2.45+2.45.tar.gz
  • Install Replicated

cat ./install.sh | sudo bash -s airgap

Upgrading Dash Enterprise or Chart Studio

Download a new version of Dash Enterprise and rename the file to add the .airgap extension. If there is more than one new version between your current version and the one you are upgrading to, contact support as you will also need to download certain intermediate versions and they can instruct you which ones are necessary.

Browse to the Server Manager at port 8800 and click the gear icon in the top right to access the Console Settings.

Find the Airgapped Settings section and enter the paths to the new .airgap and your license file, then save your changes.

Go back to the Dashboard; you should see a notice that there is an update available. Select View Update to see a list of available updates, then click Install Update.

  • Transfer plotly_data_dir.tar.gz that was backed-up and cs-app_settings.json exported above to the new Chart Studio server.

On the new Chart Studio Enterprise server

Upgrading to 4.1 will require a new license. Plotly’s support team will provide this to you.

Restore the data and settings on the Chart Studio server and start it by following these steps:

  • Add this license.rli file to the server.

  • Import the new Chart Studio Enterprise license.

replicatedctl license-load < license.rli
replicatedctl license-load --airgap-package /location/of/airgap/bundle.airgap < license.rli
  • Import the settings that were exported and transferred above.

replicatedctl app-config import < cs-app_settings.json
  • Extract the Plotly data directory into /plotly

tar -xvf plotly_data_dir.tar.gz && mv plotly /
  • Check the Server Manager settings and update anything as needed, then restart Chart Studio Enterprise.

  • Update any DNS records to point to the new Chart Studio server.

the License Changes Sync guide.
"Before you install" guide
https://s3.amazonaws.com/replicated-airgap-work/stable/replicated-2.45.0%2B2.45.0%2B2.45.0.tar.gz
during the upgrade prep
during the upgrade prep