Requirements for clustering Backup Exec in a Microsoft Cluster Server environment
The following are requirements for clustering Backup Exec:
-
Veritas strongly recommends that if you plan to cluster Backup Exec, use the default database instance (MSDE) that Backup Exec installs.
-
Veritas supports using a remote SQL Server instance to host the Backup Exec Database.
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.
Note: You must run the Backup Exec cluster wizard on the cluster node that uses the remote SQL Server instance.
-
For off-host backups that use the hardware provider in a Microsoft cluster (MSCS) environment, the Backup Exec server and the remote computer must be in different cluster groups. The cluster applications cannot support device logical unit numbers (LUNs) that have duplicate signatures and partition layouts. Therefore, the snapshots containing the LUNs must be transported to a host or remote computer that is outside the cluster.
-
For Windows Server 2008 and later, you must use the same level of operating system on the Backup Exec server and on the computer that hosts the remote SQL Server instance in the following scenarios:
-
To use a remote clustered SQL Server instance to host the Backup Exec Database
-
To use the Backup Exec Utility to reconfigure the clustered Backup Exec installation or the remote clustered SQL Server instance
-
For Windows Server 2012 and later, Backup Exec supports parallel backups across Cluster Shared Volumes (CSV) and cluster nodes.
Backup Exec does not support virtual machines that store data on both CSVFS and NTFS volumes.
For specific operating system requirements, see the Backup Exec Software Compatibility List at the following URL:
http://www.veritas.com/docs/000017788
Related information