Requirements for clustering Backup Exec using Veritas Cluster Server

Review the following items before you cluster Backup Exec using Veritas Cluster Server:

  • 32-node clusters are supported with Backup Exec for the following operating systems: Windows Server 2003, Windows Server 2003 Enterprise and DataCenter, and Windows Server 2003 DataCenter.

  • An individually licensed copy of Backup Exec, as well as any applicable agents and options, is required for each active node in the cluster as defined in the End User License Agreement. You must enter a license key for each node in the cluster (the cluster must have at least two nodes).

  • Storage Foundation for Windows Servers High Availability server components must be installed on the cluster nodes.

  • A shared volume accessible by all nodes in the cluster.

  • The shared volume must be part of a dynamic cluster disk group.

  • During installation of a Backup Exec cluster, the node that runs the cluster wizard should have exclusive control over the shared volume.

  • The shared volume cannot reside on a disk with compression enabled.

  • Symantec highly recommends that you use the default database instance (MSDE) that is installed by Backup Exec if you plan to cluster Backup Exec.

  • Symantec also supports using a remote SQL Server instance to host the Backup Exec database. However, if you plan to use this scenario, review the following:

    Only one installed instance of Backup Exec can be installed into the remote SQL Server instance on a clustered node. All other installed instances of Backup Exec in the cluster must use the default Backup Exec MSDE database instance.


    You must run the Backup Exec cluster wizard on the cluster node that uses the remote SQL Server instance.

Requirements for clustering Backup Exec using Veritas Cluster Server