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.
About this task
These steps contain a simplified
protection engine deployment specific to NAS asset protection.
For existing
protection engine deployments, expand the details section for each engine to determine the supported protection types.
Steps
Log in to the
PowerProtect Data Manager user interface as a user with the
Administrator role.
From the left navigation pane, select
Infrastructure > Protection Engines.
The
Protection Engines window appears.
In the
VM Direct Engines pane of the
Protection Engines window, click
Add.
The
Add Protection Engine wizard displays.
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.
vCenter to Deploy—If you have added multiple vCenter server instances, select the vCenter server on which to deploy the
protection engine.
NOTE Ensure that you do not select the internal vCenter server.
ESX Host/Cluster—Select on 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.
Click
Next.
On the
Networks Configuration page:
NAS protection does not support virtual networks. Leave the
Preferred Network Portgroup selection blank and then click
Next to continue without virtual network configuration.
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.
Next steps
If the
protection engine deployment fails, review the network configuration of
PowerProtect Data Manager in the
System Settings window to correct any inconsistencies in network properties. After successfully completing the network reconfiguration, delete the failed
protection engine and then add the
protection engine in the
Protection Engines window.
Data is not available for the Topic
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: <>()\