Basic requirements for installing Backup Exec (tm) for Windows Servers (BEWS) on a Microsoft Windows Cluster.

Article:TECH32702  |  Created: 2004-01-21  |  Updated: 2014-01-19  |  Article URL
Article Type
Technical Solution



Basic requirements for installing Backup Exec (tm) for Windows Servers (BEWS) on a Microsoft Windows Cluster.


Listed below are the requirements for installing Backup Exec for Windows on a Microsoft Windows Cluster:

1. Backup Exec (tm) supports two-node clusters for Windows NT, Windows 2000, Windows Server 2003, Microsoft Windows 2000 Advanced Server, and Windows Server 2003 Enterprise.

2. Two-node, four-node, and eight-node clusters are supported with Backup Exec for Windows NT, Windows 2000, and Windows Server 2003, and Microsoft Windows 2000 DataCenter and Windows Server 2003 DataCenter.

3. Backup Exec Cluster can be installed on a Windows Server 2003 majority node configuration. However, there must be a shared disk in the configuration in order for Backup Exec to share its database files between nodes. In this type of configuration, if the majority of the cluster nodes fail, then the entire cluster will fail. This configuration normally uses more than two nodes in the cluster configuration.

4. The controlling node and designated failover nodes must be online during installation of Backup Exec.

5. A unique IP address and a unique network name for the Backup Exec virtual server is required during installation.

6. During installation of a Backup Exec cluster, the shared disk should be owned by the node on which the installation is run. If a physical disk resource is used that belongs to another application, the Backup Exec Cluster Wizard will move all the resources that belong to the other application into the Backup Exec group. It is recommended that Backup Exec not be installed on the cluster quorum.

7. An individually licensed copy of Backup Exec for Windows Servers, as well as any applicable agents and options, is required for each node in the cluster as defined in the End User License Agreement. Enter a serial number for each node in the cluster (the cluster must have at least two nodes). When installing an evaluation version of Backup Exec, a cluster environment is automatically detected and serial numbers are not required.

8.  When you install Backup Exec clusters in a Storage Area Network (SAN) Shared Storage Option (SSO) configuration, all Backup Exec installations must have the same server configuration. Either all nodes should be database servers or all nodes should be secondary member servers connecting to the same primary.

9. All Backup Exec installations into a cluster must either be part of a single cluster group, or be locally installed on each node. If cluster-aware Backup Exec is installed in a cluster as well as a locally installed version of Backup Exec (not cluster-aware), then you cannot log on to the locally installed Backup Exec media server. It is only possible to logon using the Backup Exec virtual server name. To be able to log on to the locally installed Backup Exec media server, first use the Cluster Configuration Wizard to uninstall cluster-aware Backup Exec from all the nodes in the cluster.

10. When installing the Backup Exec SAN Shared Storage Option primary server to an existing SQL Server 2000 instance, then you must use the Backup Exec Utility to configure secondary cluster-aware Backup Exec media servers in the SAN.

11. Use the same account for Backup Exec services on all nodes in the cluster. If nodes in a cluster use Backup Exec and have different accounts, change the services to use the same account.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices