SharePoint Saturday Michigan Keynote - Top 5 Infrastructure Concerns for a SharePoint Environment


Published on

Keynote from SharePoint Saturday Michigan on the Top 5 SharePoint 2010 Infrastructure Concerns.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SharePoint Saturday Michigan Keynote - Top 5 Infrastructure Concerns for a SharePoint Environment

  1. 1. Michael Noel<br />Convergent Computing<br />Twitter: @MichaelTNoel<br />The Top 5 Infrastructure Concerns of a SharePoint Environment<br />
  2. 2. Michael Noel<br />Author 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 .<br />Partner at Convergent Computing ( / +1(510)444-5700) – San Francisco Bay Area based Infrastructure/Security specialists for SharePoint, AD, Exchange, Security<br />
  3. 3. Top 5 Infrastructure Concerns<br />Data Management<br />1<br />Server and Farm Sprawl<br />2<br />Security<br />3<br />Upgrade and Migration<br />4<br />High Availability/Disaster Recovery<br />5<br />
  4. 4. Concern #1Data Management<br />
  5. 5. SharePoint Content Growth Issues<br />SharePoint Products and Technologies are growing faster than any other MS product<br />SharePoint Document Management environments are on the rise<br />All of that content is being stored in SharePoint Content Databases<br />
  6. 6. SharePoint Content Database Limitations<br />Every version of every document in SharePoint is stored in full in the content database <br />This can lead to Content Databases growing in size quickly<br />Microsoft recommends 100GB-200GB max for Content DBs<br />Site Collections can only reside in a single Content DB.<br />
  7. 7.
  8. 8. Binary Large OBject (BLOB) Storage<br />BLOBs are unstructured content stored in SQL<br />Includes all documents, pictures, and files stored in SharePoint<br />Excludes Metadata and Context, information about the document, version #, etc.<br />Until recently, could not be removed from SharePoint Content Databases<br />Classic problem of structured vs. unstructured data – unstructured data doesn’t really belong in a SQL Server environment<br />
  9. 9. Getting your BLOBs out of SharePoint<br />Can reduce dramatically the size of Content DBs, as upwards of 80%-90% of space in content DBs is composed of BLOBs<br />Can move BLOB storage to more efficient/cheaper storage<br />Improve performance and scalability of your SharePoint deployment<br />
  10. 10. Concern #2Server and Farm Sprawl<br />
  11. 11. Infrastructure Sprawl and Scalability<br />
  12. 12. SharePoint 2010 ArchitectureBest Practice “Six Server Farm”<br />2 Dedicated Web Servers (NLB)<br />2 Service Application Servers<br />2 Database Servers (Clustered or Mirrored)<br />1 or 2 Index Partitions with equivalent query components<br />
  13. 13. SharePoint 2010 ArchitectureScalable to Large Farms<br />Multiple Dedicated Web Servers<br />Multiple Dedicated Service App Servers<br />Multiple Dedicated Query Servers<br />Multiple Dedicated Crawl Servers, with multiple Crawl DBs to increase parallelization of the crawl process<br />Multiple distributed Index partitions (max of 10 million items per index partition)<br />Two query components for each Index partition, spread among servers<br />
  14. 14. Service Application Matrix<br />
  15. 15. Tool for Combating Sprawl?– Server Virtualization<br />
  16. 16. Virtualized Farm ArchitectureCost-effective Virtual Environment / No HA<br /><ul><li>Allows Organizations that wouldn’t normally be able to have a test environment to run one
  17. 17. Allows for separation of the database role onto a dedicated server
  18. 18. Can be more easily scaled out in the future</li></li></ul><li>Virtualized Farm ArchitectureHighly Available Farm with only Two Servers<br /><ul><li>High-Availability across Hosts
  19. 19. All components Virtualized
  20. 20. Uses only two Windows Ent Edition Licenses
  21. 21. Can take advantage of various storage options</li></li></ul><li>Virtualized Farm ArchitectureBest Practice Virtual/Physical with HA/Perf<br /><ul><li>Highest transaction servers are physical
  22. 22. Multiple farm support, with DBs for all farms on the SQL cluster
  23. 23. Tie into consolidate storage tier</li></li></ul><li>Concern #3Security<br />
  24. 24. Address all Layers of Security<br />Infrastructure Security and Best Practices<br />Best Practice Service Account Setup<br />Kerberos Authentication<br />Data Security<br />SharePoint Security ACLs and Role Based Access Control (RBAC)<br />Transparent Data Encryption (TDE) of SQL Databases<br />Transport Security<br />Secure Sockets Layer (SSL) from Server to Client<br />IPSec from Server to Server<br />Inbound Internet Security (Forefront UAG/TMG) / Certs<br />Rights Management<br />
  25. 25. Use Multiple Service AccountsSample Service Accounts<br />
  26. 26. KerberosBest practice: Enable Kerberos!<br />When creating any Web Applications for Content, USE KERBEROS. It is much more secure and also faster with heavy loads as the SP server doesn’t have to keep asking for auth requests from AD.<br />Kerberos auth does require extra steps, which makes people shy away from it, but once configured, it improves security considerably and can improve performance on high-load sites.<br />
  27. 27. Use SharePoint-Aware Antivirus<br />
  28. 28. Protecting the Edge<br />Exchange<br />CRM<br />SharePoint<br />IIS based<br />IBM, SAP, Oracle<br />Mobile<br />HTTPS / HTTP<br />Home / Friend <br />/ Kiosk<br />Terminal / Remote Desktop Services<br />Layer3 VPN<br />Internet<br />HTTPS (443)<br />DirectAccess<br />Non web<br />Business Partners /<br />Sub-Contractors<br />AD, ADFS, <br />RADIUS, LDAP….<br />NPS, ILM<br />Employees Managed Machines<br />
  29. 29. Transparent Data Encryption (TDE)<br />New in SQL Server 2008<br />Only Available with the Enterprise Edition<br />Seamless Encryption of Individual Databases<br />Transparent to Applications, including SharePoint<br />
  30. 30. Transparent Data Encryption (TDE)<br />When enabled, encrypts Database, log file, any info written to TempDB, snapshots, backups, and Mirrored DB instance, if applicable<br />Operates at the I/O level through the buffer pool, so any data written into the MDF is encrypted<br />Can be selectively enabled on specific databases<br />Backups cannot be restored to other servers without a copy of the private key, stolen MDF files are worthless to the thief<br />Easier Administration, Minimal server resources required (3%-5% performance hit)<br />
  31. 31. Rights Protection of ContentActive Directory Rights Management Services<br />AD RMS is a form of Digital Rights Management (DRM) technology, used in various forms to protect content<br />Used to restrict activities on files AFTER they have been accessed:<br />Cut/Paste<br />Print<br />Save As…<br />Directly integrates with SharePoint DocLibs<br />
  32. 32. Concern #4Upgrade and Migration<br />
  33. 33. Upgrade and Migration Data Management Challenges<br />Most risk-averse migration/upgrade approach is Database Attach model or 3rd Party tool model<br />Requires double the current amount of disk space as the new farm needs to be built as a ‘greenfield’<br />Disk IO levels are also generally higher in SharePoint 2010<br />
  34. 34. Concern #5High Availability and Disaster Recovery<br />
  35. 35. High Availability at the 3 Tiers<br />Web = Network Load Balancing (Hardware or Software)<br />Service Application = Install on Multiple Systems<br />Data = MCSC Clustering or High Availability Mirroring<br />
  36. 36. Mirroring vs. Clustering<br />Clustering is Shared Storage, can’t survive storage failure, makes Mirroring more attractive<br />Clustering fails over quicker<br />Mirroring is not supported for all databases, but Clustering is<br />Both Clustering and Mirroring can be used at the same time<br />
  37. 37. SQL Database MirroringProviding for HA and DR for SharePoint Content<br />Introduced in SQL 2005 SP1<br />Greatly improved in SQL 2008 and now SQL 2008 R2<br />Available in Enterprise and Standard (Synchronous only) editions<br />Works by keeping a mirror copy of a database or databases on two servers<br />Can be used locally, or the mirror can be remote<br />Can be set to use a two-phase commit process to ensure integrity of data across both servers<br />Can be combined with traditional shared storage clustering to further improve redundancy<br />SharePoint 2010 is now Mirroring aware!<br />
  38. 38. Mirroring Limitations<br />Some Service Apps store data outside of the data tier, including:<br />Excel Services Application<br />Access Services<br />If a Service App Server hosting these functions goes down, the end user is affected (for that session only.) They can still use another server to re-initiate the session<br />Only Content DBs and the Secure Store DB are supported for Asynchronous Mirroring<br />All DBs except a few minor ones are supported for Synchronous Mirroring<br />
  39. 39. Single Site HA Mirrored Farm<br />Single Site<br />Synchronous Replication<br />Uses a SQL Witness Server to Failover Automatically<br />Mirror all SharePoint DBs in the Farm<br />Use a SQL Alias to switch to Mirror Instance<br />
  40. 40. Cross-Site Mirrored HA Farm<br />Two Sites<br />1 ms Latency<br />1GB Bandwidth<br />Farm Servers in each location<br />Auto Failover<br />
  41. 41. Two Farm / Mirrored Content DBs<br />Two Sites<br />Two Farms<br />Mirror only Content DBs<br />Failover is Manual<br />Must Re-index and recreate Svc. Apps<br />
  42. 42. Configuring the FarmNetwork Load Balancing<br />Hardware Based Load Balancing (F5, Cisco, Citrix NetScaler – Best performance and scalability<br />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.<br />If using Unicast, use two NICs on the server, one for communications between nodes.<br />If using Multicast, be sure to configure routers appropriately<br />Set Affinity to Single (Sticky Sessions)<br />If using VMware, note fix to NLB RARP issue (<br />
  43. 43. Clustering Best PracticeTake Advantage of both Nodes on SQL Server<br />
  44. 44. For More Information<br />SharePoint 2010 Unleashed (SAMS Publishing)<br />Microsoft ‘Virtualizing SharePoint Infrastructure’ Whitepaper<br />Microsoft ‘SQL RBS’ Whitepaper<br /> <br />Microsoft SQL Mirroring Case Study<br /> <br />Failover Mirror PowerShell Script<br /> <br />Contact us at<br />
  45. 45. Thanks!<br />Michael Noel<br />Twitter: @MichaelTNoel<br /><br />