[XCP] XCP-ng support

[kiu893]

Hello,
I work with Veeam at my company, and we are switching to XCP-NG. Could you send me the binary that supports XCP so we can test it in our lab?

Thank you

[Gostev]

We don't have a public beta for XCP-ng yet but are planning to make it available in a few weeks after addressing a few gaps in the current build.

[zimeon]

Sounds good to have Veeam support XCP-NG!

[evanrac]

Hi team, as Oliver points out in the first post, "Bonus points: if you do the VEEAM integration for XCP-ng API, you will also automatically have it for XenServer, since we use the same API. 2 birds one stone!"

Will XenServer 8 be officially supported then along with XCP-ng for this upcoming integration? We are currently using Veeam agents to do hypervisor agnostic backups on our XenServer cluster, would love to move this to a hypervisor aware backup system if at all possible, when fully released.

Cheers!

[Andreas Neufert]

Hi Evan, this is too early to say.

[datpa]

This are really great news for our team!

We are currently in the process of migrating from VMWare to XCP-ng and are already starting to miss some features of Veeam.

We are really looking forward to switching back to Veeam once the first stable release is available.

[Gostev]

Good news all, public beta of our XCP-ng integration is now available.

We shipped it as a custom Veeam Backup & Replication 12.3.2 ISO specifically to drive people to perform a separate evaluation-only install instead of dropping the plug-in into the existing production Veeam server, as to prevent any possible impact of the pre-release code on your production backups.

You may also notice that the usage reporting is required to be enabled in this beta, which is not something we have ever done before. We're doing this because I really need the beta usage data to gauge the real interest in our XCP-ng integration, and present these numbers to the business to get the approval to move forward with the actual release. There's no telemetry of any kind with the usage reporting, Veeam only gets unique installation ID (GUID) and the number of protected VMs. So we will know the total number of unique beta deployments and the number of VMs protected by each, nothing more.

[Gostev]

Moving this thread to the KVM zoo meanwhile as there's no better place at this time.
I fully understand that XCP-ng is not based on KVM, please don't roast me for doing that.
This is also where PMs have created the beta announcement topic anyway.

@olivierlambert FYI on public beta.

[olivierlambert]

Hello Gostev,

Thanks a lot for the public beta!

No worries for having the thread moved in the KVM zoo



I made an announcement on our social networks, sadly it missed at few hours the XO newsletter, so I expect to get even more traction in few weeks for the XO Halloween release.

[jmannik]

EDIT: Found the issue was my backup repository configuration... weird.

So far ive not had a good run with the new plugin:

Not sure if its an issue with the plugin, or my configuration as im still testing, but so far ive not been able to get a successful backup.
It seems that the helper vm is having trouble with its networking, not sure why yet.

[coolsport00]

I've had success (minus a couple issues...one was on me, the other I've yet to figure out). Look at the log file for the job at:
C:\ProgramData\Veeam\Backup\Plugins\XEN\Backup\<job-name-some-random-string>\<vm-name-some-random-string>.log
I had to look in there to figure out one of my issues (lack of Repo disk space). Would be nice to have more detail in the Job window (will make this known to Veeam). But start there and try and see what the issue may be. Make sure your Workers are on the same subnet as your VBR. Install one on each Host in your Pool. I tested initial BETA & overall was generally successful; Public BETA has been mostly fine..again, minus a couple issues I need to address.
Best.

[coolsport00]

BTW.."officially", Veeam put in the public beta Forums post how you should submit issues you find. See:
kvm-rhv-olvm-pve-schc-f62/veeam-plug-in ... 00399.html
I recommend posting as is recommended.

[jmannik]

Thanks Shane,

Ill post issues I have there that are not self induced lol, as I said in my post edit, turned out my issue was the repository I was trying to back up to was not cooperating with me. No real issue, was only an NFS repository that ive been having issues with previously, and I am planning on rebuilding that storage system soon anyway.

The job is currently running successfully and is processing at around 770MB/S which im very happy with.

[coolsport00]

No problem...& glad to hear you got things sorted Jake. Working through BETAs can be a challenge at times, but also exciting for something to look forward to implementing
Best.

[tsukraw]

Just giving our feedback on this.
We have it running in a couple environments for testing and so far, we have had zero hiccups or issues.
Deployment was flawless and worked without really much fuss or head scratching, all the terminality made sense.
Currently it is around 25VMs being backed up for the last few days without issue over the few deployments.

We are going to add a couple more test environments but overall, this is awesome!
Nice work!

[Gostev]

@tsukraw thank you so much for your interest and time evaluating this!

BTW.."officially", Veeam put in the public beta Forums post how you should submit issues you find. See:
kvm-rhv-olvm-pve-schc-f62/veeam-plug-in ... 00399.html
I recommend posting as is recommended.

People are not seeing this so I'm locking this thread for a few days only while beta is ramping up to make sure everyone gets to see this ask and to direct everyone to post in the right places depending on the type of beta feedback, as putting everything into the single thread is simply unmanageable.

1. If you have a general questions about XCP integration beta such as: how to do something, if certain system configuration is supported, etc. please post it in the official beta thread. This way all general questions are answered in the same place.

2. If you need help with a technical issue, it's best to create a separate, dedicated topic for each issue with [XCPBETA] tag in its name.

3. This thread will remain the place to discuss XCP-ng integration requirements, our roadmap and progress to V1.

[cody.ault]

Hi team, as Oliver points out in the first post, "Bonus points: if you do the VEEAM integration for XCP-ng API, you will also automatically have it for XenServer, since we use the same API. 2 birds one stone!"

Will XenServer 8 be officially supported then along with XCP-ng for this upcoming integration? We are currently using Veeam agents to do hypervisor agnostic backups on our XenServer cluster, would love to move this to a hypervisor aware backup system if at all possible, when fully released.

Cheers!

I tested our beta against XenServer 8.4 in my homelab and was able to take backups. We provided the beta to the XenServer team for testing in their labs, but I'm not aware of internal testing yet on other Xen-based platforms. If you have a test environment, please feel free to give it a try and provide any feedback.

[myRCvmforum]

@Gostev, I don't have a better alternative to the usage reporting thing, but please do keep little shops like us in mind when deciding if XCP-NG support is to continue or not. We don't unfortunately, have resources to do beta testing (hence we can't add to the numbers) but we are interested in using the product should it GA.

Cheering for continued XCP-NG support

[evanrac]

I tested our beta against XenServer 8.4 in my homelab and was able to take backups. We provided the beta to the XenServer team for testing in their labs, but I'm not aware of internal testing yet on other Xen-based platforms. If you have a test environment, please feel free to give it a try and provide any feedback.

Thanks Cody, appreciate the response. We use a clustered server environment with shared GFS2 iSCSI block storage. Many hypervisor backup solutions are not compatible with shared GFS2 storage, so I will see if I can get some time to try the beta myself on our systems and see if it works or not.