PowerProtect Data Manager 19.17 Storage Array User Guide

Add a Block Volume protection engine for PowerMax workloads

Deployment of a block volume protection engine is required to protect PowerMax storage array assets. Perform the following steps to add the protection engine.

Prerequisites

Block volume protection engines must be deployed on an ESXi server where SAN zoning to the PowerMax has been created.

NOTE:Configuring only one Block Volume protection engine for multiple PowerMax systems is not recommended. Add one protection engine for each PowerMax system for which you plan to protect assets in PowerProtect Data Manager, and configure all Block Volume protection engines on a dedicated ESXi server.

Steps

  1. From the left navigation pane, select Infrastructure > Protection Engines.
    The Protection Engines window appears.
  2. In the VM Direct Engines pane of the Protection Engines window, click Add.
    The Add Protection Engine wizard displays.
  3. On the Protection Engine Configuration page, complete the required fields, which are marked with an asterisk.
    • Supported Protection Type—Select Block Volume from the list.
    • Hostname, Gateway, IP Address, Netmask, and Primary DNS—Note that either only IPv4 addresses or only IPv6 addresses are supported.

      Deploy protection engines with fully qualified domain names (FQDNs) or IP addresses only. Short names are no longer supported. Existing protection engines which were deployed with short names are deprecated. Subsequent releases might require you to delete and redeploy these protection engine with FQDNs or IP addresses instead. When you deploy protection engines with FQDNs, each FQDN must have a DNS record.

    • vCenter to Deploy—If you have added multiple vCenter server instances, select the vCenter server to which to deploy the protection engine.
    • ESX Host—Select the ESXi host to which you want to deploy the protection engine.
    • Network—Displays all the networks that are available under the selected ESXi host or cluster. For virtual networks (VLANs), this network carries Management traffic.
    • Data Store—Displays all datastores that are accessible to the selected ESXi host or cluster based on ranking (whether the datastores are shared or local), and available capacity (the datastore with the most capacity appearing at the top of the list).

      You can choose the specific datastore on which the protection engine resides, or leave the default selection of <automatic> to allow PowerProtect Data Manager to determine the best location to host the protection engine.

  4. Click Next. The Networks Configuration page appears.
  5. On the Networks Configuration page:
    • To continue without virtual network configuration, or if this is a cloud-based OVA deployment of PowerProtect Data Manager, leave the Preferred Network Portgroup selection blank and then click Next and proceed to step 7.
    • To configure the virtual network (VLAN) to use for Data traffic, perform the following steps:
    1. From the Preferred Network Portgroup list, select a VST (Virtual Switch Tagging) or VGT (Virtual Guest Tagging) network.
      If you select a VGT portgroup, the list displays all virtual networks within the trunk range. If you select a VST portgroup, the list displays only the virtual network for the current VLAN ID.
    2. Select one or more virtual networks from the list.
      A protection engine requires an IP address from the static IP pool for each selected virtual network. If there are not enough IP addresses in a pool, the wizard prompts you to supply additional addresses for that network.

      Ensure that the selected virtual networks support a traffic type that is compatible with the
      protection engine. The
      PowerProtect Data Manager Administrator Guide provides more information about traffic types.
        

    3. If required, type an available static IP address or IP address range in the Additional IP Addresses column for the indicated virtual network.

      For convenience when working with multiple virtual networks, you can also use one of the
      Auto Expand options:
        

      • Expand Last IP—The wizard increments the host portion of the last IP address in the static IP pool. Click Apply.
      • Same Last Digit—The wizard adds the network portion of the IP address to the specified value. Type the host portion of the IP address and then click Apply.

      The wizard updates the value in the
      Additional IP addresses column for each selected network. Verify the proposed IP addresses.
        

    4. Click Next.
  6. On the Summary page, review the information and then click Finish.
    The protection engine is added to the VM Direct Engines pane. An additional column indicates the engine purpose. Note that it can take several minutes to register the new protection engine in PowerProtect Data Manager.
  7. Optionally, after adding the protection engine, you can change the percentage of the protection engine capacity that will be used. For example, you might want to change the Capacity setting to a lower value to avoid network bandwidth issues:
    1. In the PowerMax Block pane, select the added protection engine, and then click Edit.
    2. Change the maximum percentage value for Capacity, and then click Next to proceed through the wizard until you can click Finish to save the changes.

Next steps

In the Infrastructure > Asset Sources window, select the PowerMax and click Discover to recalculate the number of available protection engines.

For application-consistent protection, you can now add scripts and asset groups. Continue to Add pre-scripts and post-scripts for block volume protection and Add asset groups to associate scripts with block volumes.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\