Hi @Damian Andre
I am a tenant to our own Public Cloud which is based on Openstack hypervisor, I dont know the flavor details however I tried below scenarios :
Can you please guide where should I deploy the VSA proxy here, on a windows instance or somewhere else ?
It should just be on a openstack instance (i.e not physical or VMware/HyperV or other hypervisor machine) in the same region of the machines you intend to protect. It sounds like perhaps the flavor of OpenStack may not be supported - once you find out you can check it against the requirements in this list (Feature release 23) to make sure.
Commvault provides support for the following OpenStack distributions:
-
Red Hat OpenStack Platform with the following versions: Train, Stein, Rocky, Queens, Pike, Ocata, Newton, Mitaka, Liberty, Kilo
-
OpenStack Community edition running on CentOS - versions 9, 7, 8, 9, 10, 11, 12
-
Mirantis with the following versions: Kilo, Liberty, Mitaka, Newton, Ocata
-
HPE Helion OpenStack 4.0.1 with the following version: Mitaka
-
Huawei OpenStack Platform with the following versions: FusionCloud V100R002C00SPC600 (FusionCloud 2.06), FusionCloud 6.3.1, FusionCloud 6.5.0 (Huawei Cloud Stack 6.5.0), FusionCloud 6.5.1 (Huawei Cloud Stack 6.5.1)
-
H3C OpenStack Platform with the following version: Mitaka, Pike
-
EasyStack Cloud Service (ECS) OpenStack Platform 5.0.1.2-2 with the following version: Newton
otherwise the vsdiscover or cvd log files on the vsa proxy may give clues as to what is going wrong.