sp2010 high availlability
DESCRIPTION
High Availlability für SharePoint 2010TRANSCRIPT
SharePoint 2010 – High Availability
Thierry GasserTechnical Specialist Collaboration [email protected]
Agenda
High Availability versus High ScalabilitySharePoint classic architecture for High ScalabilitySharePoint High Availability ArchitectureVirtualization info.Q&A
High Availability / High Scalability“High availability is a system design approach and
associated service implementation that ensures a prearranged level of operational performance will be met during a contractual measurement period.”
Wikipedia definition
Availability % Downtime / Year
Downtime / Month
Downtime / Week
99% 3.65 days 7.20 hours 1.68 hours
99.9% 8.76 hours 43.2 minutes 10.1 minutes
99.99% 52.56 minutes 4.32 minutes 1.01 minutes
99.999% 5.26 minutes 25.9 seconds 6.05 seconds
99.9999% 31.5 seconds 2.59 seconds 0.61 secondsDon’t mix high availability (Farm/Service replication) and high scalability (Extend the farm to have better performances). In some circumstances they overlap.
Measuring Availability
525,600 minutes/ year
40 min for WFE failovers
99.999%20 min for SQL failovers
5 min for maintenance window overruns
4 hours/month of patches
100%99.99%99.9%99%
http://technet.microsoft.com/en-us/library/cc748824.aspx
RPO/RTO/SLA RequirementsRecovery Point Objective (RPO)
Acceptable amount of data loss measured in time
Recovery Time Objective (RTO)Duration of time within a business process must be restored after a disaster
Service Level Agreements (SLA)Agreed to levels of service usually between vendors, suppliers and clients or inter organizational departments
RPO RTO
Time
HA is linked to:
Data Center Considerations for HAAvailable Budget
Design for redundancy and availability before performance. -> Better to have sufficient instances of a role then high performance points of failure.
Generally you are constrained by the Hardware on hand or available for purchaseFull DR (Data Recovery) failover is rare, have redundant roles in your farm design.
Choose an Availability StrategyIts all about balancing costs versus
business risk
Strategies:
$ - Fault tolerance of hardware components
$$ - Redundancy and failover between server roles within a farm
$$$ - Redundancy and failover between farms
What is a SharePoint Farm?
What is a SharePoint® Farm?A collection of one or more SharePoint Servers
and SQL Servers® providing a set of basic SharePoint services bound together by a single configuration database in SQL Server
Key Components (3 layers):
• Web Front End (WFE) Servers:o WSS / SharePoint Foundationo Web Application Service
• Application Servers:o Search Servero Excel Serviceso PerformancePoint Serviceso Access Serviceso Visio Services
• SQL Server
SharePoint 2010 Tiers - HSWFE Tiers – Some changes, some optimizationApp Server Tiers – Many changesSQL Tiers – Some changes, heavy optimization
Architecture Typical implementationInformation for High Scalability
available on: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=fd686cbb-8401-4f25-b65e-3ce7aa7dbeab&displaylang=en
Different types of farms can consume federated services. Some may only consume a subset of services while others may not be running any service applications.
Alternatively you may decide to have a dedicated farm or multiple farms to host the federated services.
You many do this for a variety of reasons, scale, division of management, or even SLA differences in the services.
A single farm can be built out with all service applications and core services like Usage and Health Data Collection and InfoPath Forms Services.
The farm can scale to 100,000’s of users and meet most corporate business needs.
Isolation is limited to the web application level which may not meet some requirements.
If it becomes necessary to build additional farms, you can do so and still share some services.
Note only six services can be federated and of those six the User Profile service only supports federation across a LAN vs. a WAN.
We do not recommend federating Web Analytics, the service application has limitations with regards to scale.
Services Farm hosting Federated Services
Single Farm vs. Multiple Farms
UserProfile SearchManaged
Metadata
BusinessData
Connectivity
SecureStore
Service
ExcelServices
AccessServices
WordViewing
PowerPointServices
InfoPathUsage
& HealthData Collection
WordAutomation
Services
WebAnalytics
Project
Single Farm with all service applications
ExcelServices
AccessServices
WordViewing
PowerPointServices
InfoPathUsage
& HealthData Collection
WordAutomation
Services
WebAnalytics
Project
Farm consuming all federated services
Farm consuming some federated services
BusinessData
Connectivity
SecureStore
Service
ExcelServices
AccessServices
WordViewing
PowerPointServices
InfoPathUsage
& HealthData Collection
WordAutomation
Services
WebAnalytics
Project
InfoPathUsage
& HealthData Collection
Farm consuming only federated services
WebAnalytics
Architecture tips for High Scalability (HS)Sharepoint can easily scale (recommended
max 8 WFE/farm) Antivirus do not activate on temp file and Search indexService can be started and dispatch on mostly each farm machine.Some services can be shared over farms to scaleMonitoring is necessary for production to validate architecture choices. http://www.learningsharepoint.com/2010/10/16/monitoring-sharepoint-2010-%e2%80%93-tutorial/
Infra size must not be underestimated, info on:
http://technet.microsoft.com/en-us/library/cc261700.aspx http://technet.microsoft.com/en-us/library/cc263199.aspx
Web servers – Use multiple servers and load balancing
App servers – Enable SharePoint services on multiple servers
However, SharePoint has some additional availability considerations
Service applications (Search and User Profile in particular)Patching or upgrading
Redundancy and FailoverWeb and application servers
Services Machine InstancesMost services support multiple instances to run within a single farm to provide redundancy and scalability.
Service RedundantInstancesSupported
Scales Based On
Service RedundantInstancesSupported
Scales Based On
Access Database Service Yes Users Microsoft SharePoint Foundation Timer
Yes N/A
Application Discovery and Load Balancer Service
Yes Users Microsoft SharePoint Foundation Web Application
Yes Users
Application Registry Service Yes Users Microsoft SharePoint Foundation Workflow Timer Service
Yes Users
Business Data Connectivity Service Yes Users PerformancePoint Service Yes Users
Central Administration Yes N/A PowerPoint Service Yes Users
Claims to Windows Token Service Yes Users Search Administration Web Service Yes N/A
Document Conversions Launcher Service
Yes Users Search Query and Site Settings Service
Yes Users, Content
Document Conversions Load Balancer Service
Yes Users Secure Store Service Yes Users
Excel Calculation Services Yes Users SharePoint Foundation Help Search No* Users
Lotus Notes Connector Yes Content SharePoint Server Search Yes Content
Managed Metadata Web Service Yes Users User Profile Service Yes Users
Microsoft SharePoint Foundation Administration
Yes N/A User Profile Synchronization Service
No Content
Microsoft SharePoint Foundation Database
Yes N/A Visio Graphics Service Yes Users
Microsoft SharePoint Foundation Incoming E-Mail
Yes Users Web Analytics Data Processing Service
Yes Content
Microsoft SharePoint Foundation Sandbox Code Service
Yes Users Web Analytics Web Service Yes Users
Microsoft SharePoint Foundation Subscription Settings Service
Yes Users Word Automation Services Yes Users
High Availability Within a Single Farm Single data center
Is that H
A ?
NO !
SP2010 HA means especially:SP2010 service distribution and full
redundancy.SQL 2008 HA: http://technet.microsoft.com/en-us/library/cc678868.aspx
Backup / Restore strategy.Disaster Recovery strategyHardware or Virtual must support all this HA requests
Network latency (< 1ms…)1GB or 10GB network speedSame hardware on all datacenter.
Monitoring (eg: System center)
High Availability Within two Farm One active Farm, one standby farm
2 Options:1. Restore a backup in secondary farm (not
feasible for most)
2. Maintain separate UPA and use the User Profile Replication Engine (UPRE)
Replicate user profiles and social data every 5 seconds by default
User Profile Replication Engine overview (SharePoint Server 2010) http://technet.microsoft.com/en-us/library/cc663011.aspx
Workaround: Redundancy and FailoverService application drill-down – User Profile over 2 Farms.
3 Options:1. Restore a backup in secondary farm (not
feasible for most)
2. Dual-crawl the live farm from the failover farm (not sensible for most)
3. Maintain separate Search SA and crawl content locally
Requires read-only access to all content databases for the duration of a crawl
Requires an up to date SiteMap in the Config DB for new site collections to be crawled and accessed after failover
Redundancy and FailoverService application drill-down – Standard Search over 2 farms
Sample/Proposal HA Switzerland architecture
HA/HS - Role Virtualization Considerations
Role VirtualizationDecision Considerations and Requirements
Web RoleRender Content Ideal • Easily provision additional servers for load
balancing and fault tolerance
Query RoleProcess Search Queries
Ideal • For large indexes, use fixed sized VHD• Requires propagated copy of local index
Application RoleExcel Services, etc Ideal • Provision more servers as resource requirements
for individual applications increase
Index RoleCrawl Index Consider
• Environments where significant amount of content is not crawled
• Requires enough drive space to store the index corpus
Database Role Consider
• Environments with lower resource usage requirements
• Implement SQL Server® alias for the farm required
SharePoint 2010 Virtualization Best Practices Best Practices and Recommendations
CPU•Configure a 1-to-1 mapping of virtual processor to logical processors for best performance
•Be aware of “CPU bound” issues
Memory
•Ensure enough memory is allocated to each virtual machine
Disk•Be aware of underlying disk read write contention between different virtual machines to their virtual hard disks
•Ensure SAN is configured correctly
Network
•Use VLAN tagging for security •Associate SharePoint® virtual machines to the same virtual switch
•Try to have dedicated network card for each VM to communicate out
Others
•Ensure that integration components are installed on the virtual machine
•Do not use other host roles (use server core)•Avoid single point of failure: load balance your virtual machines across hosts and cluster virtual machines
Real: What a customer had on datacenter…
Hosted on 4 Physical servers
Cluster supporting many applications including 11 databases -> Perf issues
134 Virtual servers
Enterprise Search Farm
Don’t put all your VM in the same…
Switzerland HA virtualization
FARMS
Hyper-VData Centers
Additional ResourcesPlan for availability (SharePoint Server 2010): http://technet.microsoft.com/en-us/library/cc748824.aspx
Plan for disaster recovery (SharePoint Server 2010): http://technet.microsoft.com/en-us/library/ff628971.aspx
User Profile Replication Engine overview (SharePoint Server 2010): http://technet.microsoft.com/en-us/library/cc663011.aspxVirtualization for SharePoint Server 2010: http://technet.microsoft.com/en-ca/sharepoint/ff602849.aspx Boundaries and Limits Document: http://technet.microsoft.com/en-us/library/cc262787.aspxRAP Program: http://download.microsoft.com/download/1/C/1/1C15BA51-840E-498D-86C6-4BD35D33C79E/Datasheet_SPRAP.pdf
© 2010 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.