Embed Size (px)
DESCRIPTION
Come and understand different type of SharePoint Topologies and learn how to design for SharePoint architecture that serve for Intranet, Websites, Office Web Apps Server, App management, wide-area networks, monitoring, newsfeeds, distributed cache, high availability, and disaster recovery.
Citation preview
Deep Dive into SharePoint Topologies and Server Architecture
for SharePoint 2013By K.Mohamed Faizal ,
Lead Consultant, Chief Architect Office
NCS (P) Ltd, Singapore
www.zquad.in / @kmdfaizal
SharePoint
Hi !My Name is Faizal and I’m Pre-Sales Consultant and
SharePoint Architect
www.zquad.in / @kmdfaizal
Today Outline…
• SharePoint 2013 performance • Hardware Requirements• Software Requirements• Understanding the requirements • SharePoint 2013 Topology• Logical Topology• SharePoint Licensing • Migration / Upgrade
SharePoint 2013 performance challenge• New capabilities
• Richer experience
• Servers have more work
• Clients have more work
• A global online service to run
SharePoint deployments (Improvements)
Reliable
• 50% faster server response
• 4 X faster profile sync. • 10 X faster w/ Active Directory import
• 40% more efficient use of bandwidth
• 80% less file i/o related SQL IOPS
• More scalable SharePoint farms
IIS compression
Image compression
Server response time
SharePoint is optimized for wide-area networks
Betteruse of IE ports TCP ramp-up
Use of bandwidth
40% more efficient
CDN for SharePoint Online
50% faster
Limits Product does have its limits.
Limits are for each dimension.Each dimension needs to stay within limits
SharePoint farms scale more than ever
File I/O and Storage
Efficient file I/O and storage
Up to 80% reduction in SQL IOPSWrites are proportional to size of change not sizeof the fileUnproductive I/Os reduced significantly
Leveraging advanced SQL features for database level optimizations
Efficient Store
Database optimizations
Improved I/O
Scale and reliability
Better scale, better reliability
Centralized, scalable caching for social features
New Search fault tolerance and scalability model
SharePoint-aware routing with Request Management
Distributed cache
Request management
Better Search scalability
Hardware Requirements
Web & Application Servers | Single Server Farms
SharePoint 2010 Minimal Requirement
SharePoint Server 2013 Minimum Requirement
Processor 64-bit, four cores 64-bit, four cores
RAM4 GB for developer or evaluation use
8 GB for production use in a single server or multiple server farm
4 GB for developer or evaluation use
8 GB for production use in a single server or multiple server farm
Storage80 GB for system driveMaintain twice as much free space as you have RAM for production environments.
80 GB for system driveMaintain twice as much free space as you have RAM for production environments.
Database Servers | Minimum Hardware Requirements
SharePoint 2010 Minimal Requirement
SharePoint Server 2013 Minimum Requirement
Processor64-bit, four cores for small deployments
64-bit, eight cores for medium Deployments
64-bit, four cores for small deployments
64-bit, eight cores for medium Deployments
RAM8 GB for small deployments
16 GB for medium deployments
8 GB for small deployments
16 GB for medium deployments
Storage 80 GB for system driveHard disk space is dependent on the size of your SharePoint content
80 GB for system driveHard disk space is dependent on the size of your SharePoint content
Software RequirementsDependencies and prerequisites
Software Requirements
PrerequisitesWindows Management Framework 3.0Application Server RoleWeb Server (IIS) RoleMicrosoft .NET Framework 4.5Update for the .NET Framework 4 (KB2468871)Microsoft SQL Server 2008 Service Pack 1 Native ClientWindows Identity Foundation (KB974405)Microsoft Sync Framework Runtime v1.0 (x64)Windows Server AppFabricWindows Identity Foundation v1.1Microsoft Information Protection and Control ClientMicrosoft WCF Data Services
Windows Server 2008 R2 Service Pack 1
Windows Server 2012 Provides support for Windows PowerShell 3.0
Provides support for information protection
.NET Framework 4.0
Provides in memory distributed caching
Provides support for Windows PowerShell 3.0
Provides support for information protection
.NET Framework 4.5
Enables the creation & consumption of OData services
Provides in memory distributed caching
Windows Management Framework 3.0
Microsoft .NET Framework 4.5Update for the .NET Framework 4 (KB2468871)
Windows Server AppFabric
Microsoft Information Protection and Control ClientMicrosoft WCF Data ServicesHardware and software requirements for SharePoint Server 2013 (http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx)
Software Requirements
64-bit edition of Microsoft SQL Server 2008 R2Service Pack 1
64-bit edition of SQL Server 2012
Hardware and software requirements for SharePoint Server 2013 (http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx)
Client side software requirementsCompatibility and Support Considerations
Office Client Minimum Software Requirements
• Office 2010 or Office 2013• For full offline and integrated experience
• SharePoint Designer• SharePoint Designer 2010 only works for 2010 mode sites• SharePoint Designer 2013 works for both 2010 and 2013 mode sites
• SharePoint Workspace (Skydrive Pro)• SharePoint Workspace 2010 and 2013 work for both 2010 and 2013 mode sites• New folder synchronization capabilities released
Browser Support Matrix
Supported in 2013 Supported with limitations Not Tested
Internet Explorer 9 (32-bit) XInternet Explorer 8 (64-bit) XInternet Explorer 9 (32-bit) XInternet Explorer 8 (64-bit) X
Internet Explorer 7 (both) XMozilla Firefox (Latest version in-market) XGoogle Firefox (Latest version in-market) X
Safari (Latest version in-market) X
High Availability Overview
Availability Layers
Failover Clustering/Network Load BalancingActive/Passive, Active/Active, etc.
FailoverManual, Automatic
BackupFull, Incremental, Differential, etc.
Data Centric
Application Centric
Avai
labi
lity
Reco
very
High AvailabilityGenerally expressed as a percentage of uptime in a given year
Uptime Annual Downtime AllowanceDays Hours Minutes
99% 3 15 3699.5% 1 19 4899.9% 8 4699.95% 4 2399.99% 5399.999% 599.9999% ½ (30 seconds)
99.99% 53
Definitions
RTO = Recovery Time ObjectiveHow long until the application becomes available
RPO = Recovery Point ObjectiveHow much data can be lost
MTBF = Mean Time Between FailureFrequency of failure
MTTR = Mean Time To Repair/ResolveEstimated time to repair/resolve an issue
Deterministic Calculation
Availability = MTBF/(MTBF + MTTR)Useful definition for theoretical and practical
MTBF is Mean Time Between FailureWhat, when, why and how does it fail?
MTTR is Mean Time To RepairHow long does it take to fix?
Goal = Increase MTBF, decrease MTTR
PlanningCapabilities drive limitations:Infrastructure constraintsTopology constraints
High availability is not limited to just component and content-based redundancy, it also encompasses capacity
PlanningUnderstand what to protect before how to protect itApply objectivesService Level AgreementsRecovery Point ObjectivesRecovery Time Objectives
Understand what is provided out of the boxUnderstand business continuity management is an ongoing process
Planning Impact AnalysisWorkload granularityThreat identificationObjectives
Solution DesignMeet SLA within constraintsConduct cost/benefit analysis
ImplementationDeployment and configuration
TestingValidate solutions meets SLA
MaintenanceAnnual review of solution
Analysis
Solution Design
ImplementationTesting
Maintenance
Planning
Unplanned Downtime
• SAN/RAID• Backup/Restore• Log Shipping• Database Mirroring• Failover Clustering
Planned Downtime
• Rolling Upgrades/Patches• Online Operations• Database Snapshots
DriversUnplanned downtimeProtection against failures
Machine level: hardware outages, service failures, data corruption …Site level: hurricanes, fires ..
Recovery from errors (User or Application)Incorrect data modifications, accidental changes…
Planned downtimeOnline administration
Software/hardware upgrades, index rebuilds, MACs… Predictable Resourcing
Features that enhance concurrency
Drivers : Performance and ReliabilityConcurrent users?Growth or adoption over X years?Performance metrics?Services?Geographical areas?AD, SharePoint, SQL locations?Peak hours?Monitoring and Maintaining?Expected load?RAM? Distribution? NUMA Boundaries?
Drivers : Performance and Reliability? (cont.)Network speed?Encryption requirements?Virtual, bare metal, etc. ?Blade distribution? Development and Staging?Software development lifecycle?Custom code?External SharePoint apps?Concerns acquiring hardware?Time allocated for performance and reliability testing?
WORKLOAD
DATASET
HARDWARE
SLA
Planning
Facts: purpose, services, # of users, concurrency, rps, location
Tuning options: satellite farms, disable services, block clients …
Facts: #of site collections, DBs, data size
Tuning Options: split site collections, balance content…
Facts: # of servers, hw spec, roles, network
Tuning Options: add server, scale-up, tune settings …
ResponsivenessThroughputAvailabilityFailure rates
Workload Characteristics Value
Average daily RPS
Average RPS at peak time
Total number of unique users per day
Average daily concurrent users
Peak concurrent users at peak time
Total number of requests per day
Expected workload distribution No. of Requests per day % Web Browser - Search Crawl
Web Browser - General Collaboration Interaction
Web Browser - Social Interaction
Web Browser - General Interaction
Web Browser - Office Web Apps
Internet Site!
Calculator for distributed cache
Z =f( ),X Y
Sizes (In KB)• #tag size (KB)• avg user or group post size (KB)• Entity cap• LMT entry size (KB)
Absolute Counts• # of Shared regions• Time-to-live• Total # users per farm• % of socially active users in the farm• # Active users per farm
Entity stats• # of actively followed sites• # groups owned per user• # of actively followed documents• # followed/created hash tags per user• % of hash tags that are unique• # hash tags
Activity• # of public new posts per user per day• # replies per user per day• # of actively followed document
updates per doc per day• # of site activities per site per day • # of hash tags activities per user per day• # of group posts per user per day • # of group replies per user per day
Computed Activity Per Day• # public user posts per day• # followed site activities per day• # followed document activities per day• # tag posts per day• #entries in all groups (group updates
per day)• # User regions• # entities (w/o groups)• # group• # velocity tags• #entries in all user regions• # entries in all entities (no group)• # entities in LMT• size of LMT (KB)• Size of user posts (KB)• size of group posts (KB)• rest of entity size (KB)• Total Data size in Velocity (KB)• Data Size overhead (KB)• velocity overhead including region
overhead (KB)• Data size per user region (KB)• Data size per shared region (KB)
Social Network
SharePoint 2013 Topology
Hosts web pages, Web services, and Web Parts that are necessary to process requests served by the farm.
Directs requests to the appropriate application servers.
In dedicated services farms, this role is not necessary because web servers at remote farms contact application servers directly.
Server RolesWeb server In many farms, all services will run on two
identically configured application servers for redundancy.
The Search service application automatically configures the necessary services on application servers. Using the Services on Server page is not necessary.
After deployment, look for services that consume a disproportionate amount of resources and consider placing these services on dedicated hardware.
Application server rolesUse the Services on Server page in Central Administration to assign services to specific application servers.
Database server
In a small farm environment, all databases can be deployed to a single server. In larger environments, group databases by roles and deploy these to multiple database servers.
Two redundant database servers
Legend for database icons
Single database server
The distributed cache feature is enabled by default and the Distributed Cache service is automatically started on all web and application servers in a farm. Distributed cache improves performance by:
Caching social data, such as news feeds. Caching authentication tokens.
In very large environments distributed cache can be offloaded to dedicated servers.
Distributed cache Office Web Apps Server
Office Web Apps Server is a separate server product that can:
Serve multiple SharePoint Server farms for viewing and editing.
View files from Exchange Server, Microsoft Lync. Integrate with URL-accessible file servers.
By separating Office Web Apps from the SharePoint farm, servers can be updated more frequently and scale and performance can be managed independent of the SharePoint environment. Office Web Apps Server can be used with all versions of SharePoint 2013. The Office Web Apps Server architecture does not include a database.
Request management and load balancing
Request Management is a feature that gives SharePoint farms control over incoming requests and how these are routed. Routing rules are prioritized and apply logic to determine the nature of requests and to apply the most appropriate response, such as the following types of actions:
·Route requests to web servers that have good health characteristics.·Identify and block known bad requests . ·Route requests of specific types (such as search) to specific servers in the farm.
Request management does not replace the role of a load balancer and it is not enabled by default.
The Request Management component can run in integrated mode on chosen web servers in a farm. Alternatively, the Request Management component can run on dedicated servers that are not part of the SharePoint farm.
Windows Azure Workflow Server
Physical Topology - 2007
Hyper–V host A Hyper–V host B
Web tier
Application tier
Database tier
Physical Topology - 2010
Hyper–V host A Hyper–V host B
Web tier
Application tier
Database tier
Physical Topology – 2013 (Limited deployment)
• One server with all roles:• Evaluation• Very light and simple workloads
Limited deployments are typically used for product evaluation, development and testing, or for environments that have limited numbers of users and don’t require fault-tolerance.
Physical Topology – 2013Fault tolerance for simple workloads with small volumes of content
• Two tiers:• Combined front-end and batch processing
servers• Database servers
Scale the number of servers as needed.
Web tier
Database tier
Hyper–V host A Hyper–V host B
Physical Topology – 2013Fault tolerance for medium workloads with Scaling out farms
• Three tiers:• Front-end servers• Batch processing servers• Database servers
Scale the number of servers as needed.
Web tier
Database tier
Hyper–V host A Hyper–V host B
Application / Batch procssing Servers
On Critical Path For Most Requests Interactive / Serving End-user Requests Doing Background Processing
Request ManagementDistributed Cache
User Profile ApplicationMetadata ServicesBusiness Data ConnectivitySecure StoreState Session StateAccess User CodeSearch Query PerformancePointVisioExcel ServicesPowerPivotProject
User Profile SyncCrawl TargetContent DB JobsWorkflowWMAMachine TranslationSearch Crawl Document Conversion
How we think about Service Applications
Very Low Latency
Low Latency
More tolerant Latency
What is Request Management?
Request Management Fundamentals
Available in all SKUs
SharePoint Foundation Feature
Zero footprint before configuration
OFF by default
Critical to IA and deployment planning
Scoped at the Web Application
SharePoint Web Server
SharePoint Foundation Web Application Service
Request Management Architectural Overview
Request Manager (RM)
Request Throttling and Prioritization
Filter out requests which should be throttled or prioritized
Request Routing
Select which web servers the request may be sent to
Request Load Balancing
Select a single web server to route to, based upon weighting schemes
Request Management Service
Incoming Requests
Configuration
Request Management Architectural Overview
Request Manager is implemented in SPRequestModule
Request Manager is the first code that runs in response to HTTP requests
SharePoint Foundation Web Application Service (a.k.a. WFE)
Request Manager runs in process on the web server
Starting the Request Management Service Instance elsewhere serves no purpose
Request Management Service Instance should run on the web server
Web Application Configuration
Impacts traditional deployments that use IIS host headers
IIS must be “listening” for Request Management to process requests
Where Request Management is configured
Processes all requests
Intended deployment includes a Web Application with NO host headers
Request Management may route requests to another Web Application
This Web Application may not host the content requested
Host Based Sites (a.k.a Host Named Site Collections)
Change to traditional deployments that use IIS host headers
Preferred logical architecture approach for SharePoint 2013
www.contoso.comwww.fabrikam.comwww.tailspin.com
Multiple Site Collections with “top level” host names in a single Web Application
For supportability
Even if no end user accesses that entry point
A root Site Collection is required
Deployment Modes
Request Management Service runs on the web servers in a farm
Common On-Premises environments
Integrated Mode Dedicated Mode
A dedicated SharePoint farm which manages requests exclusively, and routes request to other farms
Large scale hosting environments
Components,Rules and Evaluation
Request Management Components
Static Weighting – configurable
Health Weighting – the SharePoint health score
Routing Targetsa.k.a. Machine Targets
Machine Pools
A collection of Routing Targets
The target of Routing Rules
Request Management Rules
Definition of criteria to evaluate before routing requests
Associated with a Machine Pool
Routing Rules Throttling Rules
Definition of criteria to evaluate before refusing requests
NOT associated with a Machine Pool
Request Management Components
A collection of Routing Rules
Allows for evaluation precedence
Three Execution Groups (0,1,2)
Execution Groups Rule Criteria
Criteria to evaluate
Based upon HTTP properties
Rule Criteria
UrlUrlReferrerUserAgentHost
Properties Match Methods
StartsWithEndsWithEqualsRegEx (use with caution!)
IPHttpMethodSoapActionCustomHeader
Rule Evaluation
If matched, the request is refusedIf NOT matched, Routing Rules in Execution Group 0 are evaluated
Throttling Rules
If matched, the request is routed to the correct Routing TargetIf NOT matched, Routing Rules in Execution Group 1 are evaluated
Routing Rules in Execution Group 0
If matched, the request is routed to the correct Routing TargetIf NOT matched, Routing Rules in Execution Group 2 are evaluated
Routing Rules in Execution Group 1
If matched, the request is routed to the correct Routing TargetIf NOT matched, the request is routed to ANY available Routing Target
Routing Rules in Execution Group 2
Rule Evaluation
Configuration and Management
Configuration and Management
No Central Administration
100% Windows PowerShellNo!
Usage Scenarios
Example Scenario
Request Management in Integrated Mode
Single SharePoint Farm
SP1, SP2, SP3load balanced using BIG-IP Local Traffic Manager
Three SharePoint Web Servers
www.contoso.comwww.fabrikam.comwww.adventureworks.com
Three Host Named Site Collections (HNSC)
Requirements
Requests from OneNote client should be refused
Requests for PDFs should be served by SP1 or SP2
Requests for the Fabrikam site collection should be served by SP1 or SP2
Requests for the Adventure Works site collection should be served by SP1 or SP2
Requests for the Contoso site collection should be served by SP3
Logical Architecture
To Learn more about Request management
SharePoint ArchitectEdinburgh, United Kingdom
www.harbar.net | [email protected] | @harbars
Distributed Cache Service
• The Distributed Cache service provides in-memory caching services to several features in SharePoint Server 2013.
• Example:• Newsfeeds• Authentication• OneNote client access• Security Trimming• Page load performance
• These features use the Distributed Cache for quick data retrieval. • The Distributed Cache service stores data in memory and does not have a dependency on
databases in SharePoint Server 2013. • However, some SharePoint features may store data in both the Distributed Cache and
databases. • SharePoint 2013 Server
Cache Host A
Cache Host B¶s cache
size = 8GB
Cache Host B
Cache Host A¶s cache
size = 8GB
Server Farm
Cache cluster¶s cache size for the
entire farm = 16GB
+ =
Repopulation
Activity Generators
Microblog features
Likes Posts/Replies
@ Mentions ...
Document Edits
Document Sharing
Community Posts
Timer Jobs
Birthdays ...
Feeds
Following
Likes Newsfeed
Everyone NewsfeedMentions Newsfeed
Activities Newsfeed Site Feeds
Distributed Cache
Feeds Cache
Recent User Activities
Recent Sites Activities
Recent Tag Activities
Recent Document Activities
Last Modified Time Cache
Last Modified Time of
Activities
Content Databases
All User Activities
All SiteActivities
My Sites Content Databases
Sites Content Databases
Physical Topology - 2013
Front EndLow latency
Back EndMore tolerant latency
Database tier
Routing and CachingVery low latency
Request ManagementDistributed CacheUser Profile ApplicationMetadata ServicesBusiness Data ConnectivitySecure StoreState Session StateAccess User CodeSearch QueryPerformancePointVisioExcel ServicesPowerPivotProject
User Profile SyncCrawl TargetContent DB JobsWorkflowWMAMachine TranslationSearch CrawlDocument Conversion
Physical Topology – 2013 +Search
Front EndLow latency
Back EndMore tolerant latency
Database tier
Routing and CachingVery low latency
Search (Query, Index, Admin)Low latency
For all but the smallest enterprise deployments, you will want to split Search Query functionality to a separate tier
Latency Throughput Resource Utilization
DesiredBehavior
Very low < 5 msec Very High Medium Consistent
Latency
Low <500 msec Medium Low-Medium Consistent
Latency
High > 1 min High High-Very
HighHigh Throughput
Very Low < 5 msec Very High Low-Medium Consistent
Latency
Front-End
Designing for better SLA
Batch Processing Layer
Specialized Workload
Search
Database Layer
Request Management
Distributed Cache
Scal
e U
p In
depe
nden
tly
Scale Out Independently Latency Throughput Resource Utilization
DesiredBehavior
Very low < 5 msec Very High Medium Consistent
Latency
Low <500 msec Medium Low-Medium Consistent
Latency
Low <500 msec Medium Low – High
Fairly Consistent Latency
High > 1 min High High-Very
HighHigh Throughput
Very Low < 5 msec Very High Low-Medium Consistent
Latency
< 10K Users
More Workloads
More Resources
< 10M Items
<100 Users
Evaluation
Very Light And Simple Workload
< 1,000 Users
Simple Workload
Small Content
Fault Tolerance
More & More Users
More Workloads
More Usage
Large Content
Multiple Index Partitions
Advanced Routing
Evolution of topologyRouting &Caching
Front-End
Batch Processing
Database
Scal
e U
p In
depe
nden
tly
Scale Out Independently
1..N
1..N
1..NCrawl
1..N
1..N
Query
1..N
Search
1..N
Specialized
1..N
Schematic Diagram…Machines could be virtual or physical.Topologies are rough estimates.
ANALYTICS PROCCESING COMPONENTS
Starting-point numbers for search components based on number of items*NUMBER OF ITEMS
General Guidance
10 million
10-40 million
100 million
INDEX COMPONENTS AND PARTITIONS
QUERY PROCESSING COMPONENTS
CONTENT PROCCESING COMPONENTS
CRAWLERS CRAWL DATABASES
ANALYTICS REPORTING DATABASE
SEARCH ADMNISTRATION COMPONENT
Add 1 index partition per 10 million items
2 components1 partition
8 components4 partitions
20 components10 partition
Use 2 query processing components for redundancy. Above 80 million items, increase to 4.
2
2
4
2
4
6
2
2
6
LINK DATABASE
Add 1 crawl database per 20 million items
1
2
5
Add 1 crawl database per 60 million items
1
1
2
Add one analytics reporting database for each 500K unique items viewed each day or every 10-20M total items
Variable
Variable
Variable
Use 2 search administration components for redundancy, for all farm sizes
2
2
2
2
2
2
* This guidance is intended for enterprise search within an organization. Guidance for Internet sites is provided in a different document.
DatabasesSharePoint system databases
User profile service databases
Search Service Application databases
Other service application databases SQL Server 2008 R2 (SP1) andSQL Server 2012 system databases
Microsoft SQL Server Reporting Services databases
Configuration Central Administration Content Content (many databases)
Profile Synchronization Social Tagging
Search Administration Analytics Reporting Crawl Link
App Management Apps for SharePoint Business Data Connectivity Machine Translation Services Managed Metadata Service PerformancePoint Services Secure Store Service SQL Server PowerPivot Service Application State Service Subscription Settings Service Taxonomy Usage Word Automation Services Word Conversion
Master Model Msdb tempdb
Reporting Server Catalog ReportServerTempDB Report Server Alerting
Logical Topology
“Legacy Topology” – Multiple Web Apps
Application Pool 4
Web application: Team Sites
Zone Load-Balanced URL
Default https://teams.fabrikam.com
Default https://teams.fabrikam.com/sites/Team1https://teams.fabrikam.com/sites/Team2https://teams.fabrikam.com/sites/Team3
Web application: My Sites
Database settings: Target size per database = 175 gigabytes (GB) Site size limits per site = 1 GB Reserved for second-stage recycle bin = 15% Maximum number of sites = 180 Site level warning = 150
https: / /my.fabrikam.com
https: / /my.fabrikam.com/personal/<site_ name>Team1 Team2 Team3
https: / / teams.fabrikam.com
Zone Team Sites
Zone Load-Balanced URL
Default https://my.fabrikam.com
Default https://my.fabrikam.com/personal/User1https://my.fabrikam.com/personal/User2https://my.fabrikam.com/personal/User3
Zone Self-Service Sites
Web application: Partner Web
Application Pool 5
Project1 Project2 Project3
https: / / partnerweb.fabrikam.com
Database settings: Target size per database = 200 GB Storage quota per site = 5 GB Maximum number of sites = 40
Zone Load-Balanced URL
Default https://partnerweb.fabrikam.com
Default
Zone Partner Web Sites
https://partnerweb.fabrikam.com/sites/Project1https://partnerweb.fabrikam.com/sites/Project2https://partnerweb.fabrikam.com/sites/Project3
Application Pool 2
Managed Metadata
I I S Web Site—³ SharePoint Web Services´
Unpartitioned services
Access Services
Visio Graphics Service
Excel Services
Word Automation Services
Work Management
Secure Store Service
Business Data Connectivity
Search User Profile
Default group
Web application: Published I ntranet Content
Application Pool 3
HR Facilities Purchasing
https: / / intranet.fabrikam.com
Zone Load-Balanced URL
Default https://intranet.fabrikam.com
Default
Zone Published Intranet Sites
https://intranet.fabrikam.comhttps://intranet.fabrikam.com/hrhttps://intranet.fabrikam.com/facilitieshttps://intranet.fabrikam.com/purchasing
Web servers
Application servers
Load Balancer
Managed Metadata
Partitioned services
Custom group
Partitioned by project in the Partner Web site collection
Subscription Settings
Search
Database settings: Target size per database = 200 gigabytes (GB)
Database settings: Target size per database = 200 gigabytes (GB) Site size limits per site = 30 GB Reserved for second-stage recycle bin = 10% Maximum number of sites = 6 Site level warning = 5
App Management
Machine Translation
Web application:Central Administration Site
Application Pool 1
Database servers with SQL Server installed and configured to support SQL clustering, mirroring, or AlwaysOn (AlwaysOn applies to SQL Server 2012 only)• Each Application Pool requires
additional resources on each Web Role Machine
• Caching of common assemblies alone is significant overhead
• Leads to multiple farm architectures very quickly with high numbers of web applications !!
Recommended Logical Topology
Application Pool ”SharePoint”
Logical functionality ”My Sites”
Site Collection (MySite Host)https://my.company.com
Personal My Sites (My Site)https://my.company.com/personal/<users>
Logical functionality ”Intranet”
Division Sites (Team site)https://intranet.company.com/sites/<site>
Corporate Intranet (Team site)https://intranet.company.com
Search Center (Enterprise Search Center)https://intranet.company.com/sites/search
Logical functionality ”Teams”
Team Collaboration Sites (Team site)https://intranet.company.com/sites/<site>
Team Collaboration Sites (Team site)https://teams.company.com
Logical functionality ”Communities”
Community Sites (community site)https://intranet.company.com/sites/<site>
Community Sites (community portal)https://communties.company.com
Logical functionality ”Projects”
Community Sites (community site)https://intranet.company.com/sites/<site>
Community Sites (community portal)https://projects.company.com
IIS Web Site – ”SharePoint”
SharePoint Licensing
SharePoint – Usage Scenarios
Intranet Extranet InternetSites
78
SharePoint – Deployment Scenarios
In the CloudOn-Premise
79
E4
E3
E1
SharePoint Licensing BasicsExchange, SharePoint and Lync work together to provide even more value in the Enterprise Suites
SharePoint Enterprise CAL
SharePoint Standard CAL
Enterprise CAL Suite
Core CAL Suite
SharePoint Online Plan 2*
SharePoint Online Plan 1*
O365 E Suite(includes Exchange, SharePoint and Lync)
CAL Suite(includes Exchange, SharePoint and Lync etc.)
Standalone StandaloneOnline
Note: SharePoint Online Plan 1 and Plan 2 also include Yammer
On Premise Online
E2
80
SharePoint 2013 SKUs
OnlineOn Premises
Server CAL Office 365 Add Ons
Audit & Control Mgmt Server
2013
SharePoint Standard CAL
2013
SharePoint Enterprise CAL
2013
SharePoint Online Plan 1
SharePoint Online Plan 2
1GB Storage
Azure App Hosting
Search Server
SharePoint for Internet Sites, Standard (FIS-S)
FAST Search for SharePoint
SharePoint for Internet Sites, Enterprise (FIS-E)
Discontinued SKU Existing SKU New SKU
Highlights
Consolidating FAST Search into SharePoint
Internet Sites scenario licensed through SharePoint Server
For Extranet, no CALs required for external users
Audit and Control Management (ACM) licensed through SharePoint ECAL; requires Microsoft Office Audit and Control Management Server for deployment
New Features
Enterprise: E-discovery, ACM, BI (PowerView)
Standard: App Catalog and Marketplace, Work Management, Social (Community Site), External Sharing, SharePoint 2013 Workflow
SharePoint Server 2013
Duet Enterprise Hosting for SAP
New SKU planned for H1 2013
81
OnlineOn Premises
SharePoint 2013 FeaturesOnlineOn Premises
P Kiosk Plan 1 Plan 2Foundation Standard EnterpriseFeature Set Capability
Apps
Collaboration
Search
Content Management
Business Intelligence
Business Solutions
App Catalog & Marketplace
Team Sites
Work Management
Social
External sharing
Basic Search
Standard Search*
Enterprise Search*
Content Management
Records Management
E-discovery, ACM, Compliance
Excel Services, PowerPivot, PowerView
Scorecards & Dashboards
Access Services
Visio Services
Form Based Applications*
SharePoint 2013 Workflow
Business Connectivity Services**
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●*
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●: Existing ●: New BOLD: EnhancedNote* : Some of the features may not be available (or have limited capability) in equivalent Online SKUsNote* * : Some of the features may not be available in Foundation and Standard SKUsNote : Please refer to Microsoft volume licensing website for the latest Product Use Rights document 82
SharePoint ScenariosOn Premises Extranet & Internet Sites Licensing
ExtranetCurrent (2010) New (2013)
SharePoint Server plus CALs for both internal and external
users. ORSharePoint for Internet Sites
(Standard, Enterprise)
SharePoint Server 2013 plus CALs for internal users only
Internet SitesCurrent (2010) New (2013)
SharePoint for Internet Sites (Standard, Enterprise)
SharePoint Server 2013
Extranet scenario licensed through SharePoint Server. No CALs required for external users, internal users need CALs
Internet Sites scenario licensed through SharePoint Server External users means users that are not either your or your affiliates’ employees, or your or your
affiliates’ onsite contractors or onsite agents No change in Windows server and SQL Server licensing pre-requisites
83
SharePoint Licensing– 2010 vs 2013
2013 Intranet Extranet Internet Sites
Internal UsersSharePoint Server +
CAL SharePoint Server + CAL SharePoint Server
External Users* N/A SharePoint Server SharePoint Server
2010 Intranet Extranet Internet Sites
Internal Users
SharePoint Server + CAL
SharePoint Server + CAL Or
SharePoint for Internet Sites (FIS)SharePoint for Internet
Sites (FIS)
External Users*N/A
SharePoint Server + CAL Or
SharePoint for Internet Sites (FIS)SharePoint for Internet
Sites (FIS)
Note*: External users means users that are not either your or your affiliates’ employees, or your or your affiliates’ onsite contractors or onsite agents
84
Office Web Apps
Never be without the tools you need.Access, work together & share from anywhere with anyone
85
Office 2013 Web Apps LicensingOn Premises Web Apps deployments
• I have internal users who want to access Office documents via Office Web Apps, what licenses do I need to be compliant?
• Our company users (who are licensed for Office Client) are working with external users on projects, what licensing do those external users need to access Office documents via Office Web Apps?
*External Users: defined as users that are not either your or your affiliates’ employees, or your or your affiliates’ onsite contractors or onsite agents.
Scenario Internal User
Read Office documents via Office Web Apps Free, no Office client required
Edit Office documents via Office Web Apps Requires Office 2013 Standard or Professional Plus
Scenario External User*
Read Office documents via Office Web Apps Free, no Office client required
Edit Office documents via Office Web Apps Free, no Office client required
86For O365, please refer to www.office365.com
Migration / Upgrade
Data Migration
• SharePoint provide various option to perform data migration • SQL Content Database Backup/Restore• Backup/Restore via PowerShell / STSADM commands • Use PowerShell / STSADM to Export/Import Site collections / sites • Website backup/restore via Central Administration UI• SharePoint Designer Backup/Restore (.cmp)• SharePoint Designer Web Package (.fwp file) • SharePoint Designer Site Template (.stp file) • SharePoint Site/List Template (.stp file) (Not Supported
Database Migration
As of today “Out of the box” the officially supported data migration is Content Database Backup/Restore
The migration path is SharePoint 2007 to SharePoint 2010 to 2013
(STSADM Backup/Restore) & (STSADM Export / Import)
Backup
cmd
Restore
SharePoint 2013
MOSS 2007Website
Backup/Restore
STSADM Backup / Restore Error prompted due to
unsupported version conflict between MOSS and SP2013
Restore Site Collection
Backup Site Collection
STSADM Export / Import Error: Version of the package
12.0.10.0 is different from the current version this program supports
(STSADM Export/Import [without file compression]) Content permission, properties
CANNOT import User or group 70 cannot be
resolved
STSADM Export/Import [without file compression]
Migrations Facts
• No In-Place Upgrade• Configuration database
• Unsupported for both V2V and B2B upgrades• Has never been supported in prior versions
• Search index databases• Unsupported for V2V upgrades only
• Sync database• Unsupported for V2V upgrades only
• Database Attach is the only supported MS upgrade option
93
UpgradeSetup
Re-Build / Deploy customer solutions
Apply Master Page
SA OWA
Step 1 (Setup Servers)
94
Database servers: SQL Server 2008 R2 or SQL Server 2012
Web and Application servers: Install all prerequisites and then install SharePoint 2013 Products.
Install necessary language packs, and then run the SharePoint Products Configuration Wizard to create the new farm.
Install the software1
In new farm
2Configure service applications
For Upgrade Microsoft recommend that “Do not use the Farm Configuration Wizard” to install the following service applications:• Managed Metadata service application• Search service application• User Profile service application• Office Web Application• My Site configuration
3Configure farm settings
Configure email settings, farm-level security and permission settings, blocked file types, usage and health data collection settings, and diagnostic logging settings.
4Install and Configure Office Web Application
Office Web Apps servers: Install all prerequisites and then install Office Web Apps Products.
Step 2 (Migration) – Test Run
95
1 Set up test Run
2 Identify the customizations
3
Cont
ent
data
base
s
Serv
ice
appl
icat
ion
data
base
s
Database servers
Copy and upgrade databases
4Review database upgrade results
Review upgrade log files
Review sites in 2010 mode
Step 2 (Migration) – Test Run5 Upgrade site collections
Site A in 2010 mode Site A in 2013 mode
Review site upgrade results
Web Parts
Do all the Web Parts from your original site show up in your upgraded site?
Are there broken Web Parts pages?
Are the Web Parts displayed correctly (in the correct zone, location, and size)?
Are there extra or missing Web Parts?
Do the Web Parts work correctly?
Are any pages still checked out?
Are your Excel Web Access Web Parts working correctly? Did you create your connections again correctly? Are external data sources still working?
Large listsAre there any large lists in your environment that must be reworked?
Styles and appearance
Are all images on your pages displayed correctly?
Are the appropriate cascading style sheet colors and styles used in the appropriate places?
Theme choices are different in SharePoint 2013 – which theme do you want to use?
Do you have any JavaScript controls that are not working?
Most issues in this section can be solved by correcting a link to the item.
Are your pages displayed correctly in the browser?
Are there any script errors displayed on any pages?
Customized (unghosted) pages
Are your customizations still in place?
Can you still get to the editing controls on the pages?
Are your customizations still appropriate in the new environment, or do you want to update to the new functionality and look?
Are any pages still checked out?
Step 3 (Migration) – Production
97
Cont
ent
data
base
s
Serv
ice
appl
icat
ion
data
base
s
Database servers
Copy and upgrade databases
Use the SQL Server backup and restore process to copy the databases to the new environment. Optionally, set the databases to read-only in SQL Server to preserve access to the original farm data, without allowing changes.
Cont
ent
data
base
sSe
rvic
e ap
plic
ation
da
taba
ses
Database servers
Most actions take place in SQL Server Management Studio
Original SQL Server
Set t
o re
ad-o
nly
(opti
onal
)
Back
up
New SQL Server
Set t
o re
ad-w
rite
(as
need
ed)
Rest
ore
Step 3 (Migration) – Production
• Create web applications• Upgrade content databases • Upgrade service application databases• Review database upgrade results
• Review upgrade log files• Review sites in 2010 mode
• Apply customizations• Run site collection health checks• Create an upgrade evaluation site collection• Upgrade a site collection
98
Modify Custom Master Page
Modify Custom Department Master Page
Re Build and Deploy Customize Web Parts
Re Build and Deploy Password change
SOE Integration
Migrate site from Classic mode A&A to Claims base A&A
PollingCalendar Events
Step 4 (Optional)
• Office Web Apps• Configuring Core Multi-Tenancy:- A unique deployment for each
customer on a shared set of resources
99
Direct Upgrade to SharePoint 2013• DocAve 6
• Does also support MOSS 2007 to SharePoint 2013 migration (without jumping into SharePoint 2010)
• DocAve is purely a content migrator job which migrates all SharePoint site level contents which includes• SharePoint site collection, Sites, Sub Sites etc…• SharePoint List, and Library • SharePoint List items along with versions and unique permission information• SharePoint Groups, Permissions and Permission Roles etc…• Migration of users/security/Groups/permissions etc at Site/List level…• Does have very flexible migration operation and can support granular level migration too• Does have mapping information like AD Domain Mapping, User Mapping, Sharepoint User Group Mapping etc…• Migration of custom SharePoint native Site Columns and Content Types
• Content Matrix• Content Matrix 6 removes this limitation and provides comprehensive support for upgrading to SharePoint 2013 – from
SharePoint 2003, 2007 or 2010
Your SharePoint is unique.
Deployment topology is important.
Plan for sufficient capacity.
Understand usage, monitor utilization.
Fine tune as needed.
Topology
• Topologies for SharePoint 2013
• SharePoint services• Mobile architecture• Multi-farm architecture• Global solutions• SharePoint 2013 Search• Internet site architecture
Capacity planning
• Software boundaries and limits
• Hardware and software requirements
• Performance and capacity test results
• Recommendations
Monitoring
• Usage and health reports in central administration
• Logging database• Performance counters• Diagnostic logs• IIS logs
Capacity planning resources
We are here to help.Thank you,By Mohamed Faizal
Questions?
Microsoft’s 2013 Dogfood FarmWORKLOAD
DATASET
HARDWARE
SLAs (During Peak Hours)1.3 TB total dataset size
1,001,141 documents
10 content DBs
Largest content DB - 290 GB
8,297 Site collections
Largest site collection - 275 GB
15,000 users
8,800 active users per week
1.7M requests per day
Collab, Social, Doc Mgmt, Project
204,106 profiles in UPA
1 Web App
Latency(99th ntile)
511 ms
RPS
50
Active Users (hr)
2,500
Availability
99.9%
Role HW Spec
Routing & Caching VM, 4 cores, 14GB RAM
Front End VM, 4 cores, 14GB RAM
Batch Processing VM, 4 cores, 14GB RAM
Database 8 cores, 64 GB RAM
Role Avg CPU/ Mem
Routing & Caching 12% / 8 GB
Front End 45% / 11GB
Batch Processing 80% / 12 GB
Database 11% / 46 GB
