share point high availability presentation (ron charity) proposed final 1192009
TRANSCRIPT
BIO
Ron CharityA Principle Consultant with HP. He has 20 + years in infrastructure and application consulting for fortune 500 firms. He has experience working in the US, Canada, Australia and Europe. He has SharePoint technologies experience dating back to 2000 (Tahoe). Currently he is responsible for a large global SharePoint environment consisting of several farms that service 140 countries. Additionally, he is responsible for guiding and directing many aspects of the service, providing product and service guidance, architecture, quality assurance, service management and product direction.
Abstract
• With SharePoint becoming more entrenched in organizations its importance has increased significantly.
• SharePoint might not be directly linked to revenue generation in your organization but it’s most likely become a tool that people use daily and when there is a failure or data loss, you hear about it.
• The target audience for this presentation is individuals looking for guidance specific to high availability from a holistic point of view.
• This presentation delivers a comprehensive summary view of SharePoint High Availability from managing user expectations, establishing procedures and policy and technology options.
Agenda
• What is high availability• Where to focus• Risk planning• Stakeholder expectations• Technology components• Governance• Baselining and ongoing capacity management• People, process and policy• Q&A
What is high availability?
• Service level agreements
– Recovery Point Objective (RPO)
• Acceptable data loss
– Recovery Time Objective (RTO)
• Acceptable downtime
– Uptime
• Measure of uptime usually as percentage %99.99
What is high availability?
• Meeting stakeholders expectations:
– It’s a combination of people, process, policy and technology
– Meeting peoples expectation of SharePoint's availability and performance
– Regulatory / Records Management requirements
– Addressing people tolerance for downtime (outages, maintenance windows, data loss)
– Cultures tolerance for downtime and lost data
Stakeholder expectations
• Key points:– Know your stakeholders – don’t assume
– They will most likely live in IT and the business –there will be several
– If you have external collaboration, business partners, contractors and customers can be added to your list
– Pay close attention to gaps between expectations and what's actually deliverable
– Warning - the bigger the gap, the more pain!
Where to focus
• SLAs
• Risk planning
• Technology– Infrastructure
– Applications
• People, Process and Policy
• Testing – Quality Assurance
• Third parties
Risk planning
• You have visibility of SharePoint (Tip)
• Risk planning brings multiple points of view
• What are the known risks?
• What don’t you see?
• What– can you control?
– cant you control?
Network
• General– Network, Design speed, reliability, resilience…– Monitoring and reporting
• Risks– Attacks (Hack, DOS, Virus)– Capacity issues (peak periods, spikes)– Regional network capacity– Outsourcing (Shared environment,
control…)
• Best practices– Content caching globally for consistent experience– Farm traffic isolated – client and farm/operational traffic– Monitoring and capacity planning
SharePoint
• Farm topology– Architect based on SLA– Medium or large farm (Multiple WFE and index)– SQL Server cluster (A/P)– Standby farm (For outages and updates gone awry)
• Risks– Component, server or farm failure– Caching not optimized– Customizations– Backup and recovery– Content life cycle
• Best practices– Architect for SLA and compliance needs– Implement caching – SharePoint and WAN– Previsioning and information architecture in sync– Isolate customizations – Backup and recovery– Archive solution for sites
SQL Server
• SQL Server (is the heart of SharePoint)– Architect based on SLA for SharePoint– Cluster A/P– Requires an optimized design and maintenance plan– Aggressive monitoring and reporting
• Risks– Shared infrastructure– SQL Server, network and SAN not optimized– Maintenance and monitoring plans
• Best practices– Cluster – start with A/P– Implement RAID 10 – Isolate the databases and logs– Pre-allocate your databases (100GB)– Performance and resilience testing– Aggressive monitoring and reporting and maintenance plans
Servers and Storage
• Servers– Optimized for role– Impact to datacenter (Space, AC and Power)– Impact on outsourcing
• Risks– Not optimized for SharePoint (CPUs, RAM, NICs)– Proximity to user base (Wan latency, performance)– Outsourced (Shared infrastructure, lack of control…)– No IOP guarantees (SAN bottlenecks lead SQL issues)– Operational job overlap (performance degradation and
or brief outages)
• Servers and Storage– Leverage venders R&D– Build in redundancy where possible– RAID 10 for high I/O DBs (TempDB, Search, Logs)– Dedicated SAN If you are not able to obtain IOP performance guarantees– Use 64k blocks (Windows and SAN)– Make sure you have experienced SQL and SAN administrators
Governance
• A program for bringing stakeholders together and making key decisions
• Its about people not tools…
• It’s a forum for communication and understanding
• Stakeholders utilize decision framework that aligns with business and technology guidelines
• Tools are used to record items, issues, risks, decisions and communicate them
• Very difficult to get right unless it’s a top down program
Baselining and capacity management
• High availability isn't just redundancy…
• Its also about capacity / performance
• Baseline the performance or your applications day one – in QA
• Have a plan for proactively managing capacity
• Monitor and assess aggressively against plan
• More information– http://technet.microsoft.com/en-
us/library/ff758659.aspx
– http://technet.microsoft.com/en-us/library/ff608068.aspx
People, Process and Policy
• SLA for clients and between parties– Expectations documented– Performance, provisioning and
availability metrics– Responsibilities of all parties– Required skills and training– Documented and communicated
• Capacity and performance planning– Capacity projections– Baseline of performance– Plans and reports documented
People, Process and Policy
• Administration and Operational procedures
– How to, FAQ, roles and responsibilities
– Documented procedures and policy
– Documented and communicate
• Human resources
– Formalize
– Communicate and coach
– Measure and enforce
People, Process and Policy
• Training and mentoring
– Skills an experience
– Required courses
– Mentoring and knowledge sharing
• Monitoring
– Monitor service and report
– Must be two way and open
– Cross check with capacity plan ongoing
– Status reporting to stakeholders
Best Practices
• Governance program
• SLO/SLA negotiated and documented
• Proactively manage expectations / risks / educate / network
• Global user community - plan for multiple time zones
• Redundancy built into SharePoint and related systems
• Rebuild / recovery tested and documented
Best Practices
• Technology designs well though out, detailed and based on factual information
• Performance baseline and resilience testing
• Risk plan for what you cant control
• Human resources to manage people aspects
• Third party management
• Remember Staples / Business Depot (Easy)
Additional Reading
• SharePoint 2010 Disaster recovery guide– ISBN 1435456459
• Pro SQL Server 2008 Failover Clustering– ISBN 1430219661
• SharePoint backup and recovery– http://www.sharepointpromag.com/article/sharepoint/sharepoi
nt-2010-backup-recovery-plan-how-to-140201
• SharePoint Conference 2011 – SPC387 - Leveraging AlwaysOn in SQL Server Denali with
SharePoint 2010• http://cdn.tri-digital.com/spc/videos/SPC387.wmv.zip
– SPC309 - Backup and Recovery for SharePoint 2010• http://cdn.tri-digital.com/spc/videos/SPC309.wmv.zip
Q&A
• 15 minute Q&A
• Text chat
• Contact information?