Ye Olde Cluster Curiosity Shoppe - SQLSupper 2014 Edition
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Ye Olde Cluster Curiosity Shoppe - SQLSupper 2014 Edition

on

  • 396 views

Welcome to the strange and mysterious world of SQL Failover Clustering and enter Ye Olde Cluster Curiosity Shoppe where we will reveal a miscellany of top tips, tricks and advice gained from nearly ...

Welcome to the strange and mysterious world of SQL Failover Clustering and enter Ye Olde Cluster Curiosity Shoppe where we will reveal a miscellany of top tips, tricks and advice gained from nearly two decades of installing and troubleshooting SQL Clusters.

Roll-up roll-up! Come and see :-

The "multi-headed" cluster.
The installation of Death.
The Zombie.
The Marie Celeste.
The indestructible network name.

And many more weird and wonderful exhibits.

Statistics

Views

Total Views
396
Views on SlideShare
394
Embed Views
2

Actions

Likes
0
Downloads
2
Comments
0

1 Embed 2

http://www.linkedin.com 2

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Ye Olde Cluster Curiosity Shoppe - SQLSupper 2014 Edition Presentation Transcript

  • 1. Ye Olde Cluster Curiosity Shoppe Mark Broadbent Principal SQL Consultant SQLCloud SQLCLOUD.CO.UK
  • 2. About Mark Broadbent “Possibly the hardest drinking DBA on the planet” “30 billion times more intelligent than a live mattress” Email: mark.broadbent@sqlcambs.org.uk Twitter: retracement Blog: http://tenbulls.co.uk PASS UK Regional Mentor Event Lead to the UK’s first ever SQLSaturday (Cambridge) Event #3 due on Sept 2014 (pre-con/s) and (Community day) https://www.facebook.com/groups/sqlsaturdaycambridge/ Cambridgeshire PASS Chapter UG Leader http://sqlcambs.org.uk
  • 3. Coming soon! SQLSaturday #281 Edinburgh Tha mo bhàta-foluaimein loma-làn easgannan SQLSaturday Edinburgh 2014 13th (pre-con) and 14th (free) June http://www.sqlsaturday.com/281 University of Edinburgh, Pollock Halls 18 Holyrood Park Road, Edinburgh, Scotland, EH16 5AY Come to my Pre-conference training day on Friday 13th June: “Real World SQL Server High Availability Masterclass”
  • 4. Agenda 2 Incredibly tenuous link between the Curiosity Shoppe and clustered scenarios! 3 The occasional demo fail 1 A quick introduction to Clustering 4 The best part of the presentation… beer o’clock
  • 5. A quick introduction to Clustering
  • 6. Standalone deployment of SQL Server/s Instance1 MSDTC Instance2
  • 7. Clustered deployment of SQL Server/s MSDTC *1 Install (New) Failover Cluster Instance1 Install (add) Install (add) MSDTC clustered deployment can vary greatly depending upon design considerations *1
  • 8. Clustered deployment of SQL Server/s MSDTC Install (add) Install (add) The installation to create a New Failover Clustered instance can be performed on any of the Cluster nodes Install (New) Failover Cluster Instance2
  • 9. Running Clustered Instances Failover Cluster Instance1 Failover Cluster Instance2
  • 10. Take a look at our Clustered Instance DEMO
  • 11. Welcome to Ye Olde Cluster Curiosity Shoppe!
  • 12. The Shrunken Head Cluster Role/ Group Failover Cluster Instance1 sqlserver1 10.0.0.15 One physical node but one (or very small number of) instances that you would have otherwise deployed as standalone. Useful for easy expansion of HA infrastructure when budget allows and abstraction of network name Windows Cluster is a single node only running a clustered instance
  • 13. Port o’ Plenty Failover Cluster Instance1 Port 1433 Failover Cluster Instance2 Port 1433 Failover Cluster Instance3 Port 1433 Failover Clustered Instances can be executed to all listen under the default SQL Server listening port. This can provide various benefits (and potential negatives). Remember there can only be one default instance!
  • 14. The Bearded Lady Failover Cluster Instance1 Failover Cluster Instance2 Each node sees all storage Each instance brings more clustered disks. This can result in too many cumulative disks and become unmanageable.
  • 15. Bearded Lady DEMO
  • 16. Many Headed Cluster Failover Cluster Instance1 Failover Cluster Instance2 Failover Cluster Instance3 Failover Cluster Instance4 One to many (unused) SQL Failover Clustered instances. Excellent for pre-testing Cluster node upgrades and testing database upgrade prior to risking production Failover Clustered Instance.
  • 17. “Cutting off one head” – upgrading clustered instance Fail test clustered instance onto upgraded node to upgrade instance/ databases If upgrade fails we can uninstall patch or at worst case evict node and rebuilt/ reinstall SQL instances. Our production instances have suffered zero downtime from a failed deployment Apply latest service pack
  • 18. The Marie Celeste New Cluster Storage for Instance 1 Failover Cluster Instance1 Cluster Group Fail across all nodes Cluster Groups can be easily created with little to no risk to the cluster. They are great for testing storage and other clustered resources ahead of time.
  • 19. The Marie Celeste DEMO
  • 20. The Zombie Cluster Role/ Group Dependency Failover Cluster Instance1 Failed Network Name causes dependent SQL Cluster Resource to fail. Forced online local service can return a temporary limited service Network Name SQL Service 10.0.0.15 Bring online
  • 21. The Indestructible Network Name Active Directory in Windows 2008 and above has a protection property In Windows 2003 you would need to Deny the Everyone group for the Delete and Delete Subtree permissions Deleted objects can be recovered from Tombstone in some situations.
  • 22. The Zombie DEMO
  • 23. Installation of Death! Cluster Role/ Group Failover Cluster Instance1 SSIS The Installation of SSIS has huge ramifications for a Cluster. What software and drivers will be required by packages? This is always a never ending moving set of goalposts and risk to Cluster stability. SSIS SSIS TNSnames.ora
  • 24. The Bodysnatcher Cluster Role/ Group Failover Cluster Instance1 Failed Clustered Instance across all nodes can spell panic (especially if the clustered set up is inherited). If the failure is serious and cannot be repaired a reinstallation on a new cluster can be attempted from old installation files.  New Cluster Role/ Group Install to nodes using reference files Install (New) Install (add) Install (add)
  • 25. The Bodysnatcher DEMO
  • 26. Montezuma’s Revenge Cluster Role/ Group Empty Cluster Role/ Group 10.0.0.15 10.0.0.15 Network Name Network Name Failover Cluster Instance1 Accidental move drags the whole dependent freakin’ lot! Failover Cluster Instance1
  • 27. The Scorpion Fish Cluster Role/ Group 10.0.0.15 Network Name Failure to identify all dependencies to resource prior to its removal can cause the whole failover clustered instance to unexpectedly fail. Whoopsie! Failover Cluster Instance1 “Hidden” or missed dependent to disk
  • 28. The Scorpion Fish DEMO
  • 29. In Summary… • Never attempt any operation on any cluster object *unless* you understand the impact. • Always validate anything you hear or read with your own testing in a virtual lab. • It is easy to make a mistake performing an operation or start to panic. Always take time to understand what you are doing and break it down into smaller steps if necessary. • It is worth repeating… DON’T PANIC!
  • 30. Thank you for listening and attending SQLSupper!