VPN service backups: what to save

A backup you've never restored is a hope. Here's exactly what to save.

Updated: · Markdown version

What goes into the backup

WhatWhy it matters
Panel database (PostgreSQL for Remnawave)Users, subscriptions, expiration dates, data caps. Without it there's no service.
Connection settings, including Reality keysIn Remnawave these live in the panel database. Make sure they're in the backup and that you know how to get them out.
Panel secrets and environmentTokens, keys, environment variables. Without them the panel won't come back with its old tokens and integrations.
Bot database and settingsPayments, plans, history. Bedolaga has its own database.
Node and proxy configurationSo you can rebuild a node from a record, not from memory.
Domains and DNSWhat points where, which registrar, who has access. The subscription domain matters most: every user link depends on it.

Where to keep it

  • Not on the same server. A backup on the panel server disappears with the server.
  • Ideally not with the same provider.
  • Encrypted. The backup holds user data and secrets. Store the encryption key separately, somewhere it can be found if the owner is unavailable.

How often

It depends on how many changes you can afford to lose. Daily is usually enough for a small service; if hundreds of subscriptions change every day, back up more often.

Why test restores

Common reasons a backup won't restore: missing secrets, a database version mismatch, a corrupted file, a lost encryption key. You only find out when you try.

A minimal check you can run yourself: every so often, restore a copy on a separate machine, confirm the user count matches and the panel loads.

How we handle it

Ghostplane sets up backups at onboarding and checks that they restore. What we back up and how often is agreed during the audit.

Let us look at your network

The audit is free: we review nodes, panel and bot and show the weak spots. We reply on Telegram.

Free audit →