Remote backup storage provides a recovery copy outside the web-hosting account. Plesk can use an FTP destination, with FTPS encryption when the destination supports it. FTPS and SFTP are different protocols; an SFTP-only endpoint cannot be entered as though it were an FTPS server.
IN THIS ARTICLE
What you need before you begin
Obtain the remote hostname, account, destination directory and supported connection settings. Use a dedicated backup account with enough quota and limited access. Keep the remote system independent of the hosting account and confirm who manages its retention policy.
01 Save Plesk backups to remote FTP or FTPS storage
- Open the subscription Backup & Restore page, then Remote Storage Settings. Select the FTP or FTP(S) storage option available on the server.
- Enter the server address, remote directory and dedicated credentials. Use the path expected by the remote account, not a browser URL to a file-sharing page.
- Enable encrypted FTPS when supported and choose passive mode if required by the network and destination. Coordinate firewall requirements with the remote provider instead of opening every port indiscriminately.
- Configure any available backup password protection and retain the recovery password securely. Save the settings and read the connection-test result.
- Run a small representative backup to the remote destination. When it succeeds, configure the intended full or scheduled backup and retention settings.
How do I verify the remote backup is recoverable?
Inspect the remote directory independently and confirm a completed archive or complete volume set. Check timestamps and available space. Prove that Plesk can read a backup from the destination as part of a controlled restore test.
Troubleshoot unexpected results
Authentication success with transfer failure often points to directory permissions, quota or passive data connections. A certificate error requires checking the remote hostname and trust chain. Do not solve it by permanently downgrading to an unencrypted connection. Preserve the last valid recovery copy while troubleshooting.