Hi there!

XO just uses the host.address value from XAPI, for all operations (backup which use the XAPI HTTP handler for export but also import, consoles, etc.)

You'll have to find a way to have XAPI telling that host.address is the one you want.

The XAPI doc says:

The address by which this host can be contacted from any other host in the pool

See http://xapi-project.github.io/xen-api/classes/host.html

I'll need to hire 50 lads to release all those ideas/features

Done: https://github.com/vatesfr/xo-web/commit/f9028cb366e6a102a5a0fd54755c7c0163e62a3c

There is maybe a notion of "unexpected finish" for "terminated" word. In French, "Terminé" means "finished". That explains why one of the dev use this word

You should see something in the xo-server output right when you trigger the backup job.

I'm removing the word "Terminated" by "Finished" ASAP.

@dafyre Depends of how do you install it. It's the output of xo-server.

Any log output?

But that's easy:

• XO stands for "Xen Orchestra"
• XOA is "Xen Orchestra virtual Appliance"

As I said on the topic where he's asked:

@olivier said:

For me, it's mainly XO when talking about sources, XOA the appliance. But XOS if you like, it doesn't matter

@johnhooks node stuff.

This number will give you better looking support team, faster response time and a lot more! So remember, dial 0118 999 881 999 119 725...3!

It will be better

Removed, totally replaced by a new one from scratch (from design to framework)

edit: replaced. Not removed for ever ^^ Won't sell XO without a web client ^^

The whole UI is going to be removed, so only broken UI cases are useful

At Vates, we use Shout IRC (self hosted). Pretty easy to use even if you are not used to IRC. And it acts like a bouncer, so you can reconnect from anywhere, it saves your history/connection/discussions.

edit: but mainly for internal discussions and sometimes people asking questions. A forum is needed to have a real community.

Xen is purely LF, but also the toolstack which made XenServer what it is. Eg, XAPI is also a LF project

So +1 from the Scott's comment.

@DustinB3403 If he can't backup itself, there is a problem, and it means you can't backup any other VM. Otherwise, using a file backup of the small DB + config file is pretty easy and useful.

I would say: use XO to backup your VM running XO (whatever using XOA or sources). Inception eh?

About the install itself:

• the main config is inside the redis database (often in /var/lib/redis)
• and the other source of data (mainly jobs etc.) which will become probably the only database in the future, is the leveldb database: probably inside /var/lib/xo-server/data/leveldb.
• the config file of your xo-server is useful too

If you backup those 2 db's + the config file, you can even start a new install of Xen Orchestra, and retrieve everything (configured servers, ACLs, backup jobs etc.)

For me, it's mainly XO when talking about sources, XOA the appliance. But XOS if you like, it doesn't matter

We don't want to stick manually on version for each dependency (there is a lot of them). And what about dependencies of dependencies? That's a HUGE thing to manage manually.