Configuring File Storage for Classic for backup with Plesk

You can use these instructions to configure IBM Cloud® File Storage for Classic for your backups in Plesk. The assumption is that root or sudo SSH and full admin level Plesk access are available.

For more information, see Plesk's Documentation for Storing Backups and Website Files on a Remote Server by using NFS.

Connect to the host through SSH.
Ensure that a mount point target exists.

Plesk has two options for storing backups. One is the internal Plesk storage, which is storage on your Plesk server. The other is external FTP storage, which is storage on some external server in the web or your local network. Commonly on Plesk boxes, internal backups are stored in /var/lib/psa/dumps and use /tmp as a temporary directory. In this example, the temporary directory is kept local, but the dumps directory is moved to the File Storage for Classic target (/backup/psa/dumps). No FTP user credentials are required.
Configure your File Storage for Classic as described in one of the following topics:
Mount the volume to /backup and configure it in the file system table (/etc/fstab) to enable mounting on start.

By default, NFS downgrades any files that were created with the root permissions to the nobody user. To allow root clients to retain the root permissions on the NFS share, no_root_squash needs to be added to /etc/exports.
Optional. Copy existing backups to the new storage. Use rsync for example:
```
rsync -avz /var/lib/psa/dumps /backup/psa/dumps
```
This command compresses and transmits your data, and it preserves as much as possible, except hard links. It also provides information about what files are being transferred plus a brief summary at the end.
Edit /etc/psa/psa.conf to point the DUMP_D value at the new target. It appears as: DUMP_D /backup/psa/dumps.
Optional. As dictated by your particular use case and business needs, remove the old storage from the server and cancel it from the account.