1. Virtualization Fundamentals for DBAs Joey D’Antoni February 3, 2015 DBA Fundamentals VC

2. Joey D’Antoni  Joey has over 15 years of experience with a wide variety of data platforms, in both Fortune 50 companies as well as smaller organizations  Principal Consultant, Denny Cherry and Associates  He is a frequent speaker on database administration, big data, and career management  He is the co-president of the Philadelphia SQL Server User’s Group  He wants you to make sure you can restore your data Joeydantoni.com

3. Virtualization Major PlayersTermsCosts and BenefitsTechnologyOptimizing SQL for a Virtual EnvironmentSummary

4. Major Virtualization Players

5. Virtualization Why did it happen?

6. It seemed like a good idea at the time…

7. Server Room Sprawl Server sprawlSQL sprawl Power and Cooling Issues in DCs Broader availability of SAN storage Cloud Computing

8. VM Terminology Guest—The virtual server running underneath the physical host and hypervisor (instance of an Operating System) Host—The physical server that your virtual machines run on Hypervisor—The underlying software that performs the load balancing and sharing of resources between guest operating systems

9. VM Terminology (cont’d) Thin Provisioning—Allowance in virtual environments to overallocate physical resources (more to come later) Deduplication—Process of compressing memory/disk space by saving only one copy of common bits vMotion/LiveMigration—Process which moves guest OS’s from host with high resource utilization to lower. Also an HA function with the hypervisor

10. Terminology (cont’d) Snapshot—A full point in time backup of your guest OS (very handy for upgrades/patches/code releases) Cloning—The process of building a gold guest image in order to rapid deployment

11. Costs  VMWare isn’t free  Memory Based Licensing  Hyper-V  Included with your Windows Server Licenses (amount of VMs vary based on edition)  SC-VMM, while not required is recommended

12. Benefits of Virtualization Lower cooling and powerHigher utilization of hardwareCan be used for HA configurationsRapid Deployment of new environmentsUse Gold Standard servers and rolloutSQL Server LicensingSnapshots

13. How this works… Host Hypervisor Guest One Physical Server

14. What does the hypervisor do?  Manages resources between guest O/S  Memory management  Backups  Failover and DR

15. Types of Hypervisors  Type 1—Native or Bare Metal. Run directly on host (VMWare ESX, Hyper-V)  Type 2—Run as process on local OS. (VMWare Workstation, Virtual Box)

16. VMWare Architecture

17. HA and DR

18. Typical Hardware  Virtualization hosts are the typical servers you might run SQL Server on.  2 x 4-6 core processors (Dual socket servers represent 80% of install base)  A Lot of RAM

19. Snapshots

20. Thin Provisioning  Allows over allocation of resources  Increases storage provisioning  Management console allows for easy management of this along with SAN  NOT GOOD FOR PRODUCTION DB SERVERS!!!

21. Shared Environment vs Dedicated Environment

22. Multi-Tenant Environments This can make monitoring and baselining your server more challenging You will want to have open communications with your VM administrators Ask for view access into vCenter—it will show you what else is going on in the environment

23. CPUs Can be over allocated Use servers with the newest chips—they are optimized for Virtual Workloads Maintain 1:1 ratio of physical cores to vCPU for production boxes For production workloads you may want to dedicate CPUs to the machine

24. Memory Management  Memory can be over allocated (but don’t do it for production!!!)  Hypervisor handles it by de-duplicating memory.  Host Page Files

25. Balloon Driver

26.  When hosts comes under memory pressure, VMWare reclaims memory from guests

27. Storage

28. I/O Concerns  Two choices of file types—VMFS (VMWare File System) and RDM (Raw Device Mapping)  Performance between two is similar  RDM is required for clustering  VMFS generally more flexible  Use Shared Storage (SAN) to get HA and DR functionality

29. I/O Concerns  Partition alignments still matters < Windows 2008  Work with storage team to monitor I/O— Hypervisors can have strange I/O patterns

30. Datastores It can be easy to overwhelm storage if not enough storage devices are presented Modern SANs tend to be designed with this in mind

31. Windows Server 2012  Introduces concept of “Storage Spaces”  Allows storage to be pooled and shared between multiple VM hosts  Can be created from non Microsoft platforms

32. Storage Spaces

33. Virtual Server

34. Virtualizing SQL Server  Use Trace Flag –T834—large pages enabled  Reserve memory for production workloads  Also reserve memory in Hypervisor for Prod Servers  Follow the same storage best practices you would for a physical box (Separate TempDB, Data, Logs)  Baseline IO performance

35. Virtualizing SQL Server  Think carefully about using lock pages in memory*  Enable optimize for ad-hoc workloads  DON’T OVERALLOCATE CPUs

36. Monitoring SQL Server  From the server perspective everything stays the same  Everything may not match at times  Ask for access to the vSphere client!  It’s the only way to have an overview into the broader system

37. Performance Issues  Troubleshoot as you normally would, then check VMWare  Similarly with a SAN—try to identify what you apps are sharing your resources  Can adjust load on the fly by using vMotion (or Live Migration)

38. Summary  Virtualization is the future, and the future is now!  Virtual servers work from a shared resource pool and that can impact your workloads  Identify changes you need to make to your SQL Servers for Virtual Environments  Get access to your virtualization management layer

39. Questions?

40. Contact Info  Twitter: @jdanton  Email: jdanton1@yahoo.comjdanton1@yahoo.com  Blog (slides): joedantoni.wordpress.com