X hits on this document

Word document

SAP with Microsoft SQL Server 2005: Best Practices for High Availability, Maximum Performance, and ... - page 11 / 76





11 / 76

SAP with Microsoft SQL Server 2005: Best Practices for High Availability, Maximum Performance, and Scalability7

Architectural considerations

The mySAP with SQL Server 2005 architectures are designed to provide maximum availability and to ensure reliability by offering multiple levels of failover support and redundancy including:

Failover clustering. SQL Server 2005 can run two to eight server nodes in a failover cluster to provide redundancy in the event of server downtime.

RAID. Common Redundant Array of Independent Disks (RAID) is used to provide redundancy in the event of a disk failure.

Networked storage. Storage Access Network and Networked Attached Storage (NAS) technologies can be designed with complete redundancy to ensure data integrity and avoid data loss. SQL Server 2005 is optimized for native integration with Storage Access Network hardware.

Failover clustering

mySAP with SQL Server 2005 architectures can take advantage of failover clustering. In SQL Server 2005, failover clustering offers a complete, fault-tolerant server solution that supports high availability and data integrity, and reduces the costs associated with downtime.

SQL Server 2005 failover clustering exploits Microsoft Windows Clustering Services (MSCS) to create fault-tolerant virtual servers that enable fast failover in the event of a database server or critical line-of-business (LOB) application failure. SQL Server 2005 supports two to eight servers as cluster nodes. In SQL Server 2005, support for failover clustering has been extended to SQL Server Analysis Services, Notification Services, and SQL Server replication.

The clustered servers are configured as shown in the following diagrams. A typical Microsoft clustering scenario includes running the SAP Central Instance (CI) on one of the cluster nodes and SQL Server 2005 on the other cluster node. In this case, if the primary node for SQL Server 2005 or for the SAP CI fails, or if that node is taken offline for maintenance, the clustered components will start on the active cluster node without a service interruption.

It is important to note that, when clustering is employed in a 64-bit computing scenario and SQL Server 2005 (64-bit) is used, SAP x64 application support is required.

For more information, see “Failover Clustering” in the Microsoft Developer Network (MSDN) Library at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_clustering_7t9v.asp.

Microsoft Corporation © 2005

Document info
Document views345
Page views345
Page last viewedFri Jan 20 02:46:07 UTC 2017