140 likes | 378 Views
SharePoint Infrastructure. Are you doing it wrong?. Andrew "Andy" Prosser Microsoft Capability Lead, Enterprise Content Management. Who is “Andy”. Microsoft Capability Lead, ECM @ Optus Microsoft Technologist 20 years in ICT SharePoint Specialist Western Australian born Sydney Based
E N D
SharePoint Infrastructure Are you doing it wrong? Andrew "Andy" Prosser Microsoft Capability Lead, Enterprise Content Management
Who is “Andy” • Microsoft Capability Lead, ECM @ Optus • Microsoft Technologist • 20 years in ICT • SharePoint Specialist • Western Australian born • Sydney Based • Father of 3 • Keen cyclist
SharePoint Infrastructure Review • Entry Level Design • Virtual Infrastructure provides Availability • Supports ~5,000 users • All Services Provisioned • Limited use of Services • Enterprise Search: ~2M Records
SharePoint Infrastructure Review • Extends Entry Level Design • Adds Office Web Apps
SharePoint Infrastructure Review • Extends Entry Level Design • Adds Office Web Apps • Provides Front-End Resilience • Supports ~10,000 Users
SharePoint Infrastructure Review • Extends Entry Level Design • Adds Office Web Apps • Provides Front-End Resilience • Database High-Availability • Supports ~10,000 Users • Enterprise Search: ~10M Records
Scalability How many users are you supporting? A three (3) server farm can support up to 5,000 users! Performance Considerations: • Multiple Web Apps or Site Collection Host Headers • SharePoint Search: you really only need one server • Reverse Proxy and Caching can improve performance • CPU and Memory is key to SharePoint Performance • BLOB Cache is NOT enabled by default; turn it on and tune it! • Optimise your SQL Server; Memory, CPU, and Disk I/O • Keep your Content Databases small: less than 200GB This simple architecture meets the needs of the majority of Australian businesses!
Common Mistakes • Over engineered design • Under specified components • Misunderstood requirements • Heavy customisation • Point-to-Point Integration • Not using Kerberos • Misplaced/Configured Firewalls • Manual/Piecemeal Implementation
Keep It Stupidly Simple (KISS) My experience is simple is often best - don’t over think it! Use this test on every deployment: • Can you explain it? • Is it supportable? • How hard is it to upgrade? • Do you really need it? • Can you automate it? • What is the DR Plan? • Do you need to change your business process?
Recovering from Disaster • Have a Plan • Protect your SharePoint Content Databases • Leverage your Virtualised Infrastructure • Consider VM Replication to Cloud IaaS • DR includes fail-over AND fail-back • Backups are for DR Only!
Keys to Success • Servers: less is more • Use Virtualised Infrastructure • Don’t under specify server specifications • SharePoint installs to C: drive; extra disks are wasted • Keep all SharePoint Servers on the same network segment • Automate system deployment • Dedicated SQL Server Instance for each SharePoint Farm • Understand your high-availability requirements • No Internet Access? Disable certificate revocation checks! • Separate Farms for each Security Zone; Public, Internal, etc…
Automation • PowerShell is the key • Automate SharePoint build: • AutoSPInstaller: http://autospinstaller.codeplex.com • AutoSPSourceBuilder: http://autospsourcebuilder.codeplex.com • Consider Automating: • Service Account Creation • SQL Server Build • Kerberos Configuration • Office Web Apps Install • Upgrade Process; especially remediation steps Configurable in the User Interface? You can change it via PowerShell!!
Questions? Andrew "Andy" Prosser Microsoft Capability Lead, Enterprise Content Management Business Applications & Solutions Optus Business 1 Lyonpark Road, Macquarie Park NSW 2113 m: +61 4 39098778 e: andrew.prosser@optus.com.au