Skip to content

Latest commit

 

History

History
45 lines (31 loc) · 2.44 KB

File metadata and controls

45 lines (31 loc) · 2.44 KB
copyright
years
2018, 2026
lastupdated 2026-06-05
keywords Block Storage for Classic, Plesk, backups, mountpoint, iSCSI
subcollection BlockStorage

{{site.data.keyword.attribute-definition-list}}

Configuring {{site.data.keyword.blockstorageshort}} for backup with Plesk

{: #PleskBackups}

Configure {{site.data.keyword.blockstorageshort}} for Plesk backups with root or sudo SSH access and full admin-level Plesk permissions. {: shortdesc}

For more information, see Plesk's Documentation for backing up and restoration{: external}. {: tip}

  1. Connect to the host through SSH.

  2. Make sure that a mount point target exists.

    Plesk has two options for storing backups. One option is the internal Plesk storage (backup storage on your Plesk server). The other option is an external FTP storage (backup storage on an 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 {{site.data.keyword.blockstorageshort}} target (/backup/psa/dumps). No FTP user credentials are required. {: note}

  3. Configure your {{site.data.keyword.blockstorageshort}} as described in one of the following tutorials. Mount {{site.data.keyword.blockstorageshort}} to /backup and configure /etc/fstab to enable mounting on start.

  4. Optional: Copy existing backups to the new storage. You can use rsync.

    rsync -avz /var/lib/psa/dumps /backup/psa/dumps

    {: pre}

    This command compresses and transmits your data, and preserves as much as possible, except for hard links. It provides information about what files are being transferred plus a brief summary at the end. {: tip}

  5. Edit /etc/psa/psa.conf to point the DUMP_D value at the new target. It appears as: DUMP_D /backup/psa/dumps.

  6. Optional: As dictated by your particular use case and business needs, remove the old storage from the server and cancel from the account.