Managing Team Edition server

Overview

This guide covers the initial launch, management, and maintenance of Team Edition, focusing on server configuration, updates, and backups.

Important

The Server Manager is only available for Linux, including Linux-based servers on Azure, GCP, and AWS.

Launch your Team Edition instance

After launching your instance, follow these steps to access Team Edition:

Open http://<Instance_IP>/ in your browser, where <Instance_IP> is the instance’s public IP.
The Team Edition setup wizard will guide you through the initial configuration.

Tip
For help locating the public IP address of your instance on each platform, see these resources: - AWS: Finding the Public IP Address of Your Instance - GCP: Viewing IP Addresses - Azure: Find IP Address of a VM

Info

See Team Edition Administration guide for detailed setup instructions.

Managing Team Edition with the server manager utility

Team Edition provides a built-in server manager utility in cloud deployments. Use it to manage server tasks like starting, stopping, updating, configuring, and backing up.

Using the server manager

Enter the following command to see available options:

dbeaver-te help

Managing server state

To start or stop the server:

Start the server:
```
dbeaver-te start
```
Stop the server:
```
dbeaver-te stop
```

Version update procedure

To update Team Edition, follow these steps:

Connect to the cloud instance via SSH.
List available versions:
```
dbeaver-te update list
```
Choose a version and run the update command:
```
dbeaver-te update 24.2.0
```

Note

Replace 24.2.0 with the desired version number.

Backup and restore procedure

Back up Team Edition’s state, including service volumes, database dumps, and internal certificates:

Create a backup:
```
dbeaver-te createBackup
```
Options:
- --include-certs: Adds certificates to the backup.
- --skip-db-service: Skips database dump for external databases.
Restore from backup:
```
dbeaver-te restoreBackup
```

Server configuration

To modify the Team Edition server configuration, edit the .env file:

dbeaver-te configure