Your SlideShare is downloading. ×

WFCI Storage Introduction

1,161

Published on

Here is the session that I gave on November 26th on SQLPort, a PASS chapter in Portugal.

Here is the session that I gave on November 26th on SQLPort, a PASS chapter in Portugal.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,161
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. WFCI - Storage Introduction What options do we have? Prepared by Murilo Miranda November, 2013
  • 2. About Me Murilo Miranda DBA @ The Pythian http://www.sql.pt/ Group @murilocmiranda http://pt.linkedin.com/in/murilomiranda/ 2 © 2013
  • 3. Agenda • WFC Overview. • WFCI Supported storage types: – Local Disk. – SMB File Share. – Shared Storage. – Clustered Shared Volumes. • Conclusion • Questions and Answers. 3 © 2013
  • 4. Windows Failover Cluster Overview 4 © 2013
  • 5. WFC – The advantages • In a SQL Server perspective: 5 – The WFC’s role is to make the instance highly available (WFCI). – Protects from hardware failures. – Applying service packs and hotfixes are less impactful. – It’s transparent for the applications/users connecting to the © 2013
  • 6. WFC – Handicaps • Still in a SQL Server perspective  : – Expensive than a standalone installation. • In € and effort: – More hardware. – More maintenance. – It’s a HA solution only. • No performance improvements. 6 – Doesn’t guaranties you © 2013
  • 7. Standalone instance 7 © 2013
  • 8. Standalone instance 8 © 2013
  • 9. Standalone instance HOSTNAME • One hostname. 9 © 2013 Pythian
  • 10. Standalone instance HOSTNAME • One hostname. • One or more IP addresses. 10 © 2013
  • 11. Standalone instance HOSTNAME • One hostname. • One or more IP addresses. • One or more disks. 11 © 2013
  • 12. Standalone instance HOSTNAME • One hostname. • One or more IP addresses. • One or more disks. 12 © 2013
  • 13. HOSTNAME Standalone instance 13 © 2013
  • 14. HOSTNAME Standalone instance 14 © 2013
  • 15. HOSTNAME Standalone instance 15 © 2013
  • 16. Clustered instance e m am e stnna st H l Hoo oc a l LLoca mee tnnam ta s Hoos cc l H ooaal LL Failover Failover Cluster Cluster 16 © 2013
  • 17. Clustered instance mee tnnam ta s Hoos cc l H ooaal LL HOSTNAME Failover Cluster Failover Cluster e m am e stnna st o l HHo oc a l LLoca IP IP Assigned Assigned Storage Storage 17 © 2013
  • 18. Clustered instance Failover Cluster Failover Cluster e m am e stnna st o l HHo oc a l LLoca HOSTNAME mee tnnam ta s Hoos cc l H ooaal LL IP IP Assigned Assigned Storage Storage 18 © 2013
  • 19. Clustered instance Failover Cluster Failover Cluster e m am e stnna st o l HHo oc a l LLoca HOSTNAME mee tnnam ta s Hoos cc l H ooaal LL IP IP Assigned Assigned Storage Storage 19 © 2013
  • 20. Clustered instance Failover Cluster Failover Cluster e m am e stnna st o l HHo oc a l LLoca HOSTNAME mee tnnam ta s Hoos cc l H ooaal LL IP IP Assigned Assigned Storage Storage 20 © 2013
  • 21. Clustered instance • The connection “is made to” the hostname assigned to the SQL Server role. 21 © 2013
  • 22. Clustered instance • The connection “is made to” the hostname assigned to the SQL Server role. • The cluster service redirects the connection to the appropriate (active) node. 22 – Where the SQL Server service is UP and © 2013
  • 23. WCFI supported storage types What is supported for the database files. 23 © 2013
  • 24. WCFI supported storage types • For SQL Server, we have four options: – Local Disk • From SQL Server 2012 24 © 2013
  • 25. WCFI supported storage types • For SQL Server, we have four options: – Local Disk • From SQL Server 2012 – SMB File Share 25 © 2013
  • 26. WCFI supported storage types • For SQL Server, we have four options: – Local Disk • From SQL Server 2012 – SMB File Share – Shared Storage 26 © 2013
  • 27. WCFI supported storage types • For SQL Server, we have four options: – Local Disk • From SQL Server 2012 – SMB File Share – Shared Storage – Clustered Shared Volumes • From SQL Server 2014 27 © 2013
  • 28. Local Disk • In a clustered instance it’s possible to store the TempDB into a local disk. 28 © 2013
  • 29. Local Disk • In a clustered instance it’s possible to store the TempDB into a local disk. • This local disk is not a cluster resource, so, this is not an option to user database files. 29 © 2013
  • 30. Local Disk • What are the benefits in have the TempDB stored in a local disk? 30 – More flexibility to chose the storage type. • Utilize disks with a higher rotational speed. – TempDB will utilize a different path than user databases to access data and log files. • Less congestion and contention on shared © 2013
  • 31. Local Disk – We can take advantage of PCIe. • At least 6 times the speed of traditional PCI. – More throughput than a disk interface or HBA. 31 © 2013
  • 32. Local Disk • Fusion-IO, OCZ and LSI Corp products are options. – Fusion-IO is the first firm to provide a direct PCI Express storage solution that doesn’t utilize an internal storage interface like SATA, but is not bootable. 32 © 2013
  • 33. Local Disk • Good article about PCIe and SSDs: “Three PCI Express-Based SSDs: When SATA 6 Gb/s Is Too Slow” – http://goo.gl/dhDaTy 33 © 2013
  • 34. SMB File Share • SMB 3.0 was introduced with Windows Server 2012. – It brought several significant changes to add functionality and improve SMB performance. • System and User DBs can be installed with SMB file server as a storage option. 34 – This applies to both SQL © 2013
  • 35. SMB File Share • Windows Server 2008 (SMB 2.0) – Durability, which helps recover from temporary network glitches. • Windows Server 2008 R2 (SMB 2.1) – Significant performance improvements, specifically for SQL OLTP style workloads. • Windows Server 2012 (SMB 3.0) 35 – Support for transparent failover of file shares © 2013
  • 36. SMB File Share • Supported Universal Naming Convention (UNC): – ServerNameShareName – ServerNameShareName • Not supported UNC: – Loopback path: • localhost.. or 127.0.0.1... – Administrative shares: • servernamex$ 36 – Other UNC path formats like ?x: © 2013
  • 37. SMB File Share • SMB protocol version is transparent to SQL Server. • The SQL Server engine and SQL Server agent service accounts should have FULL CONTROL share permissions and NTFS permissions on the SMB share folders. 37 © 2013
  • 38. SMB File Share 38 © 2013
  • 39. SMB File Share 39 © 2013
  • 40. SMB File Share • Network performance starts to be more than critical! – Consider use a dedicated network to access the share. • We will need to monitor the file share performance. 40 – Physical disk counters. – Memory. – CPU. © 2013
  • 41. SMB File Share • This option is not so good as SAN, but we can take advantage in few points: – In non-prod/DR servers. – Light databases. – Emergency/Temporary storage. – Database migrations. 41 © 2013
  • 42. Shared Storage • Shared storage allows direct disk access from multiple computers simultaneously. – All nodes of the WFC are physically connected. – Only the active node is able to access the disk. 42 © 2013
  • 43. Shared Storage • Shared storage allows direct disk access from multiple computers simultaneously. – All nodes of the WFC are physically connected. – Only the active node is able to access the disk. • A shared storage allows connections on either: 43 © 2013
  • 44. Shared Storage • SAN – Storage Area Network. 44 – Network to connect systems and storage for the purpose of transmitting storage I/O. • Based on Fiber Channel, iSCSI or FC over Ethernet (FCoE). • Support speed up to 16 GB/s • Centralizes storage and management. © 2013
  • 45. Shared Storage HP EVA 3000 45 © 2013
  • 46. Shared Storage IP Network IP Network Clients 46 FC SAN FC SAN Servers Storage Arrays © 2013
  • 47. Shared Storage • iSCSI Initiator: 47 © 2013
  • 48. Shared Storage • Disk Management: 48 © 2013
  • 49. Shared Storage • FC manager: 49 © 2013
  • 50. Shared Storage 50 © 2013
  • 51. Shared Storage • Be careful with dependencies! – Adapt your disk strategy to you cluster configuration. 51 © 2013
  • 52. Shared Storage W2012SQL01 52 W2012SQL02 © 2013
  • 53. Shared Storage W2012SQL01 53 W2012SQL02 © 2013
  • 54. Shared Storage W2012SQL01 54 W2012SQL02 © 2013
  • 55. Shared Storage 55 © 2013
  • 56. Shared Storage 56 © 2013
  • 57. Shared Storage 57 © 2013
  • 58. Shared Storage W2012SQL01 W2012SQL02 SAN 58 © 2013
  • 59. Shared Storage W2012SQL01 W2012SQL02 SAN 59 © 2013
  • 60. Clustered Shared Volume • CSV was being used to facilitate Virtual Machines management. – Supported since Windows 2008 R2. • Clustered Shared Volumes (CSV) could be a solution to increase the HA! 60 © 2013
  • 61. Clustered Shared Volume • How it works? – CSVs are still on SAN. – The difference is the way they’re managed. 61 © 2013
  • 62. Clustered Shared Volume • How it works? – CSVs are still on SAN. – The difference is the way they’re managed. • Only one node is the owner – Coordinator Node – CN can be any node, even if is not the SQL active node. 62 © 2013
  • 63. Clustered Shared Volume • How it works? – CSVs are still on SAN. – The difference is the way they’re managed. • Only one node is the owner – Coordinator Node – CN can be any node, even if is not the SQL active node. 63 • The CN uses SMB (Server Message Blo ck) to manage the I/O between the storage and all the cluster nodes. © 2013
  • 64. Clustered Shared Volume • How it works? – CSVs are still on SAN. – The difference is the way they’re managed. • Only one node is the owner – Coordinator Node – CN can be any node, even if is not the SQL active node. 64 • The CN uses SMB (Server Message Blo ck) to manage the I/O between the storage and all the cluster nodes. © 2013
  • 65. Clustered Shared Volume • How it works? – CSVs are still on SAN. – The difference is the way they’re managed. • Only one node is the owner – Coordinator Node – CN can be any node, even if is not the SQL active node. 65 • The CN uses SMB (Server Message Blo ck) to manage the I/O between the storage and all the cluster nodes. © 2013
  • 66. Clustered Shared Volume W2012SQL01 W2012SQL02 Coordinator Node SAN 66 © 2013
  • 67. Clustered Shared Volume W2012SQL01 W2012SQL02 Metadata write Request Coordinator Node SAN 67 © 2013
  • 68. Clustered Shared Volume W2012SQL01 W2012SQL02 Metadata write Request Coordinator Node Me tad ata wri te SAN 68 © 2013
  • 69. Clustered Shared Volume W2012SQL01 W2012SQL02 Metadata write Request Coordinator Node Data I/O 69 Me tad ata wri te SAN © 2013 Data I/O
  • 70. Clustered Shared Volume • Advantages: – The storage is accessible from all nodes. • To read and write! • SQL Server files are locked by the SQL process. – Helps to increases the availability rate. • The failover proccess faster. 70 – No need to mound disks. © 2013
  • 71. Clustered Shared Volume • With CSV, another path to the shared storage is opened, helping to increase the availability. – This alternative path is opened in case of a fail. – The cluster will use the less costly path to perform the I/O operations. 71 © 2013
  • 72. Clustered Shared Volume W2012SQL01 W2012SQL02 SAN 72 © 2013
  • 73. Clustered Shared Volume W2012SQL01 W2012SQL02 I/O request Data I/O 73 SAN © 2013
  • 74. Clustered Shared Volume • CSV is a "NTFS reparse point”, so it’s presented like a mountpoint. – Is not mounted as a disk (not assigned to a letter). – Accessible via %SystemDrive %ClusterStorage. 74 © 2013
  • 75. Conclusion • Consider the TempDB in a local disk, when designing a SQL Server 2012 solution. 75 © 2013
  • 76. Conclusion • Consider the TempDB in a local disk, when designing a SQL Server 2012 solution. • For non-mission critical instances, SMB File Share is a great option! – Also useful for emergencies. 76 © 2013
  • 77. Conclusion • Consider the TempDB in a local disk, when designing a SQL Server 2012 solution. • For non-mission critical instances, SMB File Share is a great option! – Also useful for emergencies. • Shared Storage is expensive, but still the best solution. 77 © 2013
  • 78. Conclusion • Consider the TempDB in a local disk, when designing a SQL Server 2012 solution. • For non-mission critical instances, SMB File Share is a great option! – Also useful for emergencies. • Shared Storage is expensive, but still the best solution. 78 © 2013
  • 79. Thank you – Q&A To contact murilo.miranda@gmail.com To follow http://www.sql.pt/ @murilocmiranda http://pt.linkedin.com/in/murilomiranda/ 79 © 2013

×