@coliver Grenoble, France. We found a small team of investors that "helped us" last year, but that's really small amounts of money. But despite that, our growth is not bad, and we continue to focus on great features coming soon!

@Dashrender It's not! The SR is just here to store a snapshot to make the delta.

But the files are NOT STORED inside any XenServer, but on an external storage (XOA itself or a NFS share). And you can restore the backup even if you lost your whole XenServer infrastructure.

@DustinB3403 Even classical backup: for a running VM we need to export the snapshot. So if all your VMs are running and you are backuping everything at once, you'll need to double your space usage (at least during the VM export process).

That's why it's important to use thin provisioned storage as possible.

By the way, you can spot the difference with a thin provisioned SR, like NFS in this case:

Far better...

And now you discover why we release appliance with an updater and validated updates

Lodash team made a release 6 hours ago, and it broke everything. We are working on a way to avoid that, or reported this to them.

This stuff is sadly not very uncommon.

The lodash specific stuff won't be necessary after the 4.12

@johnhooks We'll re-create it for multiple reasons:

• we stacked a lot of features inside something not planned for that
• so from a dev point of view, the code is messy
• from a user point of view, it's not really coherent everywhere
• we got perf issues for big infrastructure (1500+ VMs)

Thanks to our experience now, we can rebuild it from scratch with a LOT more in mind. It allows:

• a nice refactoring from the dev point of view
• using React+Flux for a fully component oriented software
• thinking "components" is far far better for dev but also for building generic and powerful UIs
• display only what's important

An example for the VM view:

And with a legend:

Be advised, that's a draft; we already made some changes since.

Lodash thing should be fixed everywhere

Only warnings, go ahead.

Please keep in mind we are talking here about someone:

• being on the beta branch to test a feature before the official release
• on a source install
• without the updater inside XOA
• without pro support

If you got the appliance, nothing to do. Just click on "upgrade" when it's out. So it can compete, but yes, it's not free

edit: I have no problem to be compared in terms of pricing even between VEAAM and XOA.

edit2: being turnkey is the base of our business model

So you'll have 24 files per VM disk: 1 full vhd and 23 delta. Each new backup will:

• create a new delta vhd file
• merge the oldest delta vhd in the full
• remove this oldest delta

You will be able to restore any of those 24 last backup.

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.

It will be better

But that's easy:

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

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

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

https://github.com/vatesfr/xo-server/pull/232/files

Hi,

This is not a XO limitation, but a XenServer/XAPI limitation. I heard Citrix is working on it to improve it.

Figure 1: me actually lurking in this thread

Our "special" VM copy is doing this:

Check the "Copy" button in the VM view, select a destination SR, and you are done.

edit: original blog post: https://xen-orchestra.com/blog/vm-streaming-export-in-xenserver/