> Essential > Virtualization > VMware > Implementation Planning

Deploying a VMware Access Node for Linux

You can add a VMware Linux access node (VSA proxy) to a hypervisor. The Linux access node can be used for Live Browse or Live File Recovery operations.

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 (FREL) 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.34.36 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 VMware FREL or Linux access node, 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, in the Access Node tile, click Actions, then click Deploy new Linux access node.

    The Deploy Linux Access Node wizard launches and displays the VM name and location page.

  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:

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

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

      • Thick provision eager zeroed

      • Thick provision lazy zeroed

      • Thin provision

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

  7. Click Next.

  8. Configure the client:

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

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

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

      Important

      The use of the ampersand character (&) in the password for the root user account is not supported. If using an ampersand in the root password is an absolute requirement, you can change the password in the VMs guest OS after the successful deployment.

    • Confirm password: Reenter the password of root user of the virtual machine.

      Note

      When you configure the client, the firewall settings are automatically inherited from the associated client computer group. For more information, see Network Topologies.

    • Select server group: Name of the server group. Access nodes will be added to this server group and the group's network configuration will be used in the newly created access nodes.

    • Linux timezone: Available timezones.

    • Automatic OS updates: Move the toggle switch to the right to enable automatic OS updates. By default, automatic updates are applied daily for security updates.

  9. Configure the IP:

    The following fields need to be entered when the File Recovery Enabler 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 Submit.

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

Loading...