"STOP" Backup

[Serpensin]

Today I created a full 'STOP' backup with Proxmox for the first time. I noticed the following:

I have a ct with Plesk and a ct with my DBs. These are set so that logically the db starts first and shuts down last. However, during a "STOP" backup, it happened to me that Plesk was running while the DB was still off, which can lead to problems because my services depend on the DB but cannot reach it.
Is there a way to force the cts to wait for one backup to be completed so that the two cts can be properly booted up again?

 

[Zaman]

maybe your backup is stuck
vzdump --stop
for more see
https://forum.proxmox.com/threads/proxmox-backup-wont-stop.23219/post-356084

 

[fiona]

Hi,

Today I created a full 'STOP' backup with Proxmox for the first time. I noticed the following:

I have a ct with Plesk and a ct with my DBs. These are set so that logically the db starts first and shuts down last. However, during a "STOP" backup, it happened to me that Plesk was running while the DB was still off, which can lead to problems because my services depend on the DB but cannot reach it.
Is there a way to force the cts to wait for one backup to be completed so that the two cts can be properly booted up again?

not sure if you still have the issue, so mostly commenting for future users: what you could do is use a hook script for the backup job, stop both containers in the job-init or job-start phase and turn them back on in the job-end and job-abort phases. An example hook script can be found in /usr/share/doc/pve-manager/examples/vzdump-hook-script.pl.