• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Plesk Backup - minimising down time

L

LeaUK

Guest
Hi all

To create a consistent backup I would like to stop all services, however due to the time taken to create backup files this is not feasible as we cannot accept this length of outage.

I note that plesk backup carries out the following process; assuming that I do NOT suspend control panel services but DO suspend domains:

1. Domain access for every domain is sequentially disabled
2. Backup of each domain is performed sequentially
3. Each domain is sequentially restarted.

BUT, this process means that ALL domains are not accessible for the WHOLE backup process! Again, my clients cannot accept this length of outage.


Recommendation:

It would seem that a far better approach and one that strikes a balance between backup outage and backup file consistency would be to suspend the domain for only the time it takes to backup that individual domain. So the process would be:


1. Disable domain access
2. Create backup for domain
3. Restart domain access
4. Increment domain
5 Goto 1.

This would mean minimal domain outage.

Perhaps this can be achieved already somehow?

Lea
 
Thank you for your suggestion. I think, developers will design next BU (backup utilities) according this.
 
Back
Top