PowerProtect Data Manager 19.13 Network-Attached Storage User Guide

Deploy a protection engine for NAS asset protection

The NAS protection engine hosts the NAS agent. If there is no available protection engine, data protection operations fail.

1. Log in to the PowerProtect Data Manager user interface as a user with the Administrator role.
2. From the left navigation pane, select Infrastructure > Protection Engines.
   The Protection Engines window appears.
3. In the VM Direct Engines pane of the Protection Engines window, click Add.
   The Add Protection Engine wizard displays.
4. On the Protection Engine Configuration page, complete the required fields, which are marked with an asterisk.
   • Supported Protection Type—Select NAS asset protection.
   • 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.
     NOTE: Ensure that you do not select the internal vCenter server.
   • ESX Host/Cluster—Select to which cluster or ESXi host you want to deploy the protection engine.
   • Network—Displays all the networks that are available under the selected ESXi Host/Cluster. For virtual networks (VLANs), this network carries Management traffic.
   • Data Store—Displays all datastores that are accessible to the selected ESXi Host/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.

5. Click Next.
6. On the Networks Configuration page:

   NAS protection supports virtual networks. If your infrastructure is configured with VLANs, select a network from the Preferred Network Portgroup list and click Next. Else, leave the preferred network port group blank.

7. 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. The protection engine also appears in the vSphere Client.