Adding a Node
Requirements for a node:
A node must belong to a node group.
A node cannot belong to more than one group.
The procedure for adding a node depends on the type and intended usage of the node. For example, the procedure may vary depending on whether the node communicates via TCP/IP, NDMP, or VMware, whether it is a backup source or destination, and whether it is supported for NDMP, open systems, or DPX Block Data Protection.
Considerations for adding nodes:
Basic Node
Nodes added using this procedure include UNIX, Linux, and Windows servers. DPX communicates with these nodes via TCP/IP. DPX software is required on each node.
Open Enterprise Server (OES) Node with TCP/IP
DPX communicates directly with TCP/IP-capable OES Linux nodes. DPX software is required on the node.
NDMP Node
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 the 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.
See also. For the latest system compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, see the Compatibility Guide.
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.
Related Topics:
VMware Node
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 Configuring for VMware Protection in the User’s Guide.
STORAGE_CTL Node
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.
Related Topics:
Adding a Clustered Data ONTAP SVM Node in the Deployment Guide
Configuration Requirements for Agent-Based Clustered Data ONTAP Backup in the User’s Guide
Chapter 4: Catalogic vStor in the User’s Guide
Cluster Node
Considerations for adding a cluster node are described in Considerations for NetApp Clustered Data ONTAP SVMs in the Deployment Guide.
Exchange 2010/2013 Node
See General Installation Procedure for Exchange Nodes in the User’s Guide.
SharePoint Node
See Adding Physical SharePoint Nodes to the Enterprise in the User’s Guide.
To define a new node:
Open the Configure Enterprise window by clicking the Configure tab on the Function Tab bar, then clicking Enterprise.
Open the Add Node dialog.
Right-click the node group name or icon to display a context menu. Then select Add Node. The selection check box next to the node group icon indicates the selection and the Add Node dialog appears.
Enter the Logical Node Name
Enter a logical name for the node (for example, ENG-NDMP1). You can use up to 48 characters, no spaces. This is the name that DPX uses for the node. Use the host name because the host name is what the node is already known as on your network.
Note the following:
Any node that uses iSCSI initiator must conform to iSCSI initiator and Microsoft machine naming limitations. Some characters may be impermissible in the node name. For example underscore (
_
) should not be used.On Windows, DPX does not support nodes using names reserved by Windows for specific devices: CON, PRN, AUX, NUL. Note also that the string BMR is reserved.
Enter the Access Method and Resolvable Node Name. See Selecting the Access Method.
Selecting the Access Method
Select TCPIP, NDMP, VMWARE, or STORAGE_CTL from the Access Method pull-down menu, depending on how the node is connected to the Enterprise. Ensure you have reviewed the considerations above before selecting an access method.
If you select TCPIP access method, complete the additional TCPIP dialog field:
Resolvable Node Name or IP Address
Enter either the network IP address of the node or the host name (including domain name, for example:
dcserver.abc_corp.com
).
Select Add on the task menu at the top right of the right pane.
For OES nodes, you are prompted for authentication information. Enter the User ID and password required to log in to the node. The root password is also required.
For OES nodes, the System Type may appear as NetWare.
If you select 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.
Password
Enter the password to log into the NDMP node with the User ID above.
After entering the User Name and Password, select Add on the task menu at the top right of the right pane. The Define Node Feature dialog box appears.
Make your selections from the pull-down menus and click OK to add the NDMP node.
After you click Add, the following additional fields 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.
NDMP_AUTH_TEXT
User and password information is unencrypted.
NDMP_AUTH_MD5
User and password information uses key-to-the-hash encryption.
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 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.
If you select the VMware access method, complete the additional VMware node fields:
Port No.
The port number default is 443, which is the standard secure port number used by vCenter. It is recommended to leave this at 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 that has 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.
After entering the User Name and Password, click Add.
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 either the network IP address or the host name (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.
Note. The IPX access method may display for selection, however, this protocol and Netware servers that implement it are no longer supported.
Last updated