Skip to content

How to Migrate your CloudBeaver Enterprise Workspace

DBeaverDevOps edited this page Jun 19, 2024 · 2 revisions

Table of contents

Overview

This article provides a guide on how to migrate the CloudBeaver Enterprise Edition (EE) workspace. The process involves stopping the server, copying the workspace folder, and then restarting the server.

Tip: For detailed deployment instructions, refer to the Docker image deployment.

Migration process

Step 1: Stop the CloudBeaver EE server

First, stop the CloudBeaver server to ensure that no data is being written to the workspace during the migration. This can typically be done by terminating the running server instance.

Step 2: Copy the workspace folder

Create a copy of the workspace folder. This folder is typically located in the directory specified when the Docker container is launched. For example, to start the container with a specific workspace directory, you might use the command:

docker run --name cloudbeaver-ee --rm -ti -p 8080:8978 -v /var/cloudbeaver/workspace:/opt/cloudbeaver/workspace dbeaver/cloudbeaver-ee:latest

You will need to copy all files from this directory:

  • /var/cloudbeaver/workspace

Make sure to transfer these files to the new location where you wish to migrate your CloudBeaver workspace.

Step 3: Start the CloudBeaver EE server

After relocating the workspace, restart the CloudBeaver Docker container at the new location. When launching the Docker container, it is essential to specify the correct path to the moved workspace to ensure proper configuration. Use the Docker run command with the updated volume path, like so:

docker run --name cloudbeaver-ee --rm -ti -p 8080:8978 -v [new-workspace-path]:/opt/cloudbeaver/workspace dbeaver/cloudbeaver-ee:latest

This command ensures that the CloudBeaver server operates with the workspace in its new environment, maintaining all your configurations.

CloudBeaver Documentation

User Guide

Installation

Configuration

CloudBeaver AWS

CloudBeaver Enterprise Edition

Team Edition

Deployment

Clone this wiki locally