You can add a physical node to a Microsoft (Windows) cluster file server or a Veritas (UNIX) cluster file server so that you can manage the clusters from the Command Center.
From the navigation pane, go to Protect > File servers.
The File servers page appears.
In the upper-right corner of the page, click Add server, and then click Add Cluster file server.
The Add cluster file server dialog box appears.
In the Add cluster name box, type the name of the Client Access Point associated with the Microsoft cluster group whose associated storage resources are to be backed up (as seen in the Failover Cluster Manager). The client name should have a unique name.
In the Host name box, type the fully qualified domain name of the Client Access Point for the Role that is associated with the Microsoft cluster group.
Note: The host name must be unique and the same name must not be used by an existing client in your environment.
In the OS Type area, select Windows or Unix and Linux.
From the Plan list, select the plan that you want to back up the storage resources of the client access point.
In the Job storage cache box, type the path for the job results directory.
The job results directory stores the job results files that are created when a job is initiated.
Note: The job storage cache must reside on a shared cluster drive. The shared cluster drive must be associated with the Client Access Point that you specified in the Host name box.
From the Nodes list, click to select the physical nodes where the Microsoft failover cluster is configured with the Commvault agent you installed.
While Configuring DB2 HADR cluster client, select physical nodes which are the part of DB2 HADR cluster.
From the Agents list, click to select the Agents you want to use in the cluster file server, and then click OK.
While Configuring DB2 HADR cluster client, you need to select only DB2 agent.
Optional: After you configure the cluster file server, a message is displayed that some remote cluster nodes failed to configure with the cluster file server. In such a situation, move the Force sync configuration on remote nodes key to right so that the remote clients can be accessed if one of the clients in the cluster configuration are not accessible.