Nodes

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.

See also.

• Adding a Client Node from the Master Server Level

• Adding a Client Node to the Master Server during Client Deployment

• Adding Other Node Types to the Master Server

Removing a Node

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.