Building the perfect share point farm
0 likes462 views
This document discusses strategies for building different types and sizes of SharePoint farms to meet varying needs. It addresses factors to consider like capability, performance, reliability, scalability, user experience, security and cost. The key aspects are defining requirements and goals, then designing an optimal farm topology with the right server roles, sizing, virtualization plan, high availability strategy and disaster recovery approach. The focus is on a well planned, documented and tested implementation of the "perfect" SharePoint farm for each organization's unique needs.
Ad
More Related Content
What's hot (11)
Viewers also liked (7)
Ad
Similar to Building the perfect share point farm (20)
Ad
More from David Broussard (14)
Recently uploaded (20)
Building the perfect share point farm
- 1. Building the Perfect SharePoint Farm2011
- 2. Attach the ISORun the installerLet’s Get Started
- 3. Web Front EndService Application ServerSQL ServerExternal ServicesSharePoint Server Roles
- 5. Everything on one server
- 6. Only for Development or similar use
- 7. Can run on Windows 7Single Server Farm
- 8. Break out the SQL Server
- 9. WFE and Service App layer running on the same box
- 10. Recommended for small workgroupsSmall Farm
- 11. Break out the SQL Server
- 12. WFE and Service App layer running on individual servers
- 13. Can handle large amounts of users and content
- 15. Break out the SQL Server
- 16. WFE and Service App layer running on same servers (but two of them)
- 17. Can handle larger amounts of users, but App Layer impacts performance
- 18. Some RedundancyMedium Farm – Option 2
- 19. Multiple WFEs
- 20. Multiple Service App Layers
- 22. No Single Point of FailureLarge Redundant Farm
- 23. How can one, or even four, farm architectures satisfy every need?The “Perfect” SharePoint Farm?
- 24. We need to define perfectionCapabilityPerformanceReliabilityScalabilityUser ExperienceSecurityCost
- 25. Document ManagementRecords ManagementWeb Content ManagementSocial CollaborationBI PlatformEnterprise MessagingCapability – What are we trying to accomplish?
- 26. Performance – How fast does it need to be?Is there an established SLA, and should there be?Page Load vs Transaction time (what can we directly control)Average User Load Total users * % Concurrent Users / Time Per request
- 27. Reliability is expensiveNo really…its expensiveHardware (more than doubledSupport staff increaseHigher level of competency of staffChallenge it early and oftenReliability – Are you sure you can afford it?
- 28. Scalability – What is my growth curve?Establish metrics on your farm and stay on top of themKnow scaling optionsServer sizeServer numbersServer RoleWFE – usersService App – usageSQL – Size and use of content
- 29. Needs and WantsGoals, Motivations & TriggersObstacles & LimitationsTasks, Activities & BehaviorsGeography & LanguageEnvironment & GearWork Life and ExperienceUser Experience – The mythical user
- 30. Security – Information wants to be free!Encrypt your data – yes, even internal communicationSegment SharePoint on a dedicated VLANUse reverse proxy servers (TMG)Use SSL (but off-load it)Use dedicated Admin accounts
- 31. Know your licensing optionsFoundation (free)Standard v EnterpriseInternet SitesDon’t forget to include all other server costsWindows/SQL/TMG/etcHardware costsServersRoutersCost – Plan for now and the future
- 32. The secret sauce is planningWhat roles do I need in my farm?How “big” do those roles need to be?How do we put it all together
- 33. SharePoint Roles RevisitedWeb Front End ServerVery similar to MOSS 2007Primary scale component is number of users connecting8GB RAM, 4 “cores”, 80GB HDSQL ServerClustered or other HA technologyCan have multiple instances to share loadPerformance is critical to Farm16-64GB of RAM/8+ “cores”, 80GB HD + Data
- 34. SQL ConsiderationsAlias your server (SQL Alias or DNS)Size of content DB determines minimum RAMMedium (< 4TB of Content) -> 32GB RAMLarge (>4TB of Content) => 64GB RAMDisk Performance is criticalTune the SAN for optimal performance by useRAID 10 is best, RAID 5 is OKData, Log, and Temp DB all on separate LUNS and Logical DisksEnsure that SAN NIC isn’t saturated
- 35. Service Application ServersAutomatically scale and load balanceCan partition services to specific serversSearch is very scalable, but very complexCrawl ServersCan have multiple servers crawling your dataQuery data sent directly to the Query servers (not on crawl)Query ServersCan create multiple partitions10 Million items is upper limit for a partitionCan have active and passive fail-over partitionsQuery size is estimated at 10% of crawled content (usual smaller)
- 36. Simple (Yeah Right) Search Topology
- 37. What can we virtualize?WFEService AppSQLWhat should we virtualize?WFEService AppSQL?Allows us to dynamically manage Farm as needed by requirementsSnapshots are your friendVirtualization – Problem or Solution?
- 38. High Availability, DR and VirtualizationPlan for emergenciesRecovery Time ObjectiveRecovery Point ObjectivePrevent single point of failureConsider Virtual DRAlso plan for effort to recover from fail-over
- 39. Can the Cloud Save Us?Transfers Risk to Cloud ProviderServersNetworkPatchesBackupsReduces “dark” hardware costsCan be cheaper, or more expensive (shared vs private cloud)
- 40. Its all so complex
- 41. Define our “Perfect” FarmCapabilityPerformanceReliabilityScalabilityUser ExperienceSecurityCost
- 42. Design our “Perfect” FarmServer RolesServer Size & NumberVirtualized ComponentsAvailabilityDisaster RecoveryDon’t forget Test Farm, and Development Farm
- 43. Build the “Perfect” FarmStick to the planEnsure all the pre-reqs and patches are installedScript the installAutoSPInstaller.Codeplex.com (other exist as well)Snapshot everything before you startSnapshot after installTake lots of screen shots for documentation