Hi There,
We are running on Commvault 11.32.54, Is Commvault supporting Proxmox hypervisor for backup solution.
Is there any other solutions available for Proxmox hypervisor VM’s to cover under Commvault. Please provide me the doc, if available.
Solved
Does Commavult 11.32.54 support Proxmox hypervisor, For backup solution ?
- Novice
Best answer by Alex Deaconu
It seems like Proxmox backups have been available earlier, around 11.28, given this reference I found.
https://documentation.commvault.com/2022e/essential/rest_api_get_virtualization_clients.html
Looking through the newer BOL, the entry seems to be completely removed.
https://documentation.commvault.com/2024e/essential/rest_api_get_virtualization_clients.html
Now the VSInstanceType only goes up to 17, because the support for many of these hypervisors was removed. Notably, Red Hat Open Shift and Docker are completely gone, having been deprecated in Commvault 11.26, and 11.22 respectively.
https://documentation.commvault.com/2024e/expert/deprecation_notices.html
https://documentation.commvault.com/2023e/essential/deprecation_notice_for_docker_virtual_server_agent_vsa.html
https://documentation.commvault.com/2024e/essential/deprecation_notice_for_red_hat_openshift_vsa.html
SCVMM, Alibaba Cloud, Kubernetes, MongoDB Atlas, Proxmox VE, Azure Kubernetes Services and Azure Stack HCI have been taken out of the picture. We highly encourage people to move to Kubernetes, I do not think the removal of these from the Rest API calls is because of support removal in Commvault, but it would most likely be done for a readiness standpoint.
Maybe we did not think some of our products for mass adoption, so their documentation references have been memory holed. Which applies to our Proxmox VE VSA as well.
Slightly off topic, regarding our API, it is funny to see some the number 8 missing from 2024E altogether, which was SCVMM earlier. The number do not mean anything, the value is the string.
I know this is unrelated to the actual question, but it kind of gives an indication that ‘something has to be there’.
There is also our API website, which, guess what, references Proxmox in 11.34. There is hope for PVE.
https://api.commvault.com/docs/SP34/api/cv/OpenAPI3/get-virtual-machines#get-virtual-machines
+24- Community All Star
+4- Vaulter
Onno is correct. There was some initial support added for Proxmox around 11.30, if my mind serves me right, but it was not ready for mass adoption. I am not sure what the status is on support, we could have just as well abandoned the idea. Check with your Account Manager, or with your Sales person, they can follow up internally.
If we still support Proxmox, and you are ok with testing, there might be an option to enable it via a registry key.
+24- Community All Star
I do know that have not abandoned the idea as there has been an increase in demand. I just do not know the current state and if FR36 contains an early access ready implementation.
+4- Vaulter
- Answer
It seems like Proxmox backups have been available earlier, around 11.28, given this reference I found.
https://documentation.commvault.com/2022e/essential/rest_api_get_virtualization_clients.html
Looking through the newer BOL, the entry seems to be completely removed.
https://documentation.commvault.com/2024e/essential/rest_api_get_virtualization_clients.html
Now the VSInstanceType only goes up to 17, because the support for many of these hypervisors was removed. Notably, Red Hat Open Shift and Docker are completely gone, having been deprecated in Commvault 11.26, and 11.22 respectively.
https://documentation.commvault.com/2024e/expert/deprecation_notices.html
https://documentation.commvault.com/2023e/essential/deprecation_notice_for_docker_virtual_server_agent_vsa.html
https://documentation.commvault.com/2024e/essential/deprecation_notice_for_red_hat_openshift_vsa.html
SCVMM, Alibaba Cloud, Kubernetes, MongoDB Atlas, Proxmox VE, Azure Kubernetes Services and Azure Stack HCI have been taken out of the picture. We highly encourage people to move to Kubernetes, I do not think the removal of these from the Rest API calls is because of support removal in Commvault, but it would most likely be done for a readiness standpoint.
Maybe we did not think some of our products for mass adoption, so their documentation references have been memory holed. Which applies to our Proxmox VE VSA as well.
Slightly off topic, regarding our API, it is funny to see some the number 8 missing from 2024E altogether, which was SCVMM earlier. The number do not mean anything, the value is the string.
I know this is unrelated to the actual question, but it kind of gives an indication that ‘something has to be there’.
There is also our API website, which, guess what, references Proxmox in 11.34. There is hope for PVE.
https://api.commvault.com/docs/SP34/api/cv/OpenAPI3/get-virtual-machines#get-virtual-machines
+24- Community All Star
"SCVMM, Alibaba Cloud, Kubernetes, MongoDB Atlas, Proxmox VE, Azure Kubernetes Services and Azure Stack HCI have been taken out of the picture.”
What did you hear about for example Alibaba Cloud and Azure Stack HCI? Both are still present in the latest documentation. So, I'm curious to hear what you know about the future of the support of these platforms.
+4- Vaulter
Azure Stack HCI? Both are still present in the latest documentation. So, I'm curious to hear what you know about the future of the support of these platforms.
I did not hear anything, I am pretty disconnected from these kinds of decisions. All I was talking about was what could be seen in the BOL about API calls. If you check the API website, the entries that are missing in the BOL are clearly still showing in the API, even Docker, despite it being deprecated.
Readiverse Academy Certifications
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.