FastPanel: backups to our server

Every VPS comes with space on our backup server (the "Backup disk" line of the plan). Copies are kept on a separate server, so they survive if something happens to the VPS.

1. Get the access details in the client area

  1. Log in to the client area and open your VPS service.
  2. In the server card find the "Backup-server: FTP access" block (also the "Backup server" button in the VPS menu).
  3. Copy three values: Server (backup.vps-dns.info), login, password (click "show").
WhatWhere to get it
Serverbackup.vps-dns.info
Protocol / portFTP, 21
Loginlogin from the block (same as the client area login)
Passwordpassword from the block, "show" button
Spaceper plan, "Backup disk" line

The password does not work or the block is missing — contact support and name the VPS. The backup server password will be reset.

2. Create the storage in FastPanel

  1. Left menu: Management → Backup copies. Tab Accounts.
  2. Click New account.
Menu: Management → Backup copies
Menu: Management → Backup copies
Accounts tab and the New account button
Accounts tab and the New account button

Fill in the form:

FieldWhat to enter
Nameukrline-backup — Latin letters, digits, "-", "_", "." only. Cyrillic and brackets are rejected.
TypeFTP
Userlogin from the client area
Passwordpassword from the client area
Emailyour address — an e-mail arrives here if a copy fails
Hostbackup.vps-dns.info
Path/ — the root of your space. The panel creates the plan folder itself.
Port21
The filled form: FTP type, details from the client area
The filled form: FTP type, details from the client area

Click Save. The storage appears in the list.

3. Create a plan

  1. Tab Plans → New plan.
New plan
New plan
FieldWhat to choose
Namedaily — Latin letters. The copy folder is named after the plan.
Accountthe storage from step 2
Backup copies limithow many copies to keep. Old ones are deleted automatically. For daily copies — 7.
Sitestick the sites
Databasestick the databases. It is a separate list — without it only files are copied.
Start timeDaily. The Configure link sets the exact time, e.g. 03:00.
A filled plan: storage, sites, databases
A filled plan: storage, sites, databases
Configure: start time
Configure: start time

Click Save.

How many copies fit: size of sites and databases × number of copies must be below the "Backup disk" space. Example: sites 3 GB, limit 7 → about 21 GB needed.

4. Check the first copy right away

  1. In the plan list click run (the ▶ button). Do not wait for the night.
  2. After a few minutes open the plan copies (list icon).
  3. Check the copy size. A copy of a few kilobytes is an error: files were not copied.
Plan list: run, copies, edit
Plan list: run, copies, edit
Plan copies with date and size
Plan copies with date and size

You can also connect to backup.vps-dns.info via FTP (FileZilla, same login and password) and see the plan folder with <domain>.tar.gz and <database>.sql.gz archives.

5. Restore

  1. Plans → list icon next to the plan → the copy by date.
  2. Click restore and confirm. Site files and the database are overwritten with the copy.
Copy buttons: restore, restore elsewhere, download, link, delete
Copy buttons: restore, restore elsewhere, download, link, delete

Not sure which copy you need — first click "download" or "restore elsewhere" and check the contents.

If a copy is not created

  • An error e-mail goes to the storage Email. Details on the server: /var/log/fastbackup/full.log.
  • Database dump error ("failed to create database dump") — the panel deletes the whole copy. Check that the database user and password work, or remove that database from the plan.
  • A database must belong to the same panel user as the site. Sites of different users — a separate plan for each.
  • The backup space is full — lower "Backup copies limit" or delete old copies.
  • FTP login error — check the login, password, Host and port 21.

Other storages

The Type field also offers: SCP (another server over SSH), S3-compatible, Google, Dropbox, Local (a folder on the same server — does not protect against a server failure).