• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Using "--nostop-domain" with psadump - will databases be corrupted?

T

Theovis

Guest
I'd like to use --nostop-domain with my psadump, since there's no risk of Plesk users logging in while the process is being run.

Can the mySQL databases be corrupted during this process (in the dump file, that is), or does psadump do a good "snapshot" of the database during the backup process?
 
Its better to just let PSAdump stop it when it dumps. It only takes mysql down for a few seconds on my servers. I don't see the point in doing a -nostop since apache is stopped while the sites are dumped so everything is unreachable anyway..
 
Apache isn't stopped if you use --nostop and --nostop-domain. If you're concerned you may like to use just --nostop but not --nostop-domain as that will disable that particular domain when it gets to it so there should be no MySQL queries.
 
Back
Top