Set up remote backups to FTP, SFTP or S3

Before you start#

A backup on the same disk as the server does not help when the disk fails, the server is lost or ransomware encrypts it. StackRegent's Backup Manager can store backups on:

• an FTP server, preferably with FTPS,
• an SFTP server over SSH, with the host key pinned after the first connection,
• S3-compatible storage: Amazon S3 or another provider such as Wasabi or MinIO.

Create a folder or bucket and a user that can write to it before you start. A user that can only write to that one folder or bucket is best. This article sets up storage for the whole server; customers and resellers can have their own, described at the end.

Step 1: Open Remote Storage#

Go to Tools & Settings › Backup Manager and click Remote Storage.

Step 2: Enter the storage details#

Choose the Storage:

• FTP server: Server and port (21), User name, Password and Folder, which is created if missing. Keep Use FTPS (explicit TLS); recommended ticked.
• SFTP server (SSH): the same fields with port 22. After the first connection the panel shows the server's Host key and from then on connects only while the server presents that key.
• S3-compatible storage: Endpoint (empty for Amazon S3, or the provider's address such as https://s3.eu-central-1.wasabisys.com), Region, Bucket, Access key ID, Secret access key and Folder. Tick Path-style addresses for MinIO and some other providers.

Tick Keep a copy on this server when a backup is stored remotely only if you also want a local copy for quick restores.

Step 3: Test and save#

Click Test and Save. The panel tests the connection before it saves anything; if the test fails, the message says why, usually a wrong folder, a firewall blocking the passive FTP range or a bucket in another region.

Step 4: Schedule the backups#

In the Backup Manager, click Schedule and tick Back up on a schedule. Under When, choose Every day and an hour when the server is quiet. Choose the Content (configuration is always included; add website files, databases and mail messages) and set Store on to Remote storage or This server and remote storage.

Step 5: Set retention and protection#

Set Keep to the number of scheduled backups to keep; older ones are removed, and 0 keeps all. Under protection, choose Protect with a password and enter a backup password of at least 8 characters. Click Save.

The password matters: without it, passwords inside the backup are sealed with this server's Windows key and the backup can be restored only on this server. With it, the backup can be restored on a new server after a total loss. The password is not saved in readable form anywhere, so keep it in your password manager, not on the server.

Step 6: Check the first run and test a restore#

The next morning, the backup list shows the scheduled backup with its size and where it is stored, and the Last server backup widget on Home shows it too. Once, test a restore: click Restore, pick one subscription and one content type, enter the backup password and follow the task. Restores pick subscriptions and content types (website files, databases, mail), not single files.

Backups for customers and resellers#

A customer's or a subscription's own Backup Manager has Own Remote Storage with the same fields, so customers can send their backups to storage they control. On new service plans, the permissions for backups to the server storage and to remote storage start off; tick them on the plan's Permissions tab if customers should use them.

The backups chapter covers restoring, downloading, transfer links and Plesk backups.