Building the Perfect SharePoint 2010 Farm - MS Days Bulgaria 2012
Upcoming SlideShare
Loading in...5

Building the Perfect SharePoint 2010 Farm - MS Days Bulgaria 2012






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

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.

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

Building the Perfect SharePoint 2010 Farm - MS Days Bulgaria 2012 Building the Perfect SharePoint 2010 Farm - MS Days Bulgaria 2012 Presentation Transcript

  • Building the PerfectSharePoint 2010 FarmMichael Noel, CCO
  • Michael NoelAuthor of SAMS Publishing titles “SharePoint 2010 Unleashed,” “SharePoint 2007 Unleashed,” “SharePoint 2003 Unleashed”, “Teach Yourself SharePoint 2003 in 10 Minutes,” “Windows Server 2008 R2 Unleashed,” “Exchange Server 2010 Unleashed”, “ISA Server 2006 Unleashed”, and many other titles .Partner at Convergent Computing ( / +1(510)444-5700) – San Francisco Bay Area based Infrastructure/Security specialists for SharePoint, AD, Exchange, Security
  • What we will cover • Examine various SharePoint 2010 farm architecture best practices that have developed over the past year • Examine SharePoint Best Practice Farm Architecture • Understand SharePoint Virtualization Options • Explore SharePoint DR and HA strategies using SQL 2012 AlwaysOn High Availability Technologies • Explore other common best practices (RBS, SSL, NLB) • Examine best practice security for SharePoint • A large amount of best practices covered (i.e. Drinking through a fire hose,) goal is for you to be able to take away at least 2-3 useful pieces of information that can be used in your environment
  • Architecting the Farm
  • Architecting the Farm Three Layers of SharePoint Infrastructure Web Service Apps Data
  • Architecting the Farm Small Farm Models „All-in-One‟ (Avoid)  DB and SP Roles Separate
  • Architecting the Farm Smallest Highly Available Farm • 2 SharePoint Servers running Web and Service Apps • 2 Database Servers (AlwaysOn FCI or AlwaysOn Availability Groups) • 1 or 2 Index Partitions with equivalent query components • Smallest farm size that is fully highly available
  • Architecting the Farm Best Practice ‘Six Server Farm’ • 2 Dedicated Web Servers (NLB) • 2 Service Application Servers • 2 Database Servers (Clustered or Mirrored) • 1 or 2 Index Partitions with equivalent query components
  • Architecting the Farm Ideal – Separate Service App Farm + Content Farm(s) • Separate farm for Service Applications • One or more farms dedicated to content • Service Apps are consumed cross-farm • Isolates „cranky‟ service apps like User Profile Sync and allows for patching in isolation
  • Architecting the Farm Large Virtualized SharePoint Farms• Multiple Dedicated Web Servers• Multiple Dedicated Service App Servers• Multiple Dedicated Query Servers• Multiple Dedicated Crawl Servers, with multiple Crawl DBs to increase parallelization of the crawl process• Multiple distributed Index partitions (max of 10 million items per index partition)• Two query components for each Index partition, spread among servers
  • Virtualization ofSharePoint Servers
  • SP Server Virtualization Virtualization Best Practices
  • SP Server Virtualization Virtualization CPU and Memory Requirements vCPU RAM (Bare RAM RAM (Ideal) Minimum) (Recommend)Web Only* 2 6GB 8GB 12GBService Application 2 6GB 8GB 12GBRoles OnlyDedicated Search 2 8GB 10GB 16GBService AppCombined 4 10GB 12GB 18GBWeb/Search/ServiceAppsDatabase* 4 10GB 16GB 24GB
  • SP Server Virtualization Sample 1: Single Server Environment  Allows organizations that wouldn’t normally be able to have a test environment to run one  Allows for separation of the database role onto a dedicated server  Can be more easily scaled out in the future
  • SP Server Virtualization Sample 2: Two Server Highly Available Farm  High- Availability across Hosts  All componen ts Virtualized  Uses only two Windows Ent Edition Licenses
  • SP Server Virtualization Sample 3: Mix of Physical and Virtual Servers Highest transactio n servers are physical Multiple farm support, w ith DBs for all farms on the SQL cluster
  • SP Server Virtualization Scaling to Large Virtual Environments
  • SP Server Virtualization Virtualization Performance Monitoring Processor (Host Only) • Network Bandwidth – – <60% Utilization = Good Bytes Total/sec – 60%-90% = Caution – <40% Utilization = – >90% = Trouble Good Available Memory – 41%-64% = Caution – 50% and above = Good – >65% = Trouble – 10%-50% = OK • Network Latency - – <10% = Trouble Output Queue Length Disk – Avg. Disk sec/Read or Avg. – 0 = Good Disk sec/Write – 1-2= OK – Up to 15ms = fine – >2 = Trouble – 15ms-25ms = Caution – >25ms = Trouble
  • SP Server Virtualization Quick Farm Provisioning using SCVMM 1. Create new Virtual Guest (Windows Server 2008 R2) 2. Install SP2010 Binaries. Stop before running Config Wizard 3. Turn Virtual Guest into Template, modify template to allow it to be added into domain 4. Add PowerShell script to run on first login, allowing SP to be added into farm or to create new farm End Result - 15 minute entire farm provisioning…quickly add servers into existing farms or create new farms (Test, Dev, Prod) on demand
  • Data Management
  • Data Management Distribute by Default• Start with a distributed architecture of content databases from the beginning, within reason (more than 50 per SQL instance is not recommended)• Distribute content across Site Collections from the beginning as well, it is very difficult to extract content after the face• Allow your environment to scale and your users to „grow into‟ their SharePoint site collections
  • Data Management Sample Distributed Content Database Design
  • Data Management Remote BLOB Storage (RBS) • BLOBs are unstructured content stored in SQL • Includes all documents, pictures, and files stored in SharePoint • Excludes Metadata and Context, information about the document, version #, etc. • Until recently, could not be removed from SharePoint Content Databases • Classic problem of structured vs. unstructured data – unstructured data doesn‟t really belong in a SQL Server environment
  • Data Management Remote BLOB Storage (RBS) Can reduce dramatically the size of Content DBs, as upwards of 80%-90% of space in content DBs is composed of BLOBs Can move BLOB storage to more efficient/cheaper storage Improve performance and scalability of your SharePoint deployment – But highly recommended to use third party
  • SQL Database Optimization
  • SQL Server Optimization Multiple Files for SharePoint Databases Volume #1 Volume #2 Volume #3 Volume #4 DB-A DB-B DB-A DB-B DB-A DB-B DB-A DB-B File 1 File 1 File 2 File 2 File 3 File 3 File 4 File 4 Tempdb File 1 Tempdb File 2 Tempdb File 3 Tempdb File 4
  • SQL Server Optimization Multiple Files for SharePoint Databases • Break Content Databases and TempDB into multiple files (MDF, NDF), total should equal number of physical processors (not cores) on SQL server. • Pre-size Content DBs and TempDB to avoid fragmentation • Separate files onto different drive spindles for best IO perf. • Example: 50GB total Content DB on Two-way SQL Server would have two database files distributed across two sets of drive spindles = 25GB pre-sized for each file.
  • SQL Server Optimization Tempdb Best Practices • TempDB is critical for performance • Pre-size to 20% of the size of the largest content database. • Break into multiple files across spindles as noted • Note there is a separate TempDB for each physical instance • Note that if using SQL Transparent Data Encryption (TDE) for any databases in an instance, the tempDB is encrypted.
  • Data Management SQL Maintenance Plans • Implement SQL Maintenance Plans! • Include DBCC (Check Consistency) and either Reorganize Indexes or Rebuild Indexes, but not both! • Add backups into the maintenance plan if they don’t exist already • Be sure to truncate transaction logs with a T-SQL Script (after full backups have run…)
  • Data Management Truncate Transaction Logs Statement USE CompanyABC_SP2010_ContentDB01; GO ALTER DATABASE CompanyABC_SP2010_ContentDB01 SET RECOVERY SIMPLE; GO DBCC SHRINKFILE (CompanyABC_SP2010_ContentDB01_log, 100); GO ALTER DATABASE CompanyABC_SP2010_ContentDB01 SET RECOVERY FULL; GO
  • High Availability and Disaster Recovery
  • HA and DR Comparison of High Availability and Disaster Recovery Options Potential Potential High Availability and Disaster Recovery Automatic Readable Data Loss Recovery SQL Server Solution (RPO) Time (RTO) Failover SecondariesAlwaysOn Availability Group - Zero Seconds Yes 0-2synchronous-commitAlwaysOn Availability Group - Seconds Minutes No 0-4asynchronous-commitAlwaysOn Failover Cluster Instance NA Seconds Yes NA -to-minutesDatabase Mirroring - High-safety (sync + Zero Seconds Yes NAwitness)Database Mirroring - High-performance Seconds Minutes No NA(async)Log Shipping Minutes Minutes No Not during -to-hours a restoreBackup, Copy, Restore Hours Hours No Not during -to-days a restore
  • HA and DR AlwaysOn Availability Groups in SQL 2012
  • HA and DR Creating AlwaysOn Availability Groups in SQL 2012 Install Windows Server 2008 R2 w/SP1 on multiple nodes Enable the Failover Cluster Feature on each node Use the Failover Cluster Manager Wizard to create a cluster. Name the cluster a unique name that will be separate from the instance name that will be used for SharePoint
  • HA and DR Creating AlwaysOn Availability Groups in SQL 2012 • Install .NET Services 3.5 Feature on each SQL node • Install SQL 2012 Enterprise Edition Database Services (Also recommend adding SQL Management Tools – Complete) • Ensure proper Windows Firewall ports are open • Service Account for SQL – Use the same service account for all nodes – Don‟t use Network Service – If using Kerberos, make sure all SQL names have SPNs associated with the service account • Make sure databases are set to FULL recovery mode • Ensure that the file paths and drive letters are consistent throughout all instances (ideally, or config will have to be manual) • Copy or Create SharePoint databases on Primary node only (use SQL Alias to change name later) • Perform a full backup of your SharePoint databases • Create a file share location that is accessible by all nodes that will be used for the shared backups (i.e. SQL1Backups)
  • HA and DR Creating AlwaysOn Availability Groups in SQL 2012 Enable AlwaysOn High Availability in SQL Server Configuration Manager Repeat on Each Node Restart SQL Services
  • HA and DR Creating AlwaysOn Availability Groups in SQL 2012 Ideally use the New Availability Group Wizard, it automates the process
  • HA and DR Creating AlwaysOn Availability Groups in SQL 2012 • Be sure to have a shared network location for the backup files (Created in earlier step) • Depending on size of databases, this could take a while • Backups can also be pre-staged (Join Only)
  • HA and DR Creating AlwaysOn Availability Groups in SQL 2012 • Validation should show all green, except warning for Listener • The listener („SQL‟ in this example) will be created later, and is required for SharePoint to connect to
  • HA and DR Creating AlwaysOn Availability Groups in SQL 2012 • After the wizard completes, manually create the Availability Group Listener • This is the shared name that SharePoint will connect to and will provide failover (Also called the „Client Access Point‟) • Modify the DNS record for this listener to have a low TTL (60 seconds or less) for cross-subnet failover scenarios
  • HA and DR Creating AlwaysOn Availability Groups in SQL 2012
  • HA and DR Windows Network Load Balancing • Hardware Based Load Balancing (F5, Cisco, Citrix NetScaler – Best performance and scalability • Software Windows Network Load Balancing fully supported by MS, but requires Layer 2 VLAN (all packets must reach all hosts.) Layer 3 Switches must be configured to allow Layer 2 to the specific VLAN. • If using Unicast, use two NICs on the server, one for communications between nodes. • If using Multicast, be sure to configure routers appropriately • Set Affinity to Single (Sticky Sessions) • If using VMware, note fix to NLB RARP issue (
  • HA and DR Windows Network Load Balancing - Sample Best Practice – Create Multiple Web Apps with Load-balanced VIPs (Sample below) –Web Role Servers – ( – Web Role Server #1 – ( – Web Role Server #2 –Clustered VIPs shared between SP1 and SP2 (Create A records in DNS) – ( - Cluster – ( – SP Central Admin – ( – Inbound Email VIP – ( – Main SP Web App (can be multiple) – ( – Main MySites Web App
  • Security and Documentation
  • Document SharePoint SPDocKit • Document all key settings in IIS, SharePoint, after installation • Consider monitoring for changes after installation for Config Mgmt. • Fantastic tool for this is the SPDocKit - can be found at
  • Security Five Layers of SharePoint Security • Infrastructure Security and Best practices – Physical Security – Best Practice Service Account Setup – Kerberos Authentication • Data Security – Role Based Access Control (RBAC) – Transparent Data Encryption (TDE) of SQL Databases – Antivirus • Transport Security – Secure Sockets Layer (SSL) from Server to Client – IPSec from Server to Server • Edge Security – Inbound Internet Security (Forefront UAG/TMG) • Rights Management
  • For More Information SharePoint 2010 Unleashed from SAMS Publishing ( Microsoft „Virtualizing SharePoint Infrastructure‟ Whitepaper ( Microsoft SQL Mirroring Case Study ( ) Failover Mirror PowerShell Script ( ) SharePoint Kerberos Guidance ( SharePoint Installation Scripts ( SharePoint Documentation Toolkit ( Contact us at
  • Michael Noel Twitter: @MichaelTNoel www.cco.comSlides: blog: