AndreyKashin
New Pleskian
- Server operating system version
- Almalinux 9.6
- Plesk version and microupdate number
- Plesk Obsidian 18.0.71 #2
Hello!
We have several Plesk servers with very large amounts of data (from hundreds of GB to 1-1.5 TB).
It is important to us that clients can see and restore data from administrator backups on their own right in the Plesk interface.
Problem:
- It is impractical to store such archives locally in /var/lib/psa/dumps: a full backup of 1-1.5 TB is collected for more than a day, it heavily loads the CPU and MySQL, as a result, the process freezes.
- On other servers with volumes of 250-700 GB, everything works fine.
Questions:
1. Is it possible to use external proprietary storage on a separate VM (for example, BorgBackup + Borgwarehouse) for admin backups so that:
- did customers see them in the Plesk interface,
- and at the same time such backups were not taken into account in the subscription disk space quotas?
2. Are there official or unofficial best practices for organizing big data backups (1+ TB) in Plesk?
Thanks!
We have several Plesk servers with very large amounts of data (from hundreds of GB to 1-1.5 TB).
It is important to us that clients can see and restore data from administrator backups on their own right in the Plesk interface.
Problem:
- It is impractical to store such archives locally in /var/lib/psa/dumps: a full backup of 1-1.5 TB is collected for more than a day, it heavily loads the CPU and MySQL, as a result, the process freezes.
- On other servers with volumes of 250-700 GB, everything works fine.
Questions:
1. Is it possible to use external proprietary storage on a separate VM (for example, BorgBackup + Borgwarehouse) for admin backups so that:
- did customers see them in the Plesk interface,
- and at the same time such backups were not taken into account in the subscription disk space quotas?
2. Are there official or unofficial best practices for organizing big data backups (1+ TB) in Plesk?
Thanks!