To manage your nodes better, you may organize them in node groups. To add a new node group, follow the procedure specific for the interface you are using.
For any cluster, it is highly recommended to create a separate node group.
Tip. It is advantageous to create a separate node group for nodes connected using Network Data Management Protocol (NDMP nodes). Although DPX does not prevent you from having node groups containing both NDMP and non-NDMP nodes, there are limitations placed on NDMP nodes that make it difficult to properly define backups and privileges for a mixed group.
Go to Nodes in the sidebar. Switch to the Node Groups tab. Then select the Add Node Group button in the upper right corner.
The Add Node Group dialog will open.
Provide the Node Group Name.
The name may only include alphanumeric characters (a-z, A-Z, 0-9), underscores (_) and hyphens (-). No other special characters are allowed. The name cannot be longer than 48 characters.
Note. No two node groups within the Enterprise can have the same name. Do not use the reserved string BMR.
Optionally, select a device cluster (or tape library) from the drop-down list.
A device cluster is a set of storage devices, such as tape drives. If there are no device clusters or tape libraries in the pull-down menu, you can edit the node group later to add one.
The device cluster you select here is the default backup destination for certain backup types of the nodes in the node group. During backups, DPX automatically chooses available devices in the default device cluster and prompts the operator for mounts.
When you define a backup, you can override this default device cluster and choose an individual destination device. However, it is usually preferable to accept the default device cluster and let DPX choose the destination device from that cluster.
For NDMP node groups, it is best to choose an NDMP device cluster. For non-NDMP node groups, it is best to choose a non-NDMP device cluster. You could choose a SAN device cluster for either if it has both NDMP and non-NDMP devices.
Optionally, select a media pool from the drop-down list.
A media pool is a grouping of media volumes, such as tape cartridges. If there are no media pools in the pull-down menu, you can edit the node group later to add one.
The media pool you select here is the default pool for nodes in the node group. You can override this default media pool when you define backups.
Optionally, you can add a brief Descripition (max. 48 characters).
Click Save. The Node Group is now added.
Go to the Configure tab on the Function Tab bar, then click or right-click Enterprise.
Open the Add node group dialog in the right pane by doing one of the following:
Right-click the Enterprise name or icon to display a context menu. The selection check box will appear full next to the Enterprise icon, and the Edit Enterprise dialog will appear in the right pane. Then select Add Node Group.
In the left pane, select the Enterprise to which you want to add the node group.
From the menu bar, select Enterprise > Add Node Group.
On the task panel, click Add Node Group.
The Add Node Group dialog appears in the right pane.
Complete the active fields in the Add Node Group dialog:
Group Name Enter a name for the node group (for example, SALES). You can use up to 48 alphanumeric characters, no spaces.
Note. No two node groups within the Enterprise can have the same name. Do not use the reserved string BMR.
Device Cluster Name (optional) - Select a device cluster (or tape library) from the drop-down list. A device cluster is a set of storage devices, such as tape drives. If there are no device clusters or tape libraries in the pull-down menu, you can edit the node group later to add one. - The device cluster you select here is the default backup destination for certain backup types of the nodes in the node group. During backups, DPX automatically chooses available devices in the default device cluster and prompts the operator for mounts. - When you define a backup, you can override this default device cluster and choose an individual destination device. However, it is usually preferable to accept the default device cluster and let DPX choose the destination device from that device cluster. - For NDMP node groups, it is best to choose an NDMP device cluster. For non-NDMP node groups, it is best to choose a non-NDMP device cluster. You could choose a SAN device cluster for either if it has both NDMP and non-NDMP devices.
Media Pool Name (optional) Select a media pool from the pull-down menu. A media pool is a grouping of media volumes, such as tape cartridges. If there are no media pools in the pull-down menu, you can edit the node group later to add one. The media pool you select here is the default pool for nodes in the node group. You can override this default media pool when you define backups.
Comment Enter an optional comment (description) of up to 48 characters.
Select Add. The Node Group is now added to the Enterprise.
Each machine, be it virtual or physical, server or client, is considered a node of the Enterprise’s network it belongs to. The master server is a DPX node that contains DPX software, including the Catalog and modules that control scheduling, media management, and distributed processing. There is one master server per data protection Enterprise.
In order for the DPX to be able to perform any backup or restore jobs, a logical relation must be established between the Master Server and other nodes, such as Client or storage nodes.
Typically, you will deploy the DPX Master Server first, providing its hostname, network IP address, credentials and several other parameters. In the second step, you will deploy a DPX Client on each machine you want to back up from. During this process, you will provide the DPX Master Server’s hostname or IP address and credentials, thus adding the Client as a node to the Master Server.
You may also deploy DPX clients first, and add the client nodes to the Master Server later, using either web or desktop interface.
Note. Nodes other than DPX Client nodes must be added from the DPX Master Server.
Important. Generally, removing valid nodes from DPX is not recommended, as this may result in inconsistencies in job definitions. Please also note that if you remove a node and try to add the same or another node under the removed node’s name, an error will be thrown because the name has already been taken in the database. To avoid this issue, run Catalog Condense before attempting to re-use the removed node’s name.
This procedure describes adding a client node to an already deployed Master Server within the same Enterprise. This procedure is only possible if the DPX Client is not yet installed on the machine you want to add as a node.
A Catalogic DPX Master Server is deployed within the same network
The Master Server’s hostname / IP address and credentials are known
The Catalogic DPX Client is not yet deployed on the machine you want to add as a node
In the Add node to DPX Enterprise section, choose Yes to add this node to the Enterprise. You will need to provide the Master Server Hostname or IP address.
Attention! The installer does not validate the Master Server Hostname or IP address. If invalid data are provided, the node will not be added to the Master Server. To ensure the node was added successfully, connect to your Catalogic DPX Master Server via the web or desktop interface and check the list of all available nodes. See also Adding a client node from the master server level.
This procedure describes adding an already existing DPX Client machine as a node to the DPX Master Server. This procedure is only possible if a DPX Client is already installed on the machine you want to add as a node. The DPX Client and the DPX Master Server must also be in the same network.
The Catalogic DPX Master Server is deployed and can be accessed through either web or desktop interface
At least one Catalogic DPX Client is deployed within the same network
Open a web browser and go to the Master Server’s IP address.
Go to the Nodes section in the sidebar. A list of all nodes added to the DPX Master Server will be shown. At least one node, master, should be already on the list. This is the Master Server itself – compare the IP address in the list and in the web browser’s address bar. The Master Server can also serve as a client to back up data from itself.
Tip. If you expect a node to be already on the list but you cannot find it, try refreshing the view and then search for the node by its name, group or type.
Click the Add Node button in the upper right corner.
The Add Node dialog will open. Select the node Type: DPX Client. For other node types, see Adding Other Node Types to the Master Server.
Fill in all other required fields: specify the name for the new node, provide a valid resolvable hostname or IP address, and select the group for the node.
Note. The Node Name must be unique throughout the Enterprise, regardless of the Node Group it is saved in.
Tip. Providing the hostname is recommended over providing an IP address – in case the IP address changes, the hostname can still be resolved to the new IP address, and the connection between the server and the client will remain functional.
Click Save. The node is now added and is visible in the nodes list.
Tip. If you encounter a timeout error or the hostname provided cannot be resolved to a valid IP address, double-check your machine’s firewall settings, ensuring all Prerequisites for the DPX Client deployment are met, including the ports allowed.
See also. Adding a Node Group.
Go to the Configure tab and select Enterprise under Configuration Operations.
There should be at least one node group already visible, the DefaultGroup. You can add a new node to one of the existing node groups or create a new node group (see the next section).
Right-click the node group name or icon to display the 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.
Complete the fields in the ADD NODE pane.
Enter the logical name for the node. You can use up to 48 characters, no spaces. This is the name that DPX uses for the node. Note the following:
Any node that uses an 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.
Select the Access Method. For DPX Client nodes, this is TCPIP. For other node types, see Adding Other Node Types to the Master Server.
Enter the node hostname. Alternatively, you may provide its network IP address.
Select Add. The node is now added. You can see it in your Enterprise tree, and its parameters are visible in the EDIT NODE pane.
See also. Adding a Node Group.
Before adding a Hyper-V Host as a node to DPX, make sure you have a Hyper-V host with a DPX Hyper-V Agent installed. For details, see DPX Hyper-V Agent.
Restrictions. Hyper-V backup and restore features are only supported by the web interface. The desktop interface does not allow for handling Hyper-V nodes and such nodes will not be visible in the desktop interface.
The procedure below describes adding a Hyper-V host as a node to the DPX Master Server.
Open the DPX Master Server web interface in a web browser.
In the left-hand side menu pane, go to the Nodes section.
Click the Add Node button in the upper right corner.
The Add Node dialog will open. As Type, select Hyper-V Host. Specify the name for the new node (it must be unique throughout the Enterprise), provide a valid resolvable hostname or IP address, and select the group for the node.
Click Save. The node is now added and is visible in the nodes list.
Important. DPX does not verify the connection with the Hyper-V host when the node is added. If you encounter an authorization or connection error with the Hyper-V host, you might need to remove the node and add it again, paying special attention to providing a hostname or IP address that is valid within your network.
See also. For more general information about nodes, see Nodes.
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.
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.
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.
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 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.
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.
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
Enter the password to log into the NDMP node with the User ID above.
After entering the User Name and Password, select Add. The Define Node Feature dialog box will appear.
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 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 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.
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.
See also. For the latest system compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, see the DPX 4.10 .
DPX Client
TCPIP
unsupported
NDMP
See NDMP Backup and NDMP Restore
Hyper-V Cluster
unsupported
Hyper-V Cluster nodes will only be visible in the web UI
Hyper-V Host
unsupported
Hyper-V Host nodes will only be visible in the web UI
NetApp SVM
STORAGE_CTL
Select controller storage type: NetApp in the desktop UI
VMware vCenter/ESXi
VMWARE
vStor
STORAGE_CTL
Select controller storage type: vStor in the desktop UI
NDMP_AUTH_TEXT
User and password information is unencrypted.
NDMP_AUTH_MD5
User and password information uses key-to-the-hash encryption.
