Dell EMC Avamar for VMware 19.7 User Guide

Add a vCenter as an Avamar client in the AUI

Use the following procedure to add a vCenter as an Avamar client in the AUI.

1. In the AUI navigation pane on the left, click , and then click Asset Management.
2. In the domain tree, select a vCenter domain or a sub-domain for the client.
   To select a sub-domain client, toggle the Include Sub-domain switch to on.
3. Click next to ADD CLIENT, and then select Add VMware vCenter.
   The New vCenter Client wizard appears.
4. In the New Client Name or IP field, type the name of the client and then click NEXT.
   The vCenter Information pane appears.
5. In the vCenter Information pane, compete the following information for the vCenter:
   1. In the User Name field, type the user account name of the vCenter server administrator.
   2. In the Password field, type the password for the vCenter user account.
   3. In the Verify Password field, retype the password for the vCenter user account.
   4. In the Port field, type the vCenter web services listener data port number.
      443 is the default setting.
   5. Click NEXT.
   The Advanced pane appears where you can choose to enable the following auto discovery features that include Dynamic VM import by rule or Change Block Tracking.
6. To enable Dynamic VM import by rule, select Enable Dynamic VM import by rule and perform the following steps:
   NOTE:When the VMs are auto-discovered, user defined rules are used by the Avamar software to map the auto-discovered VMs to Avamar domains. User-defined rules are also used to automatically assign backup policies to auto-discovered VMs.
   • To add a rule:
     1. Click ADD RULE.
     2. In the Rule field, select a rule from the list.
     3. In the Domain filed, type the domain that the auto-discovered VM should be included in.

        If the domain entered here does not exist, it is automatically created.

   • To create a rule:

     Rules are used to automatically map auto-discovered VMs to domains, and to assign backup policies to auto-discovered VMs. Rules use one or more filtering mechanisms to determine whether VMs qualify under the rule.

     1. Click CREATE RULE.
     2. In the Rule Name field, type a name for the rule.
     3. In the Match Type field, select whether the rule should match Any of the listed filter mechanisms, or All of them.

        This selection allows you to configure multiple different filters to select VMs, and to determine how these filters interact with one another to select the correct VMs. For example, you might create a filter that uses a VM folder path to select VMs, and another filter that uses a VM naming convention.

        This option can then be used as follows to determine which VMs are included under this rule:

        • To include only VMs that are in the defined folder path and also follow the naming convention, select All. This step excludes VMs that are in the folder path but that do not follow the naming convention, and also excludes VMs that follow the naming convention but are not in the folder path.
        • To include any VMs that are either in the VM folder path or that follow the naming convention, select Any.
     4. In the Filter field, select the filter type.

        For example, to create a filter that uses a VM naming convention, select VM Name, or to create filter that uses a vCenter VM Tag, select VM Tag.

        NOTE:The VM Tag selection is only available with vCenter 6.0 and greater.
     5. In the Operator field, select the operand.

        For example, if VM Name is selected for the filter type and begins with is selected for the operand, then all VMs whose names begin with the filter text is selected.

     6. In the Value field, type the filter text.

        For example, to create a filter that selects all VMs whose names begin with the text string HR_, select VM Name for the filter type, begins with for the operand, and type HR_ for the filter text.

     7. To create additional filters, click the plus sign (+).

        This step adds a row to the list of filters. To delete an existing row, click Delete.

     8. Click SUMBIT.

        Changes made to tags may experience a delay of up to 12 hours before being enforced. For this reason, edit tags with caution, or perform a synchronized vCenter operation, which automatically synchronizes the vCenter with the Avamar server.

        Best practice for rule creation is to ensure that rules are mutually exclusive, to avoid the situation where a VM might qualify under multiple rules.

   • To enable Change Block Tracking, select Enable Change Block Tracking.

     If changed block tracking is not enabled, each virtual machine image must be fully processed for each backup, which might result in long backup windows, or excessive back-end storage read and write activity.

     Enabling changed block tracking does not take effect until any of the following actions occur on the virtual machine:

     • Restart
     • Power on
     • Resume after suspend
     • Migrate
7. Click NEXT.
   The Optional Information pane appears.
8. Optional, compete the optional contact information including the contact name, phone number, email, and location, and then click NEXT.
   The Summary pane appears.
9. Review the client summary information, and then click ADD.
   The Finish pane appears.
10. Click FINISH.
    NOTE:Add IPV6 vCenter to Avamar using FQDN only. IPV6 address is not supported.