Commvault supports protection of the following distributions and releases:
-
Red Hat OpenStack Platform with the following actively supported versions:
-
Red Hat OpenStack Platform 17
-
Red Hat OpenStack Platform 17 (Wallaby)
-
Red Hat OpenStack Platform 16.2, 16.1 (Train)
-
Red Hat OpenStack Platform 15 (Stein)
-
-
Mirantis Cloud Platform (MCP) with the following active releases:
-
MCP with Ocata
-
MCP with 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)
-
Huawei Cloud Stack 8.1.x, 8.2.x
Note
For the Huawei Cloud Stack, an OpenStack user must have the necessary permissions to successfully perform data protection tasks.
-
For more information about data protection see Multi-Tenant Deployments.
-
For information about Openstack permissions, refer to Assigning Minimum Openstack Non-Admin User Permissions for Commvault.
The following conditions apply:
-
The account used for backup and restore must be a Tenant VDC Administrator; an HCS Operation Administrator account cannot be used for backup recovery.
-
The Tenant VDC Administrator must have full administrative rights within the tenant.
-
The VMs to be backed up and the VSA Proxy must reside within the same tenant.
-
For Huawei OpenStack Platforms with any version of FusionCloud, you must configure the bEnableFusionCloud and sCinderV1EndpointUrl additional settings to execute restores. For more information, see Restores for OpenStack.
-
-
When setting up a virtualization client, use the public endpoint of the Keystone URL if multiple endpoints are available.
If you are creating Cinder volumes on a storage array, ensure you acquire the necessary licenses, such as Storage Snapshot and LUN Copy.
Commvault software no longer supports inactive OpenStack releases. To protect these versions, you will need to use a previous release of Commvault software.
For information on which versions of the Red Hat OpenStack Container Platform are active or inactive, see Red Hat OpenStack Platform Life Cycle.
-
Red Hat OpenStack Platform 14 (Rocky)
-
Red Hat OpenStack Platform 13 (Queens)
-
Red Hat OpenStack Platform 12 (Pike)
-
Red Hat OpenStack Platform 11 (Ocata)
-
Red Hat OpenStack Platform 10 (Newton)
-
Red Hat OpenStack Platform 9 (Mitaka)
-
Red Hat OpenStack Platform 8 (Liberty)
-
Red Hat OpenStack Platform 7 (Kilo)
-
OpenStack Community edition running on CentOS versions: 8, 7, 6, 5, 4, 3
-
Mirantis MCP with Newton
-
Mirantis MCP with Liberty
-
Mirantis MCP with Kilo
-
HPE Helion OpenStack 4.0.1 with the following version: Mitaka
-
Huawei Cloud Stack 6.3.1 (FusionCloud 6.3.1)
-
Huawei FusionCloud V100R002C00SPC600 (FusionCloud 2.06)
-
H3C Cloud OS 4.0 (Mitake)
-
H3C Cloud OS 3.0 (Pike)
EasyStack Cloud Service (ECS) OpenStack Platform 5.0.1.2-2 (Newton)
Virtual Server Agent (Proxy) Requirements
The Virtual Server Agent can be deployed on a Windows or Linux instance in the OpenStack environment.
Only instances that have the VSA installed can act as VSA proxies to perform backups and restores.
At least one proxy is needed for each region. You can deploy additional VSA proxies as needed for load balancing.
The following operating systems are supported for VSA proxies:
-
Oracle Linux 8.x
-
Microsoft Windows Server 2022
-
Microsoft Windows Server 2019
-
Microsoft Windows Server 2016
Note
Microsoft ended mainstream support for all versions of Windows Server 2012 and Windows Server 2012 R2—including Hyper-V Server 2012 and Hyper-V Server 2012 R2, and Core Editions—on October 10, 2023.
-
CentOS 7
-
RHEL 7.2, 7.3, 7.4, 7.5, 8
For Linux proxies, disable automatic activation of volumes to avoid issues with HotAdd operations during backup and recovery. For more information, see Disabling Automatic Activation of Volumes for a Linux Proxy.
Note
:
-
Linux proxies must have the psmisc and lvm2 packages installed.
-
Linux proxy instances must have the dmidecode package installed.
Note
Microsoft ended mainstream support for all versions of Windows Server 2012 and Windows Server 2012 R2—including Hyper-V Server 2012 and Hyper-V Server 2012 R2, and Core Editions—on October 10, 2023.
The Virtual Server Agent should be installed on instances that meet the following requirements:
-
Minimum of 100 GB disk space recommended
-
Minimum of 4 GB RAM required beyond the requirements of the operating system and running applications
For Windows proxies, VirtIO version 62.73.104.11800 is supported as a driver for OpenStack backup and restore operations.
MediaAgent Requirements
The following packages must be installed on MediaAgents that are used for guest file browse and restore operations on Glance images:
-
QEMU disk image utility (qemu-img)
-
libguestfs
-
libguestfs-tools
-
Logical Volume Management (lvm)
Port Requirements
-
The security group associated with the proxy instance should permit all incoming and outgoing TCP traffic.
-
If unrestricted access cannot be set up, configure a one-way Commvault firewall between the CommServe host or MediaAgent and the VSA proxy instance. With this firewall configuration, you can restrict communication to a single TCP port (typically port 8400).
-
When using the RHEL-OP distribution or in any OpenStack environment that includes a firewall, ensure that CVD port 8400 is configured to accept incoming traffic from Commvault.
Hardware Specifications
For information about hardware requirements for the Virtual Server Agent, see Hardware Specifications for Virtual Server Agent.
DISCLAIMER
Certain third-party software and service releases (together, "Releases") may not be supported by Commvault. You are solely responsible for ensuring Commvault’s products and services are compatible with any such Releases.