Skip to content

VPS

Back up any Linux server by discovering databases, files, containers, and repositories over SSH.

A VPS Stack connects to a server already registered in SimpleBackups and scans it for every resource worth protecting — MySQL, PostgreSQL, MongoDB, and Redis databases, web project files, Docker containers and volumes, Git repositories, and any additional paths you define. It is the right choice for self-hosted stacks, multi-site WordPress servers, and mixed-workload Linux boxes.

Prerequisites

  • A Linux server already added to SimpleBackups under Servers with SSH access configured
  • The SSH user must have permission to read the paths you want to scan and to connect to local database sockets or ports

Supported resource types

Resource typeWhat gets backed up
DatabasesMySQL, MariaDB, PostgreSQL, MongoDB, Redis — full dump
Web projectsFile contents of /var/www, /srv, /opt, or custom paths
Home directoriesFile contents of /home/*
Docker containersRunning containers and their mounted volumes
Git repositoriesGit repos detected under web directories
Custom pathsAny additional directory you specify

Discovery settings

SettingDefaultWhat it does
Discover DatabasesOnDetects MySQL, PostgreSQL, MongoDB, Redis running on the server
Discover Web ProjectsOnScans /var/www, /srv, /opt
Discover Home DirectoriesOffScans /home/*
Discover Docker ContainersOffFinds running containers and their volumes
Discover Git RepositoriesOffFinds Git repos in web directories
Custom PathsAdditional paths to scan

Setup guide

Step 1 — Create a VPS Stack

Go to StacksCreate Stack, select VPS as the provider, and pick the linked server.

Step 2 — Configure discovery

Toggle each resource type on or off, and add custom paths if the defaults don't cover your layout (for example, /data/app or /opt/services). You can adjust these settings later from Stack → Configuration.

Step 3 — Run discovery

Click Discover Resources. SimpleBackups connects over SSH and returns a list of everything found. This typically takes 10–30 seconds.

Step 4 — Review and enable

For each discovered resource, confirm or adjust the backup configuration (database name, path, credentials if needed) and click Create Backup to activate it. Backups then run on your Stack's schedule and land on the storage destination you selected.

Troubleshooting

Databases aren't discovered

  • Verify the database service is actually running (systemctl status mysql, pg_isready, and so on)
  • Ensure the SSH user can reach the local socket or port used by the database
  • If you run databases inside Docker, enable Discover Docker Containers instead

Web projects are missing

  • Confirm your projects live in /var/www, /srv, or /opt; otherwise add the parent directory under Custom Paths
  • Make sure the SSH user has read access to the target directories

A custom path isn't picked up

  • Paths must be absolute and readable by the SSH user
  • Re-run discovery after adding a path — existing runs aren't re-scanned automatically
Stack Discovery OverviewHow Stacks scan your infrastructure and turn discovered resources into automated backups.