Becouse xoa backup is painfully slow... it's good for CR but for full vm backup, let's say it's unsuitable... on my 1Gb lan, full vm backup (DR or Copy) from xcp1 to xcp2 I have about 10-15Mb/s. This is the topic I've asked many times on this forum. And guys from vProtect brag that the speed im much better on their soft due to CBT not vhd delta - which I'll check in a while.
It'a an important to know exact time of vm and snapshot - eg when recovering for an example a Active Directory or sql database. When doing so, someone can believe that restores the data from {the time visible in name}, because can be unaware of possible offset of zulu time.
You already have the exact time π If you aren't aware of an ISO standard format date, it's another story. But this is really standard and universal way.
I suppose you meant "misinterpreting the snapshot time" which has NOT the same meaning than "incorrect time".
Automatically deleting incomplete VMs can be dangerous
This is an example - don't take it too strictly. I'm talking about exaclty the above problem. I was not aware of it. No information about the problem and this is the exactly the real problem.
Hi @akurzawa, this would be quite a big feature, please open an issue if you have something precise in mind (a list of possible actions, what could trigger a workflow, ideally some use cases that couldn't be done without it, etc.). Also, a lot can probably already be done with XO's Web Hooks, xo-cli and a third party workflow tool in between.
I can put the script everywhere - but I want to avoid non standard config. In case of failure of {system} I'm reinstalling it, and restoring config from file. I don't need to remember that I've put some fancy staff somewhere on the lan.