Configure Automatic Access Nodes Selection

Add a Hypervisor with Automatic Access Node Selection

You can add a hypervisor for the VSA and use the Automatic option to allow Commvault software to select access nodes for the Pseudo Client.

Before You Begin

  • Your environment should have at least one VSA proxy that can connect to the hypervisor.

  • For a cloud hypervisor, you will need at least one cloud vendor-specific proxy.

  • For an on-prem hypervisor, you will need at least one on-premises proxy.

  • For more information about adding a hypervisor for a specific virtualized platform, see the documentation for that platform. For example, see Guided Setup for Azure.

Procedure

  1. From the navigation pane, go toProtect > Virtualization.

    TheVirtual machines page appears.

  2. On theHypervisors tab, clickAdd hypervisor.

    The Configure Hypervisor page appear.

  3. Select the vendor to configure.

  4. Click Next and complete the details to create the hypervisor.

  5. From Access node option, select Automatic.

    The Commvault software performs the automatic access node selection process for authentication.

  6. ClickNext to add a VM group.

Create a VM Group and Configure the Automatic Access Node Selection Process

After creating the hypervisor with the Automatic option, access nodes will be configured automatically while creating the VM group. Configuration is based on:

Note

With IntelliSnap-enabled backups, make sure MediaAgents are zoned correctly since MediaAgents from the plan are used as access nodes.

The automatic access node selection operates as follows:

  • Based on selected server plan, the Commvault software retrieves the Primary Storage Pool from the plan and gets a list of access nodes (MediaAgents) from the Primary Storage Pool.

  • A resource pool is created automatically for the Storage pool if one does not already exist.

    • All MediaAgents are added (as the access nodes) to the resource pool.

    • If a MediaAgent does not have a Virtual Server package, then Virtual Server packages are added via a Push install on one of the MediaAgents.

      Note

      Further distribution of the Virtual Server package to all selected MediaAgents happens during the backup operation.

    • A resource pool is created with the following naming convention: ‘<Plan Name – Virtualization>’

    • If the first VM group is created, access nodes are picked up from the resource pool and placed at the hypervisor level and the access nodes for the VM group will show as ‘Inherited from Hypervisor.’

    • If the 2nd or 3rd VM group is created with the same plan having the same list of access nodes at the hypervisor level, the access nodes for the VM group will show as ‘Inherited from Hypervisor.’

    • If the 2nd or 3rd VM group is created with a different plan, access nodes are picked up from the respective resource pool and placed at the VM group level.

    • You can control the access nodes by modifying the Access node list at the resource pool level. This will update the access nodes at the Hypervisors or VM group level which are associated with the Resource Pool. See Updating Access Nodes via the Resource Pool.

Procedure

To create a VM group with a server plan selected, see Add a VM Group for the hypervisor.

Update Access Nodes at the Hypervisor Level

If you manually update access nodes at the hypervisor level, the automatic access node selection process will be disabled for the hypervisor and its respective VM groups. With the automatic selection disabled for the hypervisor and VM groups, any association with the resource pool is removed. This means that any update of access nodes at the resource pool level will no longer reflect at the hypervisor/VM group level.

Update Access Nodes at the VM Group Level

If you manually update access nodes at the VM group level, the automatic access node selection process will be disabled for the VM group only. With automatic selection disabled for the VM group, any association with the resource pool is removed. This means that any update of access nodes at the resource pool level will no longer reflect at the VM group level.

Enable Auto Scale at Hypervisor Level

If you enable Auto Scale at the hypervisor level, the automatic access node selection process will be disabled for the hypervisor and its respective VM groups. This means that there will no longer be an association with the resource pool, and therefore, updates to access nodes at the resource pool level will not reflect at the hypervisor or VM group level.

Cancel VM Group Creation

If you do not configure a VM group after creating the hypervisor with the Automatic option selected, then access nodes will not configure at the hypervisor level. You must select a server plan with the default VM group or create a new VM group with the plan to have the access node configure at the hypervisor level.

Change the Plan for VM Group Level

If you change the server plan for the VM group, the access nodes will be repopulated for the VM group based on the plan you selected.

Loading...