> Expert > Backup and Restore Agents > Virtualization > Virtual Server Agent > OpenStack > Deployment for OpenStack

System Requirements for Virtual Server Agent with OpenStack

Commvault supports protection for many OpenStack distributions.

  • Red Hat OpenStack Platform with the following versions:

    • Wallaby: Red Hat OpenStack Platform 17

    • Train: Red Hat OpenStack Platform 16

    • Stein: Red Hat OpenStack Platform 15

    • Rocky: Red Hat OpenStack Platform 14

    • Queens: Red Hat OpenStack Platform 13

    • Pike: Red Hat OpenStack Platform 12

    • Ocata: Red Hat OpenStack Platform 11

    • Newton: Red Hat OpenStack Platform 10

    • Mitaka: Red Hat OpenStack Platform 9

    • Liberty > Red Hat OpenStack Platform 8

    • Kilo > Red Hat OpenStack Platform 7

  • OpenStack Community edition running on CentOS versions: 8, 7, 6, 5, 4, 3

  • Mirantis with the following versions: Ocata, Newton, Mitaka, Liberty, Kilo

  • 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), Huawei Cloud Stack 8.1.x.

    Note

    For Huawei Cloud Stack 8.1.x, a backup is certified only for instances created from images.

  • H3C OpenStack Platform with the following version: Pike, Mitaka

  • EasyStack Cloud Service (ECS) OpenStack Platform 5.0.1.2-2 with the following version: Newton

When creating a virtualization client, if there are multiple endpoints for the keystone URL, use the keystone URL for the public endpoint.

If cinder volumes are created on a storage array, you must obtain the corresponding licenses (for example, Storage Snapshot and LUN copy).

Note

For Huawei OpenStack Platforms with any version of FusionCloud, you must configure the bEnableFusionCloud additional setting to execute restores. For more information, see Restores for OpenStack.

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

  • Microsoft Windows Server 2012 R2

  • CentOS 7, 8

  • RHEL 7.2, 7.3, 7.4, 7.5, 8

    Note

    For CentOS 8, Oracle Linux (OL8.x), or RHEL 8 instances, to install operating system packages that must enable automatic installation of Mono, register the instances with CentOS, Oracle, or Red Hat.

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.

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.

Loading...