1 / 21

SharePoint 2007 Large Scale Infrastructure Planning

SharePoint 2007 Large Scale Infrastructure Planning. Lessons Leant at the University of Southampton. Vicky Anderson 24 th June 2010 . Requirements Capture. Project scope included: Search of corporate sites Search of ePrints (research repository)

wayne
Download Presentation

SharePoint 2007 Large Scale Infrastructure Planning

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SharePoint 2007 Large Scale Infrastructure Planning Lessons Leant at the University of Southampton Vicky Anderson24th June 2010

  2. Requirements Capture Project scope included: • Search of corporate sites • Search of ePrints (research repository) • Migrate SharePoint WSS Intranet from existing school servers to central service • Collaboration sites for staff and students • Create a scalable infrastructure for other school services • Research Collaboration with other Universities/External Organisations • Secure External Collaboration

  3. SharePoint Features Required Immediate needs • Teamsites • Search Future Requirements • Records Centre • Intranet Portal • Business Data Catalog

  4. Useful Resources Microsoft Planning and Architecture for Office SharePoint Server 2007 Downloadable Books 1 and 2:- http://technet.microsoft.com/en-us/library/cc262757(office.12).aspx Microsoft Planning worksheets:- http://technet.microsoft.com/en-us/library/cc262451.aspx Microsoft SQL resources http://www.microsoft.com/technet/prodtechnol/sql/2005/physdbstor.mspx

  5. Identifying the Zones

  6. Web Application Architecture

  7. IIS Tweaks Recommended blog on IIS Settings for content app pools, central admin and the SSP http://blogs.msdn.com/b/joelo/archive/2007/10/29/sharepoint-app-pool-settings.aspx

  8. Server Architecture

  9. Communication between server roles

  10. Disk Architecture • Content Databases Disk Space: Hard disk space for the content database is based on a 1:1.2 ratio of content size to database capacity. E.g. If we plan for 100 GB of content, we will need at least 120 GB of available disk space for the content database, plus additional space for transaction logs. • Search Database Disk Space: Hard disk space for the search database is based on a 1:4 ratio of index size to database capacity. E.g. If the index will be 100 GB in size, we need at least 400 GB of available disk space for the search database, plus additional space for transaction logs. • Future Growth Disk Space: Plan for twice the amount of data you currently have. • Free Disk Space: Leave 25% of the disk free on each volume.

  11. Content Databases Planned for a separate database per site collection • Easier to manage • Easier to restore • Creates additional load on the SQL server

  12. Sizing Web Front Ends • Throughput = Number of Requests the server farm can process a second. The more users the higher the throughput target needs to be. • Concurrency = Simultaneous users on the system. • Request Rate = Average requests an hour an active user generates. • Common actions per user per day: figures are based on Microsoft’s ‘typical user’ generating 36 Requests per Hour. • Complex actions per user per day: figures are based on Microsoft’s ‘heavy user’ generating 60 Requests per Hour.

  13. Calculating Ops/Sec

  14. Resilience • Two load balanced web front ends • SQL cluster dedicated for SharePoint • Application server services to be run on web servers in the event of a failure

  15. Server Specifications • Web Front Ends: 2 x Dell 2950, 8GB RAM, 6 x 300GB Disks • Application Server: Dell 1950, 8GB RAM, 4 x 73GB Disks • Index Server: Dell 1950, 8GB RAM, 830GB SAN Storage for Index • SQL Servers: 2 x Dell 1950, 16GB RAM, 1.4TB SAN storage for data & logs

  16. Backups Powershell script from Codeplex gives the following benefits: • Scheduled scans • Email notification to system administrators • Backs up the IIS metadata and 12-Hive directory • Backup individual site collections if required http://spbackup.codeplex.com/

  17. Problems Encountered • Problems with SQL log files growing • Occasional high memory usage on the SQL server • Problems with Internet Explorer 6 • Restructure of site collections

  18. What would we do differently? • Single Sign-on • Managed Paths • External Collaboration developed in-house • Authentication – Kerberos • Data Protection Manager • Server Virtualisation • Remote Blob Storage

  19. SharePoint 2010 Project Project Scope includes: • Intranet • Microsoft Architecture Design Session • Microsoft Proof of Concept • Search Staff Profiles, responsibilities, expertise, interests • External facing profiles • Organisational structure • Extract data from corporate information systems • Collaboration with Wikis, Blogs, Personal document sharing • Exchange 2010 integration • Office Communication Server integration

  20. SharePoint 2010 Project Other possible tasks • Migrate existing content from SharePoint 2007 • Migrate Search from SharePoint 2007 and look into FAST functionality • Possibility to migrate from our current document management system in to SharePoint

  21. Questions?

More Related