SAP ON WINDOWS SERVER 2012 HYPER-V
DOCUMENTATION
June 2013
SUMMARY
1.
2.
3.
4.
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
Sizing
Scenario
IV
System Copy +
Backup/Restore
HA/DR
concepts
Scenario
CSV, vhd,
datafiles
III
Config of
Monitoring
on Hyper-V
&
Security
Benchmark
3.0Patching
Whitepaper
Hyper-V 3.0
SD benchmark
whitepaper
config +
Network
P2V vs.
+disk
copy
sys
Scenario
IV
Scenario
III
Scenario
II
Scenario
I
1.
2.
HW+Net
Hardware
+SAN
1. DOCUMENTATION MODEL
4 deployment scenarios are documented
Common SAP specific topics are documented across scenarios
Private Cloud
SAP Landscape Virtualization Manager (LVM)
2. SCENARIO I – CONFIGURATION
1.
2.
3.
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
Development Systems
Test Systems
Production Systems
VM1 Dev ECC
DB/CI
VM4 QAS ECC
DB/CI
VM7 PRD ECC
DB/CI
VM2 Dev BW
DB/CI
VM5 QAS BW
DB/CI
VM8 PRD BW
DB/CI
VM3 Dev EP
DB/CI
VM6 QAS EP
DB/CI
VM9 PRD EP
DB/CI
2Tier VMs running DB+CI Development QAS and
Production share the same Windows Hyper-V Cluster
Hyper-V Hosts in Single Cluster
CSV Volumes Mounted on all Cluster Nodes – FCoE, FC or 10G iSCSI
3. SCENARIO II – SEPARATE PROD & NON-PROD
1.
2.
3.
4.
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
Test Systems
Development Systems
Production Systems
VM1 Dev ECC
DB/CI
VM4 QAS ECC
DB/CI
VM7 PRD ECC
DB/CI
VM2 Dev BW
DB/CI
VM5 QAS BW
DB/CI
VM8 PRD BW
DB/CI
VM3 Dev EP
DB/CI
VM6 QAS EP
DB/CI
VM9 PRD EP
DB/CI
2Tier VMs running DB+CI Development and QAS running
on dedicated Windows Hyper-V Cluster for non-production
2Tier VMs running DB+CI Production
Windows Hyper-V Cluster
Hyper-V cluster for non-prod
CSV Volumes Mounted on all Cluster Nodes – FCoE, FC or 10G iSCSI
Hyper-V cluster for Production
4. SCENARIO III – SCALABLE
1.
2.
3.
4.
5.
6.
7.
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
Development Systems
VM1 Dev
ECC DB/
CI
Test Systems
Production Systems
VM4 QAS
ECC DB/
CI
VM2 Dev
BW DB/
CI
VM5 QAS
BW DB/
CI
VM3 Dev
EP DB/CI
VM6 QAS
EP DB/CI
SQL AlwaysOn Sync
Replica ECC + EP
VM7
SQL Server
Node A
(ECC + EP)
VM8
SQL Server
Node B
(BW)
SQL AlwaysOn Sync
Replica BW
Multi-SID SAP ASCS Windows
Cluster with ERS
VM9
SAP (A)SCS Node A
ASCS ECC 00
ASCS BW 01
SCS EP 02
VM11
SAP App Server
ECC 00
BW 01
EP 02
VM12
SAP App Server
ECC 00
BW 01
EP 02
VM13
SAP App Server
ECC 00
BW 01
EP 02
VM10
SAP (A)SCS ERS
Node B
VM14
SAP App Server
ECC 00
BW 01
EP 02
VM15
SAP App Server
ECC 00
BW 01
EP 02
3 Tier VMs with DB ,ASCS and App Server Production Windows Hyper-V Cluster
Hyper-V cluster for non-prod
CSV Volumes Mounted on all Cluster Nodes – FCoE, FC or 10G iSCSI
Hyper-V cluster for Production
5. SCENARIO IV – GEOCLUSTER HA/DR
1.
2.
3.
4.
5.
6.
7.
8.
9.
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
Development
Systems
Test Systems
Production Systems
SQL AlwaysOn Sync
Replica ECC + EP
VM7
SQL Server
Node A
(ECC + EP)
SQL AlwaysOn Sync
Replica BW
VM8
SQL Server
Node B
(BW)
Multi-SID SAP ASCS Windows
Cluster with ERS
VM9
SAP (A)SCS Node A
ASCS ECC 00
ASCS BW 01
SCS EP 02
VM13
SAP App Server
ECC 00
BW 01
EP 02
VM14
SAP App Server
ECC 00
BW 01
EP 02
VM10
SAP (A)SCS ERS
Node B
VM15
SAP App Server
ECC 00
BW 01
EP 02
VM13
SAP App Server
ECC 00
BW 01
EP 02
VM14
SAP App Server
ECC 00
BW 01
EP 02
VM15
SAP App Server
ECC 00
BW 01
EP 02
3 Tier VMs with DB ,ASCS and App Servers – Geographically Dispersed
Windows2012 Hyper-V Geocluster
DWDM Dark Fibre between
DC1 and DC2
CSV Volumes Mounted – Storage Data Center 1
CSV Volumes Mounted – Storage Data Center 2
6. VIRTUAL MACHINE CONFIGURATION
1.
2.
3.
4.
5.
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
1.
2.
3.
4.
5.
6.
7.
8.
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
1.
2.
3.
4.
5.
6.
7.
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)
1.
2.
3.
4.
5.
6.
7.
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)
1.
2.
3.
4.
5.
6.
7.
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
1.
2.
3.
4.
5.
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-onsql-server-security-whitepaper-released.aspx