Cluster Configuration - FAQ

Table of Contents

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 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.

For the steps required to install the CommServe in a cluster, see Install the CommServe in a Clustered Environment. If you want to install one or more agents in the cluster, ensure to install the agent on the cluster node where the CommServe is installed to allow future fail over operations.

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 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 install the Web Console in a cluster environment?

No. The Web Console cannot be installed on a cluster environment.

For example, if you plan to install the Web Console on the CommServe computer, but the CommServe computer is configured in a cluster, then you should install the Web Console on a different computer.

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.

Use the following steps for upgrading the software in a clustered environment from CommCell Console:

  1. You will need temporary disk space on the client to perform the upgrade. Ensure that you have the requisite space as described in Space Requirements in each of the client computer before initiating a remote upgrade.
  2. Make sure that your CommServe has been upgraded to the current version of the software.
  3. Configure software download options to download the software packages to the CommServe Cache directory using an FTP source site:
    • Verify that you have adequate space for the packages.
    • From the CommCell Browser, right-click the CommServe computer node, point to All Tasks > Add/Remove Software and then click Download Software.
    • From the General tab, select the Download Packages checkbox which automatically selects all the options under Windows and Unix.
    • Click OK.
    • After the job is complete, right-click the CommServe computer node, point to All Tasks > Add/Remove Software and then click Add/Remove Software Configuration.
    • Select the CommServe Software Cache tab. The CommServe Cache Status for Packages should be Valid.
    • Click OK.
  1. Click the Tools tab, click Add/Remove Software, and then click Upgrade Software.
  2. Select the Physical Client Computers or Client Computer Groups checkboxes to upgrade the software on the selected client(s) available on the CommServe.

    Check the following options if applicable to your environment:

    • Reboot Client: Select this option if you are upgrading clients/agents which require a reboot after the upgrade.
    • Shutdown Oracle DB: Select Shutdown Oracle DB box, to stop the Oracle database services for Oracle iDataAgents.
    • Shutdown Internet Browser: If your environment requires an upgrade of JRE, any Internet Browser applications must be terminated before the upgrade.
  3. Click OK to upgrade software immediately. To automatically schedule the upgrade at a later time, see Automatically Schedule the Upgrade on Clients.

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.

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.

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.

How do I configure an additional setting in a cluster environment?

Based on the requirement, you can either configure an additional setting on a cluster group client or on a specific physical node. When you configure an additional setting on the cluster group client, the configuration applies to all of the physical nodes associated with the cluster group. For more information, see the following procedures:

Configuring an Additional Setting on a Cluster Group Client

Use the following steps to configure a additional setting on a cluster group:

  1. From the CommCell Browser, expand Client Computers, right-click the cluster_group_client and then click Properties.
  2. On the Client Computer Properties dialog box, click Advanced.
  3. On the Advanced Client Properties dialog box, click the Additional Settings tab.
  4. Click Add.
  5. In the Name box, type the name of the additional setting. Once entered, the Category and Type details will be populated automatically. Alternatively, you can click Lookup and search for the additional setting by typing the additional setting name in the Find box or scrolling through the list. Once found, double-click the additional setting from the lookup window.

    When you try to configure a additional setting on a cluster group,  the Category box will be populated with the following value:

    Machines\<Client>

    Do not modify this value. This additional setting will be configured on all the physical machines of the cluster group.

  6. Specify the values for Type and Value and click OK.
  7. Click OK.

Configuring an Additional Setting on a Physical Node

Use the following steps to configure an additional setting on a physical node:

  1. From the CommCell Browser, expand Client Computers, right-click the client that is associated with the cluster group, and then click Properties.
  2. On the Client Computer Properties dialog box, click Advanced.
  3. On the Advanced Client Properties dialog box, click the Additional Settings tab.
  4. Click Add.
  5. In the Name box, type the name of the additional setting. Once entered, the Category and Type details will be populated automatically.
  6. In the Category box, type Machines\client_name where client_name is the name of the physical node on which you want to configure the additional setting.
  7. Specify the values for Type and Value and then click OK.
  8. Click OK.
  9. If you want to configure an additional setting on a different physical node, repeat steps 1 through 8.

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 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 use the physical node interface for backups on virtual machines in a cluster?

After installing the software on the physical node, you can use the physical node interface for backups on virtual machines using one of the following methods:

Method 1: Executing the Qscript

Execute the SetClientProp.sql qscript on the client computer using the following steps:

  1. From the command prompt on the client computer, navigate to the software_installation_path\Base folder.
  2. Run the SetClientProp.sql qscript using the following command:

    qoperation execscript -sn SetClientProp.sql -si c=clientName -si UsePhysicalnode=y

Method 2: Using a Data Interface Pair

Configure a Data Interface Pair between the virtual machine and the MediaAgent. When configuring a data interface pair, make sure to use physical node's Network Interface Card (NIC) IP address for the Virtual Machine. See Data Interface Pairs - Getting Started for detailed information.

How does SnapProtect handle service group failover on a Veritas cluster?

After the cluster group client is configured in the CommCell Console, SnapProtect 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:

  1. Turns off firewall on the service group, and enables it on the active node.
  2. Notifies the CommServe database where the service group is active for effective resource allocation.
  3. If archiving/OnePass operations are configured, the plug-in switches the monitoring mount points to the active node to handle stub recalls.

What happens if I upgrade from a previous version of SnapProtect?

When you upgrade a physical node to a new version of SnapProtect, 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:

  1. From the CommCell Browser, go to Client Computers > cluster_group_client.
  2. Right-click the cluster group client, and then click All Tasks > Release License for Client.
  3. Click OK to continue.
  4. Click Yes to continue with the license release.