280 likes | 470 Views
Symmetrix Partner Engineering Microsoft Update 2008. Txomin Barturen. Session Outline. Microsoft 2008 Updates Exchange Server 2007 SQL Server 2008 SharePoint Server 2007 Windows Server 2008 Hyper-V Hyper-V Server 2008 System Center Virtual Machine Manager. Microsoft Exchange Server 2007.
E N D
Symmetrix Partner EngineeringMicrosoft Update 2008 Txomin Barturen
Session Outline • Microsoft 2008 Updates • Exchange Server 2007 • SQL Server 2008 • SharePoint Server 2007 • Windows Server 2008 • Hyper-V • Hyper-V Server 2008 • System Center Virtual Machine Manager
Microsoft Exchange Server 2007 2008 was the year of the SAN vs DAS event
Microsoft Exchange Server and Virtual Provisioning • Exchange Server 2007 validated with DMX Virtual Provisioning • Exchange databases are Thin-Friendly • Expand when necessary • Support mailbox moves into environment • Can be used in conjunction with Quotas • Over-provision space, but limit utilization with quota • Later enable larger quota • No volume level changes required • Exchange log files are not a great option for Virtual Provisioning • Log files are created and removed over time • Windows NTFS allocations always (percentage may be small) come from free space • Over time, storage is fully allocated • Windows Server 2003 SP2 and Windows Server 2008 are better with allocations • White paper: • http://powerlink.emc.com/km/live1/en_US/Offering_Technical/White_Paper/H4286-implmntg-vrtl-provsng-emc-symmetrix-dmx-ms-exch-2007-wp.pdf?
DMX Enterprise Flash Drives (EFD) • Host and application transparent • Everything can benefit • FAST • Still have a price premium • Q4 50% discount! http://one.emc.com/clearspace/docs/DOC-7552 • FAST • Best, most obvious, return is for Random Read (miss) environments • FAST • For optimal performance big, wide bandwidth is required along the entire I/O path: LUNs, HBAs, FAs, DAs • FAST • For applications that have a special storage requirement (e.g. Exchange) there may be further value limitations • FAST
Exchange Server and Enterprise Flash Drives • Validated Exchange Server 2003 with EFD • EFD provide significant performance improvements for read requests • Write activity is dealt with primarily by Symmetrix Cache • Mailbox size will limit the total number of users configured for a given storage allocation on EFD • Transaction logs were not located on EFDs • Microsoft Exchange recommend to separate data and log for availability reasons • Sequential write stream is buffered by write cache • Optimized through write coalescing • In comparison testing, the same log devices were used for both EFD and HDD • Total Cost of Ownership affected by: • Reduction of short-stroked devices (if applicable) • Reduction in power consumption • Reduction in footprint and weight
Exchange on Enterprise Flash Drives • White paper: • http://www.emc.com/collateral/software/white-papers/h5833-symm-enterprise-flash-ms-exchange-wp.pdf
Symmetrix SRDF/S Concurrent J0 Write Symmetrix Enginuity 5772 (88.80) and 5773 introduce SRDF/S concurrent J0 write Multiple writes to a single volume across FAs Exchange Server generates multiple concurrent writes to the database Significantly improves performance in Synchronous environments 16 Servers (Jetstress) 24 SGs per server 58,000 IOPs
Microsoft SQL Server 2008 • Microsoft SQL Server 2008 includes enhanced versions • SQL Server Business Intelligence • SQL Server Reporting Services • SQL Server Analysis Services • SQL Server Database Engine • Significant draw of SAN based storage • Multi-TB SQL Server databases are now common • Reporting instances required in many new implementations • D/R capabilities required – draw for SRDF and SRDF/CE • Synchronous storage solutions required for multi-site, zero data loss
DMX / SQL at Microsoft adCenter • Key EMC Technologies • EMC Symmetrix DMX • EMC TimeFinder • EMC Replication Manager • Key Statistics • Vastly improved performance • Offloaded servers: scaled transactions from 2 Million to 100 Million on same servers • 120 TB nightly data migrations • Power / space savings helped delay datacenter upgrade http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=4000002051
Microsoft SQL Server and Virtual Provisioning • SQL Server 2005 validated with DMX Virtual Provisioning • SQL Server database files can be Thin-friendly • Require SQL Server Instant File Initialization • Blocks allocated as needed • SQL Server transaction log files are fully allocated • SQL Server will write zeros to entire log device • If the transaction log is size limited then it can be Thin-friendly • Keep space in reserve until required • MSIT moving SAP R/3 instance into a VP environment • White paper: • http://powerlink.emc.com/km/live1/en_US/Offering_Technical/White_Paper/H4287-implemtng-vrtl-prov-emc-symmetrix-dmx-ms-sql-srvr-05-wp.pdf?
Microsoft SQL Server and Enterprise Flash Drives • Host and application transparent • Everything can benefit • FAST • Still have a price premium • Q4 50% discount! http://one.emc.com/clearspace/docs/DOC-7552 • FAST • Best, most obvious, return is for Random Read (miss) environments • FAST • For optimal performance big, wide bandwidth is required along the entire I/O path: LUNs, HBAs, FAs, DAs • FAST • For OLTP applications where a single DB is shared amongst multiple users, there can be significant value • FAST
EFD : SQL Server 2008 OLTP Workload • EMC DMX4 Array • RAID5 - 3+1 • 4 physical devices • Log/Data on same physical devices • Database size (~300GB) • Random read and write for checkpoints / sequential log writes • 16 core server completely CPU bound • Sustained 12K IOPs
HDD : SQL Server 2008 OLTP Workload • EMC DMX4 Array • RAID 1+0 • 34 Physical Devices Data • 4 Physical Devices Log • Database size (~300GB) • Nearly same sustained IO’s with ~10x number of spindles • Higher latency • Slightly lower throughput
EFD Vs HDD : SQL Server 2008 OLTP • EFD • HDD
SharePoint Server 2007 • Storage based on SQL Server • SQL Server value/benefits apply • Whitepaper on D/R capabilities • Describes SharePoint configuration • Describes SharePoint components • Replication requirements • SRDF flavors • Outlines issues with mis-configured scenarios • E.g. Re-crawl • http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-006-888_a01_elccnt_0.pdf?
Microsoft Windows Server 2008 • Windows Server 2008 introduced • Corrected alignment (1 MB offset) • Enhanced NTFS/Disk functions • Grow/shrink volume features from Windows 2003 R2 • Enhanced VSS functions • Enhanced Windows Failover Clustering • SCSI-3 Persistent Reservations • Multiple Flavors: • Windows Server 2008 with Hyper-V – (and without) • Windows Server Core installation option • Microsoft Hyper-V Server 2008 • Windows Server Core w/ CLI • And of course Hyper-V itself
Microsoft Windows Failover Clusters • SRDF/CE enhanced to provide support for Windows 2008 functionality • Provides an automated, predictable, reliable solution for business continuity SRDF/S SRDF/A 64 Clusters MNS Shared Disk Quorum MNS w/ FSW Node Majority Node and Disk Majority Disk Only Node and FW Majority
Microsoft Windows Hyper-V • Opportunity for consolidation of all Microsoft applications • Same value as other virtualization solutions • Consolidate server • save rack space, power and cooling • Support for multiple storage options • FC, iSCSI and NAS • Requires SAN storage for many features and functions • High Availability: Windows Failover Clustering : SAN • VM Mobility: VDS/NPIV/iSCSI : SAN • VM Mobility: Live Migrate : SAN accelerated • Deployment scenarios: TimeFinder Clones/Snaps : SAN • En masse Cloning operations = Dynamic Datacenter capabilities
Microsoft Hyper-V Server • Standalone download – Free • No VM OS licenses included • Hyper-V Server (Parent Partition) provides: • Support for systems with up to 4 processors with 1, 2, or 4 cores • Support for systems with up to 32 GB of physical memory • Support for up to 128 virtual machines or as many will fit within 32 GB of memory (whichever comes first) • Hyper-V Server virtual machines provide: • 32-bit (x86) and 64-bit (x64) virtual machines • Up to 4 virtual processors per virtual machine • Up to 31 GB memory for all running virtual machines (1GB reserved for Hyper-V Server Parent Partition
Hyper-V Architecture Hyper-V Manager (runs in Parent partition) Parent Child Child Child Hypervisor Layer Physical Server
Microsoft System Center Virtual Machine Manager System Center Virtual Machine Manager (runs on dedicated server) Parent Parent Parent Child Child Child Child Child Child Child Child Child Hypervisor Layer Hypervisor Layer Hypervisor Layer
Hyper-V Availability and Mobility • High Availability and D/R • Provided by Windows Failover Clustering • Restart solution • Cannot pre-plan for outage • No persistence of state • Clusters must be configured • Limited to 16 nodes • Mobility • Dynamic allocations on external feedback • Performance and Resource Optimization (PRO) • Pre-planed operation • Can persist state • Nodes can be added dynamically • No logical limit • Solutions include • Windows Failover Clustering • SRDF/CE for Windows Failover Clustering • VDS Migration • NPIV Migration • Live Migration (Windows Server 2008 R2)
Hyper-V Mobility with VDS Parent Child Child SCVMMServer Parent Child Child Child Hypervisor Layer EMC VDSProvider Hypervisor Layer SCVMM initiates Move Hyper-V Source suspends VM Hyper-V Source dismounts VM LUN VDS Provider does masking/unmasking Hyper-V Target mounts VM LUN Hyper-V Target resumes VM
Hyper-V Best Practices • For current deployments • One-to-one relationship of VM to LUN • Enables granular migration and H/A • Provisioning for Applications • Follow the same storage rules as you have today • Drawbacks • Pass-thru devices • Offline to Parent: no performance counters for off-line disks • Counters in Child may be slightly incorrect due to time-slicing on CPUs
For more Microsoft information • ONE|EMC • http://one.emc.com/clearspace/docs/DOC-5993 • Central location of related documents • Discussion forums • Distribution lists • MSAT : Microsoft advisory team • MicrosoftExchangeTech • SQLDBTT