# Deploy a Linux access node for VMware vSphere

To deploy a Linux access node for VMware vSphere data protection operations, review the requirements and placement guidelines, deploy the access node, verify registration and connectivity, and then run a small test operation.

You can deploy a Linux access node by using either:

- The Deploy New Linux access node workflow in Commvault (recommended)

- A manual OVA deployment in vCenter (use when automated deployment isn't available)

## Requirements

- VMware vCenter access with permissions to deploy VMs

- Network connectivity between:

  - The access node

  - vCenter and ESXi hosts

  - Storage targets

- Commvault environment configured and reachable

- VMware vSphere credentials with the required permissions

- Commvault credentials with the required permissions

## Guardrails

- Use separate access nodes for on-premises and cloud hypervisor workloads. If you use multiple access nodes:

  - Allow communication between nodes.

  - Verify that each node can reach vCenter, ESXi hosts, and storage targets.

- Do not use the same VM template for the access node and protected VMs.

- Use the latest OVA image to ensure security updates and compatibility.

## Deploy a Linux access node in Commvault

This method is the most common and recommended deployment for Linux access nodes.

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

2. On the Hypervisor tab, click the hypervisor.

3. On the Configuration tab, in the Access nodes tile, click Actions > Deploy new Linux access node.

4. Enter a name for the VM, and then click Next.

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

6. Select a deployment size, and then click Next.

7. Configure the following:

   - Destination network

   - Virtual disk format

   - Datastore

8. Click Next.

9. On the Customize template page, configure the access node:

   - Client name

   - Host name

   - Root password

   - Server group

   - Linux timezone

10. Enable the Automatic OS updates toggle key if required.

11. Configure network settings:

    - Enable Use DHCP, or specify:

      - Static IP address

      - Netmask

      - Gateway

    - DNS search suffix

    - Nameserver 1

    - Nameserver 2

12. Configure additional network settings:

    - Network gateway hostname

    - NTP server hostname

13. Click Next.

14. On the Summary page, review the configuration, and then click Finish.

## Deploy a Linux access node by using a VMware OVA

Use this method in the following cases:

- You are a Commvault SaaS customer

- When automated deployment from Commvault isn't possible

- When internet access or vCenter permissions are restricted

To deploy a Linux access node using an OVA, follow these steps:

1. Download the Linux access node OVA file:

   Commvault SaaS

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

   2. On the Hypervisor tab, click the hypervisor.

   3. On the Configuration tab, in the Access nodes tile, click Actions > Add hypervisor.

   4. Download the Linux (64-Bit) OVA for your ring.

   Commvault software
   - Download the Linux access node and MediaAgent OVA file.

2. In VMware vCenter, deploy the OVA by using Deploy OVF Template.

3. During deployment, configure:

   - Compute resource

   - Datastore

   - Network

   - Template customization values for:

     - Host name and root password

     - Timezone and NTP

     - DHCP or static IP settings, including DNS

     - Registration with Commvault

     - Authcode (for Commvault SaaS deployments, copy the authcode from the Add a new Access node dialog)

4. After deployment, power on the VM.

## Verify the access node in Commvault

Verify that the access node registers with the Commvault environment.

1. Confirm that the access node appears in the infrastructure list at Manage > Infrastructure.

2. In the hypervisor configuration, confirm that the access node appears under Configuration > Access nodes.

3. Verify connectivity to:

   - vCenter

   - ESXi hosts

   - Storage

4. Run a small test operation (for example, a test backup or a browse action) to confirm end-to-end access.

×

Loading...