# Deploying a Linux Access Node for OpenStack

You can deploy an OpenStack Linux access node using the QCOW2 template provided by Commvault. You can use the Linux access node to perform VM backup, Live Browse and File Recovery operations, with support for ext2, ext3, ext4, XFS, JFS, HFS and HFS Plus file systems (subvolumes). You can also browse VM data from a backup for the source VM.

Note

- As needed, Commvault updates the QCOW2 template to include operating system updates and enhancements. To ensure that the access node contains all features and critical security vulnerability fixes, you must decommission the existing client and deploy the latest Access Node and MediaAgent QCOW2 template. You must also upgrade the CommServe server and Virtual Server Agent to the most recent Commvault service pack or install available HotFixes for the installed service pack.

- You must decommission the existing client only if it was deployed in maintenance release of the respective Commvault service pack, prior to August 2024.

- Starting 11.36 release, the template has the automatic OS updates feature enabled by default, which automatically installs all critical security vulnerability fixes without the need of decommissioning the client.

## Before You Begin

- Before creating the access node for Linux file restores, ensure that the CommServe server and Virtual Server Agent have the latest service pack updates.

- To verify the supported OpenStack software versions, see OpenStack System Requirements.

- Ensure that the OpenStack instance (VM) where you deploy the access node meets the following minimum system requirements:

  - Image File: Select the QCOW2 template.

  - Format: Select QCOW2 - QEMU Emulator.

  - Minimum Disk (GB): Provide at least 80 GB.

  - Minimum RAM (MB): Provide at least 2048 MB RAM.

- The Linux access node supports live browse and restore of NTFS files from a Linux MediaAgent. For more information, see NTFS Live Browse for Restores Using a Linux MediaAgent.

- Live recovery is only supported for recovery from backups using magnetic disk libraries, not from backups to tape libraries.

- Live browse and file recovery operations are not supported for XFS realtime subvolumes.

- The Linux access node supports NFS version 3 for guest file restores.

Note

To perform a live browse of files on RedHat Enterprise Linux or Oracle Linux 9.x VMs, you must deploy Commvault software Feature Release 36 or a corresponding recent version of the Access Node and MediaAgent QCOW2.

## Procedure

1. Go to the Commvault Store on the Cloud Services website and download the OpenStack access node Image with 11.36 n package for the installed service pack (for example, SP36) to a location that is accessible from OpenStack.

2. To deploy a Linux access node in an OpenStack environment, you must first upload the provided access node image to your OpenStack environment. Once uploaded, you can deploy the access node instance using one of two supported methods:

   - OpenStack Metadata Service

   - Configuration Drive (Config Drive)

   Both methods allow you to pass initialization parameters to the instance at boot time, so it automatically configures itself and registers with the Commvault environment.

### Specifying Parameters in a Customization Script

During instance creation from the access node image, you can enter values for all required parameters in the Customization Script field provided in the OpenStack interface:

- Parameters marked as required (Yes) must be defined for successful registration.
- Optional parameters can be customized as needed for your network configuration.

  Parameter | Description | Required
  --- | --- | ---
  `paramIsFBRMA` | Enables Full Backup Restore Media Agent mode. Set to `True` to enable. | Yes
  `paramNetworkGateway` | Hostname or FQDN of the CommServe (CS). | Yes
  `paramAuthCode` | Tenant authentication code for registration. | Yes
  `paramIpRoute` | Default IP route for the NIC (format: `x.x.x.x/prefix`). | No
  `paramTimezone` | Linux timezone name (case-sensitive). | No
  `paramTimeserver` | NTP server FQDN. | No
  `aaUseDHCP` | Specifies whether to use DHCP for network configuration (`True` or `False`). | Yes
  `abIP` | Static IPv4 address for the NIC (required only when DHCP is `False`). | No
  `acNetmask` | Static subnet mask for the NIC (required only when DHCP is `False`). | No
  `adGateway` | Static gateway for the NIC (required only when DHCP is `False`). | No
  `aeDNSSearch` | DNS search prefix. | No
  `afdns1` | Primary DNS server (required only when DHCP is `False`). | No
  `agdns2` | Secondary DNS server (required only when DHCP is `False`). | No
  `baClientName` | Client name (case-sensitive). | Yes
  `bbClientHostname` | Client hostname. | No
  `bcRootPassword` | Root password for the client. | Yes
  `bdClientGroup` | Client group name (case-sensitive). | No
  `beAutomaticOSUpdates` | Enables or disables automatic OS updates (`True` or `False`). | No
  `ccCSUsername` | CommServe username used for registration. | Yes
  `cdCSPassword` | CommServe password used for registration. | Yes

### Using the Metadata Service

1. Enter the customization script.

2. The OpenStack Metadata Service is used to pass these parameter values to the instance after it launches.

3. Inside the instance, the Commvault init client service retrieves these values from the Metadata Service.

4. The Commvault init client service then automatically configures the Commvault software using the provided parameter values.

### Using a Configuration Drive

1. Enter the customization script.

2. You must also select the Configuration Drive checkbox before launching the instance. OpenStack writes the provided parameter values to a configuration drive (ISO) that is attached to the instance at boot time.

3. The Commvault init client service inside the instance reads these values from the configuration drive and automatically configures the Commvault software accordingly.

### Configuring a Linux Access Node in Commvault

You can edit a Linux access node in Commvault by using the following steps:

1. From the Command Center navigation pane, go to Protect > Virtual machines.

   The Overview page appears.

2. On the Hypervisors tab, click the hypervisor.

   The hypervisor page appears.

3. On the Configuration tab, in the Access Nodes tile, click Actions > Edit.

   The Edit access nodes page appears.

4. Select the access nodes that are registered in the OpenStack environment.

5. Click Save.

×

Loading...