Do you mean to say when you edit the network config box, and fill it out with your own network info (adhering to this standard: https://cloudinit.readthedocs.io/en/latest/topics/network-config-format-v1.html) that cloudinit in the vm gives a yaml error? This indicates the way you filled out the entry box is not properly formatted. Keep in mind to pass networking info, your cloudinit install in your template VM needs to be set to use nocloud data sources, and keep in mind the network configuration passed via cloud-init is added to the template VM, not replaced, so you need to properly configure your template VM to not already have adapters configured with IP addresses etc
Yes, you are right infact the old instances are halted and are temporarily kept till I am not sure the imported ones are perfectly working on new node. Unfortunately in the meantime I need a way to manage boths and it means xencenter or cli. Thanks for having pointed my attention to the duplicated uiids problem.
I think the simplest way to just do this once is to go to Settings > Config, there you can export the backup. Once you create your new instance of XOCE, you can import the backup using the same page, then just logout of the default user, and you can login using your old credentials. Make sure to delete the email@example.com account after.
This is a 3rd party container not validated nor endorsed by XO devs. We don't know what's inside, if you have questions on it, ask on the Github repo of the maintainer
Backup reports will answer your initial question/requirement (reports can be sent by email, Slack etc.) There's also a Nagios plugin, or you can use XO API to make request to be support in any software of your infrastructure
Monitoring a Docker container is outside scope of XO, I would suggest to ask Docker community.
Regarding XO and how backup are done, any fresh XOA deployed (or from the sources) will be able to find all the previous backup done by an old XOA, because we store every info on the remote.