Adding Other Node Types to the Master Server

Nodes other than DPX Client nodes must be added manually from the DPX Master Server. The procedure is similar to Adding a Client Node from the Master Server Level. There are differences in naming conventions and feature handling between the web interface and desktop interface.

Web interface

Desktop interface

Remarks

Note. The IPX access method may be displayed for selection in the desktop interface. However, this protocol and Netware servers that implement it are no longer supported.

Proceed with adding a node as described in Adding a Client Node from the Master Server Level.

Depending on the selected access method, different fields need to be completed.

Hyper-V Cluster

A Hyper-V cluster is a group of multiple physical servers clustered together, each running the Hyper-V hypervisor. The clustering enables automatic failover, load balancing, and simplified management of VMs across the cluster, ensuring continuity of services in case of hardware or software failures.

If you select Hyper-V Cluster as the node type, complete the following additional fields:

Port Number The default port number for Hyper-V Agent is 50881. It is recommended to leave the default setting.
Authorization Key Provide the Authorization Key specified when configuring the DPX Hyper-V Agent.

Hyper-V Host

A Hyper-V host is a single physical server that runs the Hyper-V hypervisor. It hosts and manages virtual machines, providing them with the necessary resources like CPU, memory, storage, and network connectivity. The Hyper-V host ensures VMs can run isolated from one another while sharing the physical hardware efficiently. In the event of a failure on this host, VMs may experience downtime unless failover mechanisms, like those in a cluster, are in place.

If you select Hyper-V Host as the node type, complete the same additional fields as in Hyper-V Cluster:

Port Number The default port number for Hyper-V Agent is 50881. Leave the default setting unless the port has been changed during the installation process.
Authorization Key Provide the Authorization Key specified when configuring the DPX Hyper-V Agent.

NetApp SVM

The NetApp SVM node serves as a destination node for agentless backup operations. When adding NetApp SVM node do the DPX Enterprise, define the node at the data SVM level, not the cluster level.

If you select NetApp SVM as the node type, complete the additional fields:

User Name
Enter the User ID to log into the node.
Password
Enter the password to log into the node with the User ID above.

VMware vCenter/ESXi

VMware is a special node type used for scanning in a VMware vCenter server. The vCenter server is used to coordinate agentless Block backup and restore operations. See Agentless Backup for VMware and Agentless VMware Restore.

If you select the VMware as the node type, complete the additional fields:

Port No.
The default port number is 443, the standard secure port number used by vCenter. It is recommended to leave the default setting.
User Name
Enter the User ID to log into the vCenter node. The User ID determines the resources that DPX has access to in the vCenter enterprise. Use an ID with access to all the virtual machines you want to back up.
Password
Enter the password to log into the vCenter node with the User ID above.

Click Test to verify the details and credentials, and to confirm the vCenter can be reached.

vStor

Catalogic vStor server is a virtual or physical data storage appliance, acting as the primary backup destination for DPX. For more information, refer to the vStor 4.10 Documentation.

If you select vStor as the node type, complete the additional fields:

User Name
Enter the User ID to log into the vStor node.
Password
Enter the password to log into the vStor node with the User ID above.

Click Test to verify the details and credentials, and to confirm the connectivity with the vStor.

Proceed with adding a node as described in Adding a Client Node from the Master Server Level.

Depending on the selected access method, different fields need to be completed.

NDMP

DPX communicates with NDMP-compliant nodes, including NetApp storage systems, NetApp OSSV nodes, and other third-party storage appliances. Such NAS devices are referred to as NDMP nodes. DPX software is not installed on NDMP nodes; the NDMP service is provided directly by third-party hardware or software.

To communicate with an NDMP node, there must be at least one non-NDMP client node licensed to run the NDMP client “proxy” module. This module is included with Windows or Linux DPX client installation. An NDMP node communicates with DPX through the NDMP module on the client node.

You can use NDMP nodes for local backups, three-way (remote) backups, or appliance-to-server backups. For NetApp 7-Mode controllers, the node can be used as a destination for Block backups.

DPX allows non-root accounts to scan NDMP nodes into the Enterprise and to perform NDMP backup and restore operations. Consult your third-party vendor documentation for setting up the appropriate login, permissions, authentication style, and password required for coordinating NDMP backups.

If a tape library is attached to a NAS device or NetApp storage system, any node specifying the tape library as a backup destination must be added to the Enterprise as an NDMP node.

If you select the NDMP access method, complete the additional NDMP dialog fields:

