Dash Enterprise Administration
4.3.1
4.3.1
  • Changelog
  • Installation
    • Capacity Planning
      • Dash Enterprise Single Server
      • Dash Enterprise for Kubernetes
    • Before you install
    • Dash Enterprise Single Server
      • Installation on cloud provider
      • On-premise installation on own server
      • Fully offline 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
    • Add SELinux permissions to mapped directories
    • Other options and customizations
    • Using Snapshots & Backups
    • Running and logging into Dash Enterprise
    • Next steps
  • Advanced Configuration
    • General troubleshooting and problem solving
      • Dash Enterprise Kubernetes
    • 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
    • Configure Dash Enterprise to use common LDAP IdPs
      • Okta
  • Upgrade
    • Prepare for the upgrade
    • Upgrade
      • Dash Enterprise Single Server
      • Dash Enterprise for Kubernetes
    • After the upgrade
  • Advanced Troubleshooting
    • Dash Enterprise Architecture and Internals
    • Navigating the System
    • Navigating the Support Bundle
    • Getting Help and Reporting Issues
    • Troubleshooting Specific Issues
Powered by GitBook
On this page

Was this helpful?

  1. Advanced Configuration

Transfer Dash Enterprise to a new server

PreviousImport an LDAPS certificate from Active Directory into Dash EnterpriseNextSync license changes

Last updated 2 years ago

Was this helpful?

1 - Go to the Server Manager; then select Stop Now to stop the running instance.

2 - Back up your Plotly data directory the same way you would when preparing for an upgrade (see for guidance).

3 - Transfer your data directory to your new server using your preferred method (e.g. rsync).

4 - Install Dash Enterprise from scratch on your new server using the Plotly instructions in this guide that are appropriate to your use case.

4.1 - , specify the transferred data directory as your new Plotly data directory.

4.2 - You will need to SSH into your server and rebuild your Dash services and apps from within the dash container for them to start up correctly:

docker exec -it dash bash

for service in $(dokku --quiet redis:list); do dokku redis:start $service; done

for service in $(dokku --quiet postgres:list); do dokku postgres:start $service; done

dokku ps:rebuild --all

5 - Once the installation is complete and running on your new server, you can stop the running instance on your old server.

When configuring the new instance's Settings
Back up your Plotly data and databases