How do I back up directories, system files or MongoDB?

Directory / system files jobs

A Directory job backs up folders that are not accounts: a symlink's target, a data volume, configuration folders.

1. Open Backup jobs and choose + New job.
2. Set Source to "Directory / system files". There is no Panel type choice.
3. Enter absolute paths separated by commas in Directory paths.
4. Pick a destination, optionally set excludes, and create the job and schedule.

Each configured path is backed up as one pseudo-account, and the whole engine is reused (walk, dedup, bundling, sealing, manifest, integrity, cleanup and retention). Notes:

• Paths are checked for safety. / and /proc, /sys, /dev and /run are rejected.
• Directory jobs use only the job's own exclude patterns, not the server-wide defaults.
• Directory jobs are admin-level: there is no self-service restore for them.
• Directory and MongoDB jobs share the per-server backup slot with every other job.
• Use a Directory job to back up data that a symlink points at, since symlinks are stored as links and never followed.

MongoDB jobs

A MongoDB job backs up one MongoDB instance. Set it up first, then create the job:

1. Open Settings → MongoDB and configure the connection.
2. Create a job with Source "MongoDB (standalone databases)" and enter the database names in Databases.

Details and limits:

• A MongoDB job is one pseudo-account named mongodb. Each database is dumped on its own with mongodump --archive --gzip and no oplog, so there is no point-in-time across databases.
• TLS is a plain switch (no CA or client certificate). Replica-set and sharded connection strings are not supported.
• install.sh does not install mongodump, mongorestore or mongosh. A helper script, scripts/vendor_mongo_tools.sh, exists but works only on RHEL-family 9 on x86_64.
• A MongoDB job has no self-service restore and is never migrated. It has been checked by unit tests only.

Redis, Microsoft SQL Server and Elasticsearch are not supported.