Can I configure a Windows or UNIX cluster for Oracle RAC?
Oracle RAC uses its own cluster technology. Therefore, it does not depend on operating system-level clusters.
Can I have a fully configured client on a physical node without consuming licenses?
Yes. If you do not want the licenses to be consumed on the physical computer, install the Agents in restore only mode. This alternate installation method will move the license consumption to the cluster group client. For installation steps, see Installing Restore only Agents.
Can I install an agent software in the cluster group client?
No. All software components must be installed on a physical node to make them available for the cluster group client.
Can I install the CommServe in a cluster environment?
Yes. The CommServe can be configured in a cluster environment during installation.
During installation, CommServe binaries are installed on the physical nodes while the SQL database is installed on the cluster server. The install procedure is performed on the active node with the choice of an automated or separate install to all passive nodes, with no failover required at the end of the installation process. Once installed on each cluster node, the CommServe software tolerates binary corruption, meaning that if the binaries are corrupted on one physical computer, the cluster resources can fail over to another physical computer.
Can I install the SQL Express Edition in a cluster environment?
No. The SQL Express Edition cannot be installed on a cluster environment. You need to install the SQL Server Enterprise Edition to prepare your cluster setup for the CommServe installation.
Can I perform snapshot and VSS backups for SQL Server agents in a Veritas cluster?
No. Snapshot and VSS backups for SQL Server iDataAgents are not supported on Veritas clusters.
Can I remotely upgrade the software on a clustered server?
Yes, you can remotely upgrade the software on a clustered server.
Can I use the Cluster Group client to update all the physical nodes associated with it?
No. You cannot use the cluster client to apply updates to the physical nodes. Updates and service packs should be applied on the physical node that you want to update.
Can the software on physical nodes associated to a Cluster Group client be installed on different Instances?
No. The Agent software on all physical nodes that will be associated with the cluster group client must be installed on the same instance. For example, consider that you have physical nodes P1 and P2. If you install the software on P1 on Instance001, you must also install the software on P2 on Instance001.
When the active node fails over, the new active node will not be able to start the cluster services if it is on a different instance.
How do I install the MediaAgent in the cluster group?
As any other agent, the MediaAgent must be installed on a physical computer. Libraries must be attached to the physical computer and shared across SAN in a DDS or non-DDS environment. You can also use Alternate Data Paths (GridStor) to provide the necessary failover capabilities. For more information on GridStor, see Alternate Data Paths (GridStor).
Follow the steps described in Managing Agents in the Cluster Group Client to configure a MediaAgent computer in a cluster group. Note that the index cache must be configured on the cluster group and not on the physical computer. If you do not specify the index cache, the Job Result directory path will be used.
How do I uninstall CommServe from a Microsoft cluster?
To remove the CommServe from a cluster environment, you must uninstall the software from each of the cluster nodes where it was installed.
You can also remove the CommServe from just one of the cluster nodes, while allowing it to continue to function on the remaining nodes. To do so, the computer from which you are uninstalling the CommServe must be a passive node. If you uninstall the CommServe from an active node, it will stop functioning because the database will also be removed.
When you have more than one CommServe installed in a cluster and if you uninstall one of the CommServes from any of the nodes, you need to re-register the DM2FastWebquery.dll using the following command line utility on the node where the CommServe was uninstalled:
<software installation path>\Base\CVGACUtil.exe /i /s DM2FastWebquery.dll
How do I use the physical node interface for backups on cluster clients in a cluster?
If a cluster client interface cannot talk to the CommServe computer/MediaAgent, then use the following procedure to configure cluster client backups using the active physical node's network interface.
-
Configure one-way network routes from physical nodes (including cluster client) to the CommServe computer/MediaAgent.
For more information, see Setting Up a One-Way Direct Connection (Client to Server) Using a Predefined Network Topology.
-
Configure multiple data interface pairs (DIPs) between the cluster client and the CommServe computer/MediaAgent.
Note
While adding DIPs for a passive physical node, you must manually enter the IP address of the node, as the GUI drop-down list will not automatically populate with IP addresses of passive nodes.
For the cluster client, select each physical node's interface. For example, if the cluster client has three physical nodes, then add three DIPs between the cluster client and the CommServe computer/MediaAgent (that is, one for each physical node).
For more information, see Setting Up a Data Interface Pair Between a Client Group and a Client.
How does Commvault handle service group failover on a Veritas cluster?
After the cluster group client is configured in the CommCell Console, Commvault creates an application called GxClusterPlugin_service_group_name in the Veritas cluster (VCS).
During a VCS service group failover, the plug-in performs the following tasks:
-
Turns off firewall on the service group, and enables it on the active node.
-
Notifies the CommServe database where the service group is active for effective resource allocation.
-
If archiving/OnePass operations are configured, the plug-in switches the monitoring mount points to the active node to handle stub recalls.
If a CommServe installed in a Microsoft Cluster Environment fails over, what happens to all backup operations?
After a CommServe in a Microsoft Cluster Environment undergoes a failover, restartable jobs are restarted, but non-restartable jobs fail to complete. There might be scenarios when the failover process is quick enough to beat the network timeout, allowing backup jobs that cannot be interrupted to continue.
We recommend that all "non-interruptible" backups are restarted after the failover.
Is cluster configuration from the CommCell Console supported for clients from previous releases?
No. Cluster configuration from the CommCell Console is not supported for clients from previous releases.
What happens if I upgrade from a previous version of Commvault?
When you upgrade a physical node to a new version of Commvault, all the cluster group clients associated with the physical node are automatically upgraded. This operation will not upgrade other physical nodes in the cluster client. You must upgrade each physical node individually.
Will my cluster group client be deconfigured if I remove all physical nodes associated with it?
No. When you remove all associated physical nodes from the cluster group client, it is recommended to deconfigure the cluster group client as it will become a non-active client. Use the steps below to deconfigure the client:
-
From the CommCell Browser, go to Client Computers > cluster_group_client.
-
Right-click the cluster group client, and then click All Tasks > Release License for Client.
-
Click OK to continue.
-
Click Yes to continue with the license release.
