Your SlideShare is downloading. ×
Getting SharePoint 2010 Deployment Right
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Getting SharePoint 2010 Deployment Right

6,261
views

Published on

A discussion of SharePoint 2010 deployment, the unknowns, and how to prepare yourself and your environment for your SharePoint 2010 roll out.

A discussion of SharePoint 2010 deployment, the unknowns, and how to prepare yourself and your environment for your SharePoint 2010 roll out.

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
6,261
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
245
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Related to budget is management. Handling more servers simply requires more people. I’ve never seen a shop happily managing lots of servers and it’s not the OS’s fault. Servers, regardless of make, are not perfectly reliable. Add to that routine maintenance such as patching, defragmentation, backup, and restore, and you can quickly see how the overhead starts adding up. Case in point, MSIT. Even with nearly 30 operations people and outsourcing agreements for SQL, storage, and base hardware/OS support, the 400 something servers keep those folks very busy. Make sure the managing team has enough people to manage the additional servers or can hire more as needed. And don’t forget about the psychology of server administration. There are few tools that allow you manage multiple servers from one place. Each server instance represents a standalone management challenge that burdens the psyche of the administrator until he or she becomes overburdened and unhappy. While scaling up has its management challenges as well, removing the burden of the extra hardware, OS, and multiple points of administration makes scaling up attractive in this respect.
  • Transcript

    • 1. Getting SharePoint 2010 Deployment Right
      Mike Watson
      Sr. Product Manager
      Quest Software – SharePoint
      www.sharepointmadscientist.com
      www.sharepointforall.com
      www.twitter.com/mikewat
    • 2. Agenda
      Understanding the Unknown
      Preparing for the Unknown
      Summary
      Q&A
    • 3. About Mike
      Product Manager at Quest
      Web Parts
      Deployment Advisor
      Focus on availability, scalability, and manageability of SharePoint
      Previously at Microsoft
      BPOS (Dedicated and helped design Standard)
      Worked on SharePoint guidance as
      SharePoint CAT virtual team member
      Center of Excellence
      Helped teach the MCM
      U.S. Army
      Computers, Finance, Accounting, and Armor (M1A2)
    • 4. Problems in SharePoint 2007
      Maintenance
      Customization
      Tracking & improving performance
      Managing & Monitoring Change
      Governance
      Managing Systems
      Patching
      Lack of knowledge
      Storage Usage & Growth
      Cross-farm management
      Managing Capacity
      Security
      Guaranteeing Availability
      Lack of insight
    • 5. Problems in SharePoint 2010
      Maintenance
      Customization
      Tracking & improving performance
      Managing & Monitoring Change
      Governance
      Managing Systems
      Patching
      Lack of knowledge
      Storage Usage & Growth
      Cross-farm management
      Managing Capacity
      Security
      Guaranteeing Availability
      Lack of insight
    • 6. OMG!
    • 7. What’s Going On?
      Complexity
      New capabilities and terminology
      Changes to familiar services
      Brand new services
      Additional databases (was 7: now 19)
      Concurrency
      Clients more connected
      Ajax polling
      Offline
      Expectation
      Users are more sophisticated
      Accountability
      More ways than ever to catch you
    • 8. The SharePoint 2010 Administration Paradigm
    • 9. It’s Getting Harder!
    • 10. Prepare Yourself
    • 11. Prepare Yourself and Your Team
      Setup an evaluation environment
      Install and play with SP2010
      http://sharepoint2010.microsoft.com/try-it/Pages/Trial.aspx
      Install and play with Office 2010
      http://technet.microsoft.com/en-us/evalcenter/ee390818.aspx
      Learn LearnLearn!
      http://blogs.msdn.com/arpans/archive/2009/12/02/sharepoint-2010-training.aspx
      Practice your upgrade
    • 12. Prepare Your Environment
    • 13. Hardware Requirements (2007)
    • 14. Hardware Requirements (2010)
      Source: http://technet.microsoft.com/en-us/library/cc262485(office.14).aspx
    • 15. Four to Six Servers Min for HA, Sanity, & Performance
      Web Server +
      Query Server
      Clustered SQLServer
      Application Server
      • Why?
      • 16. Optimizes performance of web servers
      • 17. Increases redundancy and reduces points of failure
      • 18. Redundancy across serserver roles
      • 19. Allows most flexibility & role isolation
    • KISS Principle
      Mo Servers = Mo Problems
      Mo Problems = Mo Money
    • 20. SharePoint & Virtualization
      Virtual is never as good as physical (sharing)
      Some virtualization features don’t work well
      E.g. Resource pool allocation aka overcommit
      Virtualization introduces some artificial limitations to scaling up
      Processor limitations per machine
      Ability to leverage memory
      Sharing across bottlenecks (hw bus, NIC)
      Some roles work better with virtualization than others…
    • 21. Virtualization is Great But be Careful
    • 22. VM’s Need Hardware Too!
      Source: http://technet.microsoft.com/en-us/library/cc262485(office.14).aspx
    • 23. Balance Front-end & Back-end Capacity
    • 24. Database Performance is Paramount!
      SQL Health = SharePoint Health!
      Sub-optimal SQL performance will radiate to other components in the farm
    • 25. Configure SQL to conform w/ best practices
      Configure Memory
      Min & Max values = Total memory – 2GB for OS overhead
      Configure Temp DB
      Allocate ¼, ½, or 1 data file per processor core
      Pregrow databases & never autogrow
      Align partitions
      64KB or 256KB
      Use 64KB or larger multiple for RAID stripe size
      Dedicate storage for SQL
      Separate storage for different workloads
      Use RAID 10
    • 26. Pregrow Databases and Never Autogrow
    • 27. Think Disk IO! Not Disk Capacity!
    • 28. Calculating Disk IO – An Example
    • 29. Allocate as many disks as needed to SQL
      Temp
      Logs
      Search
      Data
    • 30. Best Practices – SQL Disk IO
      Allocate separate and dedicated disks with the following specifications:
      * Raid 1 or variants (0+1, 1+0)
      ** Depends on type and amount of content being indexed
      *** 2000 IOPS minimum. Plan on 1500 IOPS per simultaneous crawl. (e.g. 3 crawls = 4500 IOPS)
      **** Use Raid 5 when redundancy needs are met with replication
    • 31. Use RAID 10
    • 32. Problems in SharePoint
      Maintenance
      Customization
      Tracking & improving performance
      Managing & Monitoring Change
      Governance
      Managing Systems
      Patching
      Lack of knowledge
      Storage Usage & Growth
      Cross-farm management
      Managing Capacity
      Security
      Guaranteeing Availability
      Lack of insight
    • 33. Deployment Advisor for SharePoint
    • 34. What is Deployment Advisor?
      A tool created specifically to instill confidence in SharePoint, its administrators, their managers, and ultimately end users.
    • 35. What is Deployment Advisor Currently?
    • 36. Usage Scenarios
      Discover layouts folder customizations
      Compare web.config files across web applications and servers
      Compare service settings across farms
      Determine upgrade readiness across farms
      Assess health of services, servers, databases, and farms
      Discover best practice and capacity boundary violations
      Export and print anything you see – overviews, summaries, risks.
    • 37. Where is Deployment Advisor Going?
    • 38. Benefits of Deployment Advisor
    • 39. Features
    • 40. Extensible, Open, Community-Driven
    • 41. How Deployment Advisor Works
    • 42. Summary
      2010 is infinitely better than 2007
      Higher level problems still exist just as they did in 2007
      Our jobs as Administrators are getting harder due to:
      Complexity
      Concurrence
      Expectations
      Accountability
      Prepare for the unknown by:
      Learning as much as you can
      Practicing
      Excess hardware capacity (physical and virtual)
      Deploy SQL right
      Allocate proper storage
    • 43. Technology Responsibilities
      Toughest Challenges
      User Provisioning/de-provisioning
      Delegation of Admin Rights
      Compliance Reporting
      Disaster Recovery
      Technology Used / Deployed
      Source: DEC 2008 Attendee Survey Whitepaper
      40
    • 50. Q&A

    ×