I have a couple of questions concerning shutdown, stop and vzdump.
Firstly, what is the difference between shutdown and stop, command wise ?
The reason I ask is because when I do a stop on one of my OpenVZs, running Zimbra on 8.04, it fails to startup again unless I reset it a second time. I am presuming that this is caused by the stopping of one of the databases involved making it go into recovery on reboot.
From what I read stop isn't very database friendly:
http://www.ctacat.net/blogs/ctacat/2010/08/28/proxmox-et-larret-des-systemes-virtuels-shutdown-sur-linterface/
Shutdown works fine as does shutting down Zimbra inside the vm before using stop.
This impacts on backup of this vm.
In these forums I've read that both suspend and snapshot aren't particularly database friendly. The whole point of a backup is to preserve data so I'm not happy using either of these, plus they are slower to complete than stop which is important if I have to have Zimbra shutdown while it's happening.
The stop backup option causes the same behaviour as I described with stop above.
Is it possible to use vzdump with shutdown rather than stop ?
Can --stopwait used for this ? I have found very little written on what --stopwait is used for.
It would be much cleaner than using cron to shutdown Zimbra a short while before vzdump --stop.
This must affect other vms containing databases too, not just Zimbra.
Firstly, what is the difference between shutdown and stop, command wise ?
The reason I ask is because when I do a stop on one of my OpenVZs, running Zimbra on 8.04, it fails to startup again unless I reset it a second time. I am presuming that this is caused by the stopping of one of the databases involved making it go into recovery on reboot.
From what I read stop isn't very database friendly:
http://www.ctacat.net/blogs/ctacat/2010/08/28/proxmox-et-larret-des-systemes-virtuels-shutdown-sur-linterface/
Shutdown works fine as does shutting down Zimbra inside the vm before using stop.
This impacts on backup of this vm.
In these forums I've read that both suspend and snapshot aren't particularly database friendly. The whole point of a backup is to preserve data so I'm not happy using either of these, plus they are slower to complete than stop which is important if I have to have Zimbra shutdown while it's happening.
The stop backup option causes the same behaviour as I described with stop above.
Is it possible to use vzdump with shutdown rather than stop ?
Can --stopwait used for this ? I have found very little written on what --stopwait is used for.
It would be much cleaner than using cron to shutdown Zimbra a short while before vzdump --stop.
This must affect other vms containing databases too, not just Zimbra.