DBOps

Control Plane
v3
Waiting for data…
User Manual
A admin
DBOPS WORKSPACE

Activity

Review recent operator and system activity.

Operations Activity

Each operator has a colored branch. Follow connected actions from newest to oldest.

0today
0recent events
Shared team feed
No activity recorded yet. Snapshots, pings, verifications and target switches will appear here.
Esc

Add Any Database Target

Paste a database URL and choose its engine. Connectivity is checked; read-only access depends on the account permissions you configure.

Supported: postgresql://, mongodb://, mongodb+srv://, mysql://, redis://

Create PostgreSQL Snapshot

Creates a point-in-time snapshot without taking exclusive locks.

Primary Database
No servers registered.

Register Remote Server

SSH credentials are encrypted in the app registry. Remote files are limited to the directories entered below.

SSH host identity is checked against the app's trusted known_hosts file. Enter absolute Linux paths; database and snapshot paths may be the same. Their parent directories must already exist; registration checks paths without creating remote files.

Create Isolated Database Container

New container and new data directory only. Existing containers are not changed.

Letters, numbers, dots, underscores, and hyphens; must be unique on this server.
Select a server port to check.
postgresql://dbops:PASSWORD@SERVER_HOST:55432/appdb
The preview updates as you enter values. Reserved characters in credentials are percent-encoded.
Supported image tags: postgres:16-alpine, mongo:7, mysql:8, mariadb:11.4, redis:7-alpine.
After creation, the new database is selected under Targets. Click its masked connection URL in the Console toolbar to copy the full URL. The server port must be reachable by teammates who connect from outside this application.

Automated Snapshot Schedule

Choose the database to snapshot, where to copy it, and when the schedule runs.

A local archive is always saved in the configured backup folder.
Optionally copy each completed snapshot to mounted repositories or registered remote servers. Copies are checksum-verified.
Loading repositories…
Loading servers…
The preview also shows this time in Sri Lanka time (SLST, UTC+5:30).
Snapshots will run every day at 02:00 UTC (Sri Lanka time: 7:30 AM).
--

Archive Integrity Verification

Non-destructive checksum & table-of-contents validation.

Validating TOC and checksums…

Restore Snapshot

Choose which saved snapshot to copy, where to restore it, and whether to create a database or write into an existing one.

Only databases with a completed snapshot can be used as a restore source. Registered PostgreSQL databases without a completed snapshot are shown as unavailable. Choose a registered database to narrow the snapshot list. This is the source; the destination is selected separately below.
This is a saved copy of the source database. The source is unchanged unless you explicitly choose it as the existing restore target.
Before restoring, check the PostgreSQL major version on the snapshot source and target. Use the same major version for the most reliable restore; restoring a newer-version snapshot to an older server may fail because it does not support settings or features in the archive.
Only “Local or mounted repository” appears until this snapshot has a verified copy on a registered remote server. To add a remote option, register a server in Servers and copy this snapshot there. Remote copies can only restore into a new database.
Choose a registered PostgreSQL target. To restore into another existing database, choose “Write into an existing database” below; this list will show registered PostgreSQL databases you can select.
Created on the destination server. Must be a new name that does not already exist there.
A separate database will be created on the selected destination server. Existing databases, including the snapshot source, are left unchanged.
Restore plan
Snapshot fromSelect a snapshot
Restore toSelect a destination
EffectNo database has been changed yet.

Telegram Notifications

Route operational events to a Telegram chat. Settings are stored on the server and seeded from environment variables.

Stored server-side. The saved token is shown masked.
Optional fixed chats. Users who send /start to this bot are added automatically; /stop removes them. The listener needs polling access (no webhook configured).
Registered Telegram IDs
  • No users have registered with /start yet.

Please confirm

Are you sure?

Manage users

Create login credentials or remove an account.

Administrators can manage users and access all application features.
When enabled, the new user must scan the QR code below during first sign-in.