Resolvable Node Name or IP Address
Enter either the network IP address of the NDMP node or the host name (including domain name, for example: dcserver.abc_corp.com).
Client Node
Select the node name for the node that is running the NDMP module. This field specifies a server that has client software on it. The node acts as an NDMP agent, transmitting commands between DPX and the NAS appliance.
In a three-way backup, data from one NDMP appliance is backed up through another NDMP appliance that is locally attached to a storage device. If the two NDMP nodes have different client nodes, the client for the NDMP node connected to the storage device is the controlling node for both NDMP nodes in the three-way backup operation.
Click Test to the right of the Client Node field to test NDMP communication with the client node. DPX issues a message informing you whether the test passed or failed.
Port No
The port number default is 10000, which is the standard port number reserved for NDMP. It is strongly recommended to accept the default setting.
User Name
Enter the User ID to log into the NDMP node. The User ID determines the files and directories that DPX has access to on the NDMP node. Use an ID that has access to all the data you want to back up (for example, the system administrator account).
You must enter a user name with root privileges when you configure a NetApp storage system for use with DPX Block Data Protection. For NDMP Tape backup and restore, a non-root account can be used. See DPX with NetApp Data ONTAP 7-Mod in the DPX 4.9.x Reference Guide.
Password
1. Enter the password to log into the NDMP node with the User ID above.
2. After entering the User Name and Password, select Add. The Define Node Feature dialog box will appear.
3. Make your selections from the pull-down menus and click OK to add the NDMP node.
After clicking Add, the following additional fields will appear:
Authentication Type
Specifies how user and password information is encoded. The following values may be defined, depending on the authentication methods configured on the NDMP node.

Backup Type
Select the backup method for NDMP backup. The pull-down menu displays the valid NDMP backup types supported by the NDMP server. NDMP backup types depend on the manufacturer of the configured node hardware. Appropriate licensing from the manufacturer may be required. See the documentation from the manufacturer for definitions of backup types and licensing requirements.
The most common backup types for storage systems are Dump and SMTape. In general, Dump is essentially a file system backup of the volume and SMTape is a block-level image of the volume. The Dump protocol is generally used when backup of specific (but not all) files, folders, or qtrees are desired and selective file restore is a priority. The SMTape protocol is generally used when a full volume restore is necessary for disaster recovery or for seeding a secondary remote storage system for subsequent SnapMirror synchronization.
For additional information about Dump and SMTape, see Considerations for NetApp Clustered Data ONTAP SVMs in the DPX 4.9.x Deployment Guide and read the knowledge base article 42154.
Volume Snapshot Count Error Level
Specify the maximum number of backup snapshots on the secondary volume. Accept the default value unless you have a specific need to lower it. Backups fail if the limit of the storage system is exceeded.
Volume Snapshot Count Warning Level
Specify the number of backup snapshots on the secondary volume that triggers a warning message. Accept the default value unless you have lowered the Volume Snapshot Count Error Level.
Volume Low Space Error (%)
Enter the minimum percentage of free space you require on the secondary volume to run a backup. The minimum setting is 1 percent.
Volume Low Space Warning (%)
Enter the percentage space remaining on the secondary volume that triggers a warning message. The minimum setting is 15 percent.
For details on the enforced volume low space fields, read the knowledge base article 46114.

VMWARE

If you select the VMware access method, complete the additional VMware node fields:

Port No.
The default port number is 443, the standard secure port number used by vCenter. It is recommended to leave the default setting.
User Name
Enter the User ID to log into the vCenter node. The User ID determines the resources that DPX has access to in the vCenter enterprise. Use an ID with access to all the virtual machines you want to back up.
Password
Enter the password to log into the vCenter node with the User ID above.

STORAGE_CTL

Agentless Backup
A STORAGE_CTL node can be added for agentless backups of virtual machines. The STORAGE_CTL node serves as the destination node for the agentless backup operation.
When adding NetApp Clustered Data ONTAP to the DPX Enterprise, define the STORAGE_CTL node at the data SVM level, not the cluster level.

Note. To protect a STORAGE_CTL node, you can add the same node as an NDMP node, then define and run an NDMP backup job where that node is the client.

Agent-Based Clustered Data ONTAP Backup
To define an agent-based backup to NetApp Clustered Data ONTAP, scan the destination data SVM as a STORAGE_CTL node instead of an NDMP node. When adding NetApp Clustered Data ONTAP to the DPX Enterprise, define the STORAGE_CTL node at the data SVM level, not the cluster level. See If you select the STORAGE_CTL access method in Selecting the Access Method.
vStor Backup
To define an agent-based backup to a vStor node, scan the destination vStor server as a STORAGE_CTL node.

If you select the STORAGE_CTL access method, complete the additional STORAGE_CTL node fields:

Storage Controller Type
Select either NetApp or vStor
Resolvable Node Name or IP Address
Enter the network IP address or the hostname (including the domain name). If adding NetApp Clustered Data ONTAP, define the node at the data SVM level, not the cluster level.
User Name
Enter the User ID to log into the node.
Password
Enter the password to log into the node with the User ID above.
Volume Snapshot Count Error Level
Specify the maximum number of backup snapshots on the STORAGE_CTL node. Backups fail if the limit is exceeded.
Volume Snapshot Count Warning Level
Specify the number of backup snapshots on the STORAGE_CTL node that triggers a warning message. Accept the default value unless you have lowered the Volume Snapshot Count Error Level.
Volume Low Space Error (%)
Enter the minimum percentage of free space you require on the STORAGE_CTL node to run a backup. The minimum setting is 1 percent.
Volume Low Space Warning (%)
Enter the percentage space remaining on the STORAGE_CTL node that triggers a warning message. The minimum setting is 15 percent.
For details on the enforced volume low space fields, read the knowledge base article 46114.

Last updated 3 months ago