Well.... yes...
I was copying it, but I was also dropping a copy in the /etc/xo-server/config.toml directory as well....apparently i was trying to get ahead of the game.
As soon as I removed the /etc/xo-server/config.toml path and sample.config.toml file, everything loaded. 
@olivierlambert said in XO and XCP-ng pricing:
if you’re working with a nonprofit, I’d really recommend reaching out to our sales team directly.
--- K-12 education as well?? 
Small school districts are getting beat up by Broadcom too. Most small districts would easily fall at or under the 3/4 host limit.
Lovin' this.... thank you for picking it up. Great tool to have.
I have 2 other standalone XCP hosts...that do not exhibit the same symptoms.
Both are running older versions of XO.
The oldest has zero cleanup problems at all.
It's running commit 902f0
the 2nd is running commit 992d6 and seems to leave some snapshots behind.... but doesn't exhibit the VDI issue.
commit 290f5 looks like it may be the issue.
Never mind.... seems to have been something "stuck".
As soon as I deleted a couple of the VDI's..... everything took off and cleaned it self up.
I don't know if this is related to the "Snapshots not being removed after successful backup" issue that I posted a couple weeks ago.... but it seems like maybe it is.
I seem to be getting a bunch of "Unhealthy VDI's" ...and they are using up my storage space...
Any safe easy way to clean these all out ???
I can remove the leftover snapshots without issue....but I'm unsure how to proceed with cleaning up these VDI's ???
Hi All,
On 2 of my hosts (all are up to date on patches) my backup snapshots seem to hanging around.
ie: not being deleted / removed after successful backup.
On my 3rd host... everything seems to be working normally (?)
"In any case, XO is able to restore anything from the BR (backup repo or "remote") even on a completely brand new hosts with a complete different hardware, it's fully self contained and agnostic."
--- Understood. Thank you!
I was under the assumption that there may be issues with the XCP-NG host / backups etc... when UUID's are changed ? (recovering a lost host ) Or even restoring the XO config may be
not quite as easy as maybe it should be.... restoring a downed host
I understand that the referenced post (above) is a few years old....and that maybe things have changed regarding the procedure.
In my mind .... having an image available (during a high stress situation) that is already setup and ready to go seems like a good idea. 
But I also see the beauty of being able to restore the XCP-NG host and config back to a system that may be installed on completely different hardware. That is pretty awesome.
Maybe I'll try a dry run in a lab situation to see which one feels better.
Thank you again for your time and consideration.
