Build should be back on track on next-release branch.

@DustinB3403 said:

@olivier how well does XO work with APC Powerchute?

Because, that is my next goal. Get my VM's and Hosts to gracefully shutdown during a power-outage.

I strongly encourage people using it to contribute. You got 3 solutions:

• using xo-cli (from anywhere) to send basic orders to xo-server
• make a script using xo-lib if you want to make more advanced stuff
• write a xo-server plugin to manage that. But I don't know the APC product possibilities neither its API/callback capabilities.

Should be out tomorrow if we got no QA surprise in the release process: https://xen-orchestra.com/blog/continuous-delta-backup/

/teasing:

edit: blog post is out: https://xen-orchestra.com/blog/xenserver-vm-continuous-replication/

Currently in QA.

We'll have indeed more sources coming (and better graphs) in the 5.x branch. There is a lot of sources available, so again, the thing will be to display main graph and allow extra stuff if needed.

Using XO VM replication between 2 XS 7 hosts, initial copy of a 61GB VM in 8 minutes:

This is on a classic GB link.

Clearly, previous bottlenecks weren't in XO.

Hi guys, if there is any VEEAM users (or other popular VM backup products), I'll be happy to have feedback for improving our current VM backup workflow.

See https://github.com/vatesfr/xo-web/issues/999

I mean, it terms of UI, having something easier to understand and manage.

This is plain Xen + their own home-made "secret" toolstack (built year after year).

They also implement features on their side, sometimes valuable stuff, sadly it seems there is a lack of sharing. And because Xen is GPL and not aGPL, they are not forced to give it back.

Sometimes, you see Xen people developing a feature which is already working in Amazon. That's a bit sad when you have to do things twice, but you know, big corps...

The "base" of this new xo-web is cleaner and well technically designed (main goal of 5.0). So, in theory, 5.1 will be mainly about UI improvements per se.

I prefer to release now than waiting 1 more month to have something "better"

Should be better because:

• No split brain possible
• No modification in XS host (so no problem to upgrade XS hosts)
• Scalable

Cons:

• losing a bit of RAM and storage
• some extra layers, but in a 2 hosts situations I don't think it's a big deal

Extra layers are necessary so far until XenServer SmapiV3

I still have 27 days to stay in track

Just a new blog post talking about Erasure Code solution for XOSAN: https://xen-orchestra.com/blog/xenserver-hyperconverged-with-xosan/

AKA a great solution to mix security, space available and scalability

Just bought 10GB network stuff to dig on perfs.

# python -V
Python 2.7.5

On XenServer 7.1

Hi there!

Long story short:

• creator of Xen Orchestra project
• doing some talks sometimes (LinuxCon US, FOSDEM...)
• Open source lover (Xen, Linux, BSD)
• Web and NodeJS advocate

If you want a longer version of the story, feel free to ask!

@johnhooks We got some delay on the SMB feature, but it will be out for the 4.12

Anyway, the blog post about the 4.11: https://xen-orchestra.com/blog/xen-orchestra-4-11/

Hi!

Thanks for the hint, will do

Guys,

You should ping me or create GitHub issues when you have concerns, bug report or questions about XO

For the restore without knowing what's happening: I just updated this yesterday, now the VM is named "[Importing...] VMname" until the restore is completed. See https://github.com/vatesfr/xo-web/issues/641

Already closed, so out for 4.12 around Jan 15

About "Forever forward incremental backup", allowing you to avoid any full export after the initial one, it consists of:

• merging offline (ie: without Xen, by ourselves) the original full backup with its contiguous snaphot
• doing step each time, step by step

So you never need to re-export the full stuff after the first time. A good illustration here, from VEEAM:

This should be out in 4.13 (end of Jan.), 4.12 with some luck.

XOA Free is a quick way to test the product (and we even have users totally happy about it, and using it everyday for basic tasks).

We got a trial, which is relatively easy to access (about 100 new trial users per month), so it serves the purpose to make people discover without having to pay anything.

Sincerely, if a company can't afford a "Starter" plan for using a basic backup solution (without limitations!), they won't be become a paid customer anytime.

The only way to please (almost) everyone, is to have something which seems totally free, like Facebook or Google, even if it's not in reality. But this strategy can only work on huge volumes and not in our niche market.

@Dashrender It's not exactly like that on a thick storage. It's a little bit more complicated in fact.

It depends of the current disk content. XenServer will try to deflate as possible. Let's take for example, only one VDI with the total size of the disk space provisioned (let's say on a LVMoiSCSI):

Then, if you do a snapshot, you'll have 3 disks:

• the original one will become the parent
• the new created active VDI will be remapped to be current VM disk
• the snapshot

Doubling size is the worst case, when deflate won't free some space (or very little). In this case, the initial snapshot mechanism will double the space used.

But any extra snapshot (after the initial one) won't consume a lot of space.

Also check this article: we got a feature which should be very interesting in your case @DustinB3403 : https://xen-orchestra.com/blog/xenserver-emergency-shutdown/