Veeam for Xen Orchestra has been release today 13.1

[acebmxer]

Well after getting the Veeam Appliance installed does not support xcp-ng. Veeam Backup and Replication on a windows server does support xcp-ng.

[AtaxyaNetwork]

@acebmxer Looks like xen drivers missing (as usual with appliance...)

Does the Veeam Appliance can be downloaded for free ? I would like to take a look at it
I found the community version (but it looks like the one running on windows), but didn't found the appliance based on rocky

[AtaxyaNetwork]

(Edit, found the iso once i created a account, i'm taking a look)

[AtaxyaNetwork]

@acebmxer Looks like it worked on my side

4VCPU 8G RAM 2x256G of disk

(the default choice is reinstall, not install, did you "force" select install ?)

[MajorP93]

@acebmxer Hello, thanks for sharing this here!

Me and my team have been waiting for this release!

I signed up for the Veeam newsletter hoping I would get notified once Veeam 13.1 (an XCP-ng plugin) gets released but they seem to be a bit slow.

So I found out about this release due to your post.

Will start testing!

[acebmxer]

Yeah I was succuesfull getting the appliance to install but did not see any xen or xcp-ng support. On the Windows version of B&R Xen or xcp-ng is support and backups worked. Just sucks to eat up MS license for it.

Also the Appliance does not seem to support other storage repos aside from local, where the Windows version you can setup smb, nfs, etc... Also the Xcp-ng plug in itself is windows exe file. So unless the plugin can be deployed to the appliance via a windows system.

[MajorP93]

This post is deleted!

[poddingue]

Nested RDP eating the arrow keys is not something I'd have guessed, and @AtaxyaNetwork's post probably explains why I went the wrong way too.
If the default selection is reinstall rather than install, that fits your log better than my disk-naming guess did, since the thing that aborted was ReinstallLayoutGenerator looking for an existing SYSTEM volume a fresh disk wouldn't have.
So the LVM error was probably the installer doing the right thing in the wrong mode, and my xvda theory was, at best, misleading.
I'm less sure about the other part, that the appliance doesn't support XCP-ng while B&R on Windows does, since AtaxyaNetwork seems to have the appliance running.
Where did that one come from, the Veeam docs or your support case?

Worth pinning down before it gets repeated.

[acebmxer]

@poddingue

Nothing reported yes since i was able to get the installer working, still in testing mode. I believe in beta only worked in B&R on windows but not in the appliance. I thought i read that support would come to the appliance in 13.1 that is why i was supporised when i did not see the option for it once it got it installed.

If i overlooked something in the appliance please share the details.

[acebmxer]

So when i try to run the installer for just he plugin on a fresh windows server it prompt that b&r 13.1 needs to be installed. On fresh install of 13.1 the plugin is include. My guess if someone is upgraded from previous version the plug would not get installed by default? When i run the plug installer with B&R 13.1 fresh install it prompts to uninstall the plugin.

[acebmxer]

Ok with the veeam Appliance you can use a windows vm or pc with the veeam console and you can connect the applaince to add nfs share for backup repo and connect to XCP-NG.

So two working cofigs...

1. Windows VM with B&R
2. Veeam Appliance + Windows Client for console access

When i upgraded the current veeam client to the latest client it also installed the xcp-ng plugin.