> Essential > Virtualization > VMware > Implementation Planning

Deploying a Linux Access Node for VMware

You can add a VMware Linux access node to perform VM backup, live browse and file recovery operations and browse virtual machine data from a backup for the source virtual machine (VM). Commvault uses its open virtual appliance (OVA) template to create the Linux access node with support for ext2, ext3, ext4, XFS, JFS, HFS, HFS Plus, and Btrfs file systems.

Note

  • As needed, Commvault updates the OVA 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 OVA 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 CU10 maintenance 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

For offline CommCell environments, to deploy a new Linux access node for VMware, you must download the VMware image file (.OVA) and save it to a location on the access node. For instructions, see Configuring Deployment of the VMware Image in an Offline CommCell Environment.

Procedure

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

    The Overview page appears.

  2. On the Hypervisors tab, click the hypervisor.

    The hypervisor page appears.

  3. On the Configuration tab, you can do the following:

    • To add an access node, in the Access nodes tile, click Actions > Deploy New Linux Access Node.

    • To add a preferred node for guest file restores, in the Options tile, beside Preferred node for guest file restores, click the Edit button edit button outline grey/gray pencil. In the Edit file recovery window, click Deploy New Linux Node.

    The VM Name and Location page of the Deploy Linux Access Node wizard appears.

  4. Enter a name for the virtual machine (for example, VM_LinuxAccessNode), select a location, and then click Next.

    The Compute Resource page appears.

  5. Select the destination compute resource for this operation, and then click Next.

    The Storage and Network page appears.

  6. Configure the following:

    • Destination network: From the list, select the network on the destination site.

    • Virtual disk format: From the list, select the appropriate format for the virtual disk:

      • Thick provision eager zeroed

      • Thick provision lazy zeroed

      • Thin provision

    • Storage for the configuration and disk files: From the list, select the datastore.

  7. Click Next.

    The Customize Template page appears.

  8. Configure the client:

    • Client name: Short name for the virtual machine (for example, VM_LinuxAccessNode).

    • Host name: Host name or IP address for the client.

    • New password for "root": Password for the root user of the virtual machine.

    • Select server group: Select the server group; the Linux access node is assigned to this group if the group exists (or after it is created).

      When you configure the access node, the firewall settings are automatically inherited from the associated server group.

  9. Configure the IP:

    The following fields need to be entered when the Linux access node is being deployed using a static IP address, or with DHCP if there is a possibility that the DHCP server in your environment provides incorrect or incomplete DNS information. The fields below override any DNS configuration that is obtained from the DHCP servers.

    • Use DHCP: Select this option or enter values for the Static IP Address, Netmask, and Gateway.

    • DNS Search Suffix: Identifiers for domains to be supported.

    • Nameserver 1: IP address for the primary name server.

    • Nameserver 2: IP address for the secondary name server.

  10. Configure the CommServe route:

    • CommServe or gateway hostname: Verify the gateway hostname or the IP address. Make changes, if required.

  11. Click Next.

    The Summary page appears.

  12. Review the summary, and click Finish.

For more information about client firewall settings, see Network Topologies.

Loading...