Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Share Point Ha And Dr


Published on

  • Be the first to comment

  • Be the first to like this

Share Point Ha And Dr

  1. 1. SharePoint Alphabet Soup – HA and DR<br />Greg Kamer<br />
  2. 2. Greg Kamer – The Mirazon Group<br />MCSE:2003, MCTS: MOSS 2007, WSS 3.0 <br />5 Years in IT<br />3 with SharePoint<br />Twitter: @gregkamer<br />Email: <br />About Me<br />
  3. 3. High Availability<br />Simply, keeping a system up as long as possible without interruption.<br />Redundancy is key here.<br />Tends to be more costly, but when weighed with mission critical apps, the costs may be easily justified.<br />Some Definitions<br />
  4. 4. Disaster Recovery<br />How can we recover, in terms of money, speed and manpower, a system that has been brought down.<br />Factors can be as small as someone tripping over a network cable and yanking it out to a large scale natural disaster.<br />Costs range from small to VERY high.<br />Definitions (cont’d)<br />
  5. 5. Considerations must be made for the roles at hand (WFE, Excel, Indexer, Query, etc)<br />Clustering v Load Balancing<br />No roles in SharePoint can be clustered, with the exception of the database “role”<br />Some roles will self-load balance<br />Discussion<br />High Availability in SP<br />
  6. 6. Web Front Ends are special <br />They must be load balanced to make them highly available<br />This is where SharePoint and the user(s) directly meet<br /><br />WFEs and Load Balancing<br />
  7. 7. Network Load Balancing – Microsoft<br />Free, but limited in functionality<br />Inclusive walkthrough -<br />Virtual Appliances<br />Some free, some paid. Your mileage may vary.<br />Hardware<br />F5, CoyotePoint, Cisco<br />Awesome features but pricey<br />Load Balancing WFEs<br />
  8. 8. When this is setup in SharePoint, you MUST specify a conversion load balancer.<br />There are no configuration settings once the service is in place.<br />Document Conversion<br />
  9. 9. Multiple ECS Servers can be used. <br />There is configuration and options, but they are few.<br />Excel Calculation Services<br />
  10. 10. Once a workbook is opened, the book uses the same server throughout the duration.<br />For further study:<br />ECS Cont’d<br />
  11. 11. This role cannot be made highly available.<br />There are ways to make it somewhat highly available, but it is not an automatic process and can tax resources.<br />Index<br />
  12. 12. The role can run on a WFE or on separate servers<br />The roles are made redundant by using multiple WFEs<br />If not on dedicated WFEs, then round robin is used to serve queries<br />Beware the dreaded “My query role runs on the index server, but he has no friends cause he doesn’t know how to share” scenario.<br />Query Role<br />
  13. 13. SQL Clustering – very highly available, but requires shared storage (SAN)<br />SQL Mirroring – not automatic failover for SharePoint, nor really high availability, but can be scripted for more-highly-available-than-not scenario<br />Database<br />
  14. 14. Can provide instant HA in some circumstances<br />Most any role can be virtualized *with exceptions of course*<br />DR can be factored in here as well.<br />Virtualization<br />
  15. 15. We all have a plan and we have all tested it, right? Right???<br />SharePoint has many facets with respect to DR. SQL, Server 2008, hardware and connectivity, etc<br />Disaster Recovery<br />
  16. 16. How do we look at SharePoint in terms of DR?<br />SQL?<br />Virtualization?<br />Redundancy?<br />Network Connectivity?<br />Backup and restore procedures?<br />Hot/warm/cold recovery sites?<br />Brainstorm<br />
  17. 17. CRUCIAL to any DR discussion. If you have no backups, you have no disaster recoverability.<br />Restore time and SLAs will determine the type of backups that may be required.<br />Backups<br />
  18. 18. Are available via the GUI (Operations -&gt; Backup)<br />Are really just database dumps<br />Important for Enterprise search-gets index file and DB at the same time<br />Not able to be scheduled!<br />STSADM –o backup<br />Able to be made a scheduled task<br />Can cause table locking issues on DB<br />Not good for large site collections<br />Third party (AvePoint, Idera, DPM, etc)<br />Backups<br />
  19. 19. SharePoint native backups not able to restore individual sites, lists, or items (without a lot of hassle!)<br />Third party tools must be used for that<br />SPD can backup sites…but not the cleanest way to do it.<br />Recycle Bin – Can save your bacon!<br />Backups Cont’d <br />
  20. 20. Creating a mirror farm.<br />Database mirroring or log shipping<br />Backup and restores<br />Third party mirroring tools<br />AvePointDocAveHigh Availability -<br />Other DR considerations <br />
  21. 21. Plan for Redundancy – MSFT Whitepaper<br />Case Study of High Availability for SharePoint Server by Using Virtualized Environments and Database Mirroring – MSFT Whitepaper<br />SharePoint Disaster Recovery Guide By John Ferringer and Sean McDonough<br />Further Reading<br />
  22. 22. SharePoint Backup and Disaster Recovery – Joel OlesonTechEd 2008 PPT<br />Differences between Log Shipping and Mirroring<br />More Reading<br />
  23. 23. Q&A<br />Please fill out your evaluations<br />Don’t be afraid to play, it’s a resilient platform.<br />Thank you!<br />