Best Practices in Deployment and Management Presented by: JD Wade, Consultant, MCTS Mail: jd.wade@hrizns.com Blog: http://wadingthrough.wordpress.com Twitter: http://twitter.com/jdwade
Agenda Governance Infrastructure Development
Infrastructure
Maintain as a Platform More than an Application Patch/Update more than Patch Regularly At least Quarterly Fixes Problems Before They Occur Prepares For Cases That Are Opened Users Latency is Effected by Multiple Components
Server Configuration Disable Loopback Check Security Feature on servers (MS KB 896861 Two Methods to Disable) IIS Thread Patch (MS KB 946517).Net Framework 3.5 SP1 64 Bit OS Partition (30GB-32 bit, 40GB-64 bit) Ensure 25% free space on NTFS partitions PowerShell Gigabit Ethernet Connections
Software Updated to Service Pack 2 April 2009 Cumulative Update preferred Use Cumulative Update Packages (April is complete, June soon) Use Multiple Service Accounts Know When to Use Kerberos
Backups Test Recovery Set Service Level Agreements Backup as prescribed Site Collection Size Backup Method Less 15 GB STSADM Between 15 GB and 100 GB SQL or Data Protection Mgr Larger than 100GB Data Protection Mgr
SQL Server Lifeblood of Farm Cluster to Ensure Availability Use SQL Aliases Pre-size and pre-construct files Watch Auto Growth settings Simple versus Full Backups Defragment data files Do regular normal SQL Server maintenance
SQL Server Storage RAID 10 provides better throughput than RAID 5 Separate databases and logs onto separate spindles to scale up Sector Align Disk Partitions Format data and log file LUNs to 64KB allocation units Database files need random read and write optimization Log files need sequential read and write optimization Heavy read only environments should focus on database files
SQL Server TempDB Ensure adequate throughput use separate spindles Size database to 25% of largest database in the instance Divide into equal data files based on # of cores in SQL Server
SQL Server Priorities TempDB Database Log Files Search Databases Content Databases
Governance
Governance Unique to Every Organization Balance IT Control with User Empowerment Get Executive Sponsorship Adoption is What Counts Establish an Information Architecture Setup Structure with Most Important Items at the Top Establish Roles and Responsibilities Loosen Rules as There is More collaboration
Collaboration Sizing 15GB Maximum Site Collections 100GB Content Databases for effective performance (25GB if effective) Expect file server data to grow 1.2x - 1.5x going into Ensure Information Architecture has multiple site collections For larger deployments One site collection per content database Break content database into multiple data files equal to # of cores in SQL Server Put data files onto separate spindles for every more performance
Development
Development Use Solutions Use Source Control Use Data Connectors and SSO Database Determine Customization Tools Allowed (Designer is Free Now) Choose Versioning Methods Early Use Multiple Environments Procedure/Tool for Moving Solutions Between Environments Keep Staging and Production alike Create Virtual and Automated Developer Instances
Code Dev Staging Produc8on Content
Appendix Governance Resource Center for http://technet.microsoft.com/en-us/office/sharepointserver/ bb507202.aspx Database Maintenance for Whitepaper http://technet.microsoft.com/en-us/library/cc262731.aspx Working with TempDB in SQL Server 2005 http://technet.microsoft.com/en-us/library/cc966545.aspx
Q & A Presented by: JD Wade Engineer, MCTS Mail: jd.wade@hrizns.com Blog: http://www.wadingthrough.com Twitter: http://twitter.com/jdwade