Hi @CGI
Thanks for the question!
You are correct, XCP-ng is not currently supported, so let me follow up your request internally with our Development teams to see what plans there are or if anything is already on the roadmap for XCP-ng.
Thanks,
Stuart
Hi @CGI
Here is the list of supported versions for Xen Server:
https://documentation.commvault.com/11.23/expert/3302_system_requirements_for_virtual_server_agent_with_citrix_hypervisor_xenserver.html
The team here have informed me that unfortunately, there are no plans currently to support open source XCP-ng.
However, if you have a specific project and would like to discuss supportability, please reach out to your account representative to discuss options.
Thanks,
Stuart
Hi Stuart!
I’m sad Commvault doesn’t plan that. I’ll follow your advice, but in the end it probably means: I either stick with Citrix or have to replace our Commvault environment. Not what I hoped for, but what I expected.
Regars
- Christof
@CGI , I’ll reach out to your Account Rep on your behalf so you can see what options you have.
He probably still needs to find out. ;)
Have you heard from them yet? I didn’t see an update, but they may have reached out by phone.
I’ll follow up on my side as well 
I got an E-Mail today, will give him a call and find out “what’s in”.
(Seems he’s busy right now, will try later or tomorrow again)
Thanks!
Appreciate the reply here (and to my e-mail) @CGI !!
I’ll keep an eye out for an update.
So sadly there is currently no real option. I either have to stay with Citrix or replace our Commvault environment.
Only current option would be: Install an agent into every VM and for that. Absolutely no realistic option.
Finding out if more (possible) customers do want XCP-ng support und by thus giving it enough priority, seems the only way to get it working.
I already tried to just connect it, but it failed telling me the version is not supported. It obviously checks the Hypervisor version through XAPI.
It’s especially sad, as XCP-ng and XS/CH are based on the same XAPI, which means:
What’s working on XS/CH should also working on XCP-ng without any changes.
I’m not happy with Citrix and their roadmap. Will see how to fix that, when I get the time.
Appreciate the full load of details, @CGI . Definitely wish there was an easier path.
Sadly I didn’t get a poke from your reply, but I’ve also accidently noticed the added support. I doubt it was much work, as it’s 100 % API compatible (yet).
I’ve prepared a test environment and: It indeed works, I successcully connected, found VMs, backed them up and restored them. Neat: Citrix Vendor Lock-in removed and a fully OSS project supported. Will most likely make use out of it and migrate.
Edit: I can’t change your post to “the answer”, which ould be neat, if someone stumbles over this.
Update: I migrated our Citrix Hypervisor/XenServer (Namechaos) pool to XCP-ng.
No problems at all, nothing to touch - it just continues to backup our VMs.
(Also: Migration means: mount media, “upgrade”, done)