Symptoms
DPX reads the cluster configuration when performing either a browse or a backup job. It has a strict requirement for the cluster resources to have specific names. Typically, these are added at the time of the installation. If the names are not successfully added at the time of installation, you can resolve this using the steps below.
Resolution
The Cluster GUI (Cluster Failover Manager) will not allow you to configure all the resource names that DPX requires to communicate correctly. To bypass certain restrictions, you can use Windows PowerShell to configure the resource names and values. When opening Windows PowerShell, select Run as Administrator.
The following two resource names must match one another for DPX to function correctly:
Catalogic DPX Network Name
Catalogic DPX IP Address
1. Adding the Catalogic DPX group
If the cluster group Catalogic DPX does not exist, it can be created as follows:
a. Open Failover Cluster Manager, expand the cluster name, right-click Roles, and select Create Empty Role.
b. Right-click New Role, then select Properties. In the Name field, type Catalogic DPX, then click Apply and OK.
2. Adding the DPX Virtual Node Name
To add the DPX Virtual Node Name Catalogic DPX to the group, run the Windows PowerShell command below:
add-clusterresource –name “Catalogic DPX Network Name” –resourcetype “Network Name” –group “Catalogic DPX”
The DNS name and the IP address will need to be added via the Failover Cluster Manager. Right-click the server name “Catalogic DPX Network Name” (DPX Virtual Node Name) created by the previous command. You will see it in the Resource tab. Select Properties.
In the DNS field, enter the hostname of the DPX Virtual Node Name. For IP addresses, click Add and enter the IP address for this hostname. Click Apply, confirm the change, then click OK.
Note: For the purpose of this documentation, the example hostname is DPX2012FS.
Failover Cluster Manager will then change the name Catalogic DPX Network Name to the DNS name you entered, which is DPX2012FS.
You will need to fix the DNS name, or DPX will not be able to browse the DPX Virtual Node Name successfully. This will also cause failures when adding DPX Cluster Nodes to the Enterprise. For example, when using the commands Add Node or Edit Node IP for the cluster node in Configure > Enterprise, it fails with the error rc=0. MS_SUCCESS.
You will need to run the Windows PowerShell Commands below to change the name back to Catalogic DPX Network Name.
Get-clusterresource “DPX2012FS” | %{ $_.Name = “Catalogic DPX Network Name” }
Note: You can run the command Get-clusterresource to see a list of the resource names.
Expand the DPX Virtual Node Name, right-click the IP address you just assigned, then select Properties. Change the name of the IP address to “Catalogic DPX IP Address”. Click Apply and OK.
3. Adding the DPX Cluster Cmagent Service
You can add the DPX Cluster cmagent service using the Failover Cluster Manager.
Right-click the Catalogic role, select Add a Resource, then Generic Service. This brings up a wizard. Choose the Virtual CMAgent and click Next. Accept any remaining default options to exit the wizard.
Once the service has been added, right click on the service, select Properties, then select the Dependencies tab. Add the Catalogic DPX IP address and Catalogic DPX Network Name in the Resource list. Click Apply and OK.
4. Starting the Catalogic DPX Role
Under Roles, right-click Catalogic DPX and select Start Role. Once the Role is online you will see that Windows changed the role name from Catalogic DPX to the hostname of the DPX Virtual Node Name. Right-click it and select Properties. In the Name field, change it back to Catalogic DPX. Click Apply and OK.