SAP on windows server 2012 hyper-v documentation June 2013

summary This documentation is applicable to Windows Server 2012 Hyper-V 3.0 and SQL 2012. Hyper-V 2.0 is not covered Proposed documentation is targeted to small and medium SAP on SQL Server customers only. Very large complex landscapes tend to be “custom” solutions H/W platform documented is 2 socket SandyBridge or IvyBridge ranging from 8-15 core. Documentation provides customers a “cookbook” to deploy SAP on Win/SQL on Hyper-V 3.0

1. Documentation Model Scenario I Scenario II Scenario III Scenario IV 4 deployment scenarios are documented Common SAP specific topics are documented across scenarios Private Cloud SAP Landscape Virtualization Manager (LVM) Scenario I Scenario II Scenario III Scenario IV HW+Net+SAN Hardware config + Network+disk P2V vs. sys copy Hyper-V 3.0 SD benchmark whitepaper Whitepaper on Hyper-V 3.0 Benchmark Security & Patching Monitoring Scenario III Config of CSV, vhd, datafiles HA/DR concepts Scenario IV System Copy + Backup/Restore Sizing 1 Cameron 2 3 4 Cameron 5 6 Cameron 7 8 9 Cameron

2. Scenario I – CONFIGURATION Simple implementation suitable for smaller customers or Dev/QAS All components are consolidated as 2 tier DB/CI on a single Hyper-V cluster comprised of n nodes. 1:1 mapping between SAP system and VM

3. Scenario II – separate prod & non-prod Simple design – suitable for medium size customers All components are consolidated as 2 tier DB/CI on a non-production and separate Production Hyper-V cluster comprised of n nodes. 1:1 mapping between SAP system and VM Separate Hyper-V cluster for non-prod and production

4. Scenario III – scalable suitable for medium to large size customers All components are consolidated on a non-production and separate Production Hyper-V cluster comprised of n nodes Multi-SID (A)SCS Windows Cluster is implemented Application server stacking is implemented 3 Tier concept provides much more scalable than 2 tier solutions AlwaysOn used to provide SQL Server HA More complex configuration but suitable for large systems

5. Scenario IV – Geocluster HA/DR suitable for medium to large size customers Provides HA/DR “in a box” All components are consolidated on a non-production and separate Production Hyper-V cluster comprised of n nodes Multi-SID (A)SCS Windows Cluster is implemented Application server stacking is implemented 3 Tier concept provides much more scalable than 2 tier solutions AlwaysOn used to provide SQL Server HA More complex configuration but suitable for large systems Hyper-V Replica use to synchronize VMs between data centers (if required). SAN storage replication also supported

6. VIRTUAL MACHINE CONFIGURATION Use only the following 4 predefined virtual machine sizes SAP application servers should only use virtual machine sizes 1 + 2 SQL Server can run on all 4 VM sizes Use the Virtual Machine landscape calculator Excel spreadsheet to design the VMs and landscape Review SAP on Microsoft Private Cloud chapter 9

6. VM Standard config: small Target use: Development systems, Solution Manager and very small test and production systems. Small config can also be used for ASCS clusters. DB size up to 320GB with full PAGE compression VM Properties: Single 10G network, 32GB RAM, 4 vCPU SAP DB Layout: 4 datafiles, 1x 5GB Log Tempdb Layout: 4 x 1GB datafiles, 1x 1GB Log VHDX: 4 x 20-100GB for SQL Datafiles + 10GB for Log file OS = Windows Server 2012 Standard Edition or higher DB = SQL Server 2012 SP1 or higher Note: when used as SAP application server only storage is 1 x 100GB VHDX for OS + SAP

7. VM Standard config: medium Target use: medium test and production systems. Medium VM can be used for both SQL Server and SAP application servers. Typically less than 500 users. DB size up to 640GB with full PAGE compression VM Properties: Dual 10G network, 128GB RAM, 8 vCPU SAP DB Layout: 8 datafiles, 1x 40GB Log VHDX: 4 x 50-200GB for SQL Datafiles + 50GB for Log file OS = Windows Server 2012 Standard Edition or higher DB = SQL Server 2012 SP1 or higher Note: when used as SAP application server only storage is 1 x 100GB VHDX for OS + SAP

8. VM Standard config: large (SQL only) Target use: Large production SQL Server databases. DB size up to 2TB with full PAGE compression VM Properties: >2 10G network, 192GB RAM, 16vCPU SAP DB Layout: 16 datafiles, 1x 200GB Log Tempdb Layout: 4 x 1GB datafiles, 1x 1GB Log VHDX: 4 x 100-400GB for SQL Datafiles + 400GB for Log file OS = Windows Server 2012 or higher DB = SQL Server 2012 SP1 or higher

9. VM Std config: Extra large (sql only) Target use: Extra large SQL Server use only. Not for SAP application servers. DB size up to >3TB with full PAGE compression VM Properties: >2 10G network, HW max GB RAM, HW max vCPU SAP DB Layout: 16 datafiles, 1x 600GB Log Tempdb Layout: 4 x 1GB datafiles, 1x 1GB Log VHDX: 4 x 100-1000GB for SQL Datafiles + 1TB for Log file OS = Windows Server 2012 Standard Edition or higher DB = SQL Server 2012 SP1 or higher

Appendix I – sql 2012 notes 1651862 - Release planning for Microsoft SQL Server 2012 1721480 - MSS: Support for system copy to SQL Server 2012 1676665 - Setting up Microsoft SQL Server 2012 1702408 - Configuration Parameters for SQL Server 2012 1684545 - SAP Installation Media and SQL4SAP for SQL Server 2012 Blogs: Windows Server 2012 Generally Available for SAP NetWeaver – April 2013 SAP on SQL General Update for Customers & Partners January 2013 SQL Server Column-Store available for all major SAP BW releases SAP High Availability in virtualized Environments running on Windows Server 2012 Hyper-V Part 1: Overview

Appendix II – general notes 1294762 - SCHEMA4SAP.VBS 1649078 - Disabling autostats for certain tables with Microsoft SQL Server 1565347 - SAP Systems Based on SAP NetWeaver 7.0 EHP3: SQL Server 1648817 - Disallow Page Level Locks for Microsoft SQL Server 62988 - Service Packs for Microsoft SQL Server 1609057 - SQL Server Setup Check Overview and Explanation 1238993 - Proportional File Auto-Growth with SQL Server 2008 1645041 - Changing the password of a MS SQL Server Login in SAP environment 1476928 - System copy of SAP systems on Windows 2008 (R2): SQL Server 1482275 - Setting Traceflags for SQL Server 133381 - Database-Hints in Open SQL for MS SQL Server 1581700 - PAGE compression support for DDIC & Hom./Het. System Copy 683447 - SAP Tools for MS SQL Server 151603 - Copying an SQL Server database 159316 - Reorganizing tables on SQL Server 1459005 - Enabling index compression for SQL Server 1006887 - Online index creation with SQL Server 2005, 2008 and 2008 R2 1145221 - JDBC driver exchange to Microsoft JDBC Driver

Appendix III: sap on sql server security The patching requirement for SAP on SQL is the same or less than that of UNIX/Oracle A maximum of 2 patching cycles per 12 month period is the target The total downtime per SAP system per year due to schedule patching is 10 minutes The total man-hours spent on patching the entire infrastructure is ~10 hours per year Please review the “Securing SAP on SQL 2012” Whitepaper http://blogs.msdn.com/b/saponsqlserver/archive/2012/05/28/sap-on-sql-server-security-whitepaper-released.aspx