Ten Non-SharePoint Technical Issues That Can Doom Your Implementation by Robert Bogue - SPTechCon
Upcoming SlideShare
Loading in...5
×
 

Ten Non-SharePoint Technical Issues That Can Doom Your Implementation by Robert Bogue - SPTechCon

on

  • 3,488 views

Technical Class:

Technical Class:
Monday, Marc

Statistics

Views

Total Views
3,488
Views on SlideShare
3,488
Embed Views
0

Actions

Likes
0
Downloads
88
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Ten Non-SharePoint Technical Issues That Can Doom Your Implementation by Robert Bogue - SPTechCon Ten Non-SharePoint Technical Issues That Can Doom Your Implementation by Robert Bogue - SPTechCon Presentation Transcript

    • Top 10 Non-SharePoint Technical Issues That Can Doom Your 3/3/2013Implementation Top 10 Non-SharePoint Agenda Technical Issues That Can • Background Doom Your • Do the Top 10 thing Implementation • Close out Robert Bogue Rob.Bogue@ThorProjects.com (317)844-5310 My Background 10. SQL Server Performance • Assembled computers What You’ll See What’s Wrong • Slow performance across the board • SQL Server is the bottleneck in when memory was • Long search crawl times SharePoint implementations chips and not sticks • Ran Ethernet when it was coax • Built servers when SCSI What to Check What to do was a dirty word and • SQL Server Buffer Manager: Page • Add memory Life Expectancy > 300 (seconds) • Add memory RAID was used to get • Improve disk performance rid of bugs • Add another SQL instanceCopyright 2013 AvailTek LLC – All Rights ReservedVisit: http://www.SharePointShepherd.com 1
    • Top 10 Non-SharePoint Technical Issues That Can Doom Your 3/3/2013Implementation Platter Around the mulberry bush… Arm Head It Bugs Me! 9. SAN Configuration What You’ll See What’s Wrong • Slow performance, especially initial • Disks aren’t producing enough IOPS loading of a site RAID 1+0 RAID 5 • Less effectiveness in adding RAM to the SQL server A1a A1b A2a A2b A1 A2 A3 Ap B1a B1b B2a B2b B1 B2 Bp B3 C1a C1b C2a C2b C1 Cp C2 C3 D1a D1b D2a D2b Dp D1 D2 D3 What to Check What to do • Average time per read < 20ms • Reconfigure from RAID 5/6(DP) to Disk 0 Disk 1 Disk 2 Disk 3 Disk 0 Disk 1 Disk 2 Disk 3 • Average time per write < 20ms RAID 10 • RAID configuration is RAID 10 not • Buy more, faster, smaller disks 5/6 (DP)Copyright 2013 AvailTek LLC – All Rights ReservedVisit: http://www.SharePointShepherd.com 2
    • Top 10 Non-SharePoint Technical Issues That Can Doom Your 3/3/2013Implementation 8. Load Balancer Configuration 7. SharePoint Server Disk What You’ll See What’s Wrong What You’ll See What’s Wrong • First hit response times, even after • The load balancer isn’t configured • SharePoint Server disks get filled up • The full text (non-SQL) indexes get the first hit for session affinity (sticky sessions) copied to every query server (and they’re big) What to Check What to do What to Check What to do • Session affinity • Configure the load balancer for • Every query server has 30% of the • Add disks until you have enough • Session identification session affinity (sticky sessions) total size of everything you want to search 5. Lack of Quality 6. Core Network (Assurance Environment) What You’ll See What’s Wrong What You’ll See What’s Wrong • Weird SharePoint errors • Insufficient bandwidth between • Unknown problems in your • There’s no way to validate your code • Erratic and unpredictable servers production environment and configuration changes performance • Packet loss What to Check What to do What to Check What to do • No Firewall between servers • Remove firewall and proxy servers • The value of downtime in • Get at least one controlled • Network adapter transmit buffer < 1 between SharePoint and SQL production to the organization environment before production • Ensure all network ports plugged in and bonded • Plug all SharePoint servers into a single switchCopyright 2013 AvailTek LLC – All Rights ReservedVisit: http://www.SharePointShepherd.com 3
    • Top 10 Non-SharePoint Technical Issues That Can Doom Your 3/3/2013Implementation 4. Crosstalk Between 3. Abstract IP Environments What You’ll See What’s Wrong What You’ll See What’s Wrong • Random outages in production • Production is referencing • All clients look like they’re coming • The proxy server or load balancer is • Random performance issues in development resources (which are from one IP address NATing (abstracting) the IP address production being shutdown) • Difficult to diagnose specific client problems when you can’t find them What to Check What to do What to Check What to do • Production can not communicate • Put production (and QA) on a • Configuration of the proxy server or • Reconfigure the network to transmit with development separate subnet that can’t talk to load balancer client IP addresses to the server development resources • IIS Logs to verify client IP addresses are being recorded 2. Lack of Monitoring 1. Login Prompts What You’ll See What’s Wrong What You’ll See What’s Wrong • Nothing • You can’t fix what you can’t find • Prompts for login (like every 30 • IE with your web site not in the seconds) Intranet zone What to Check What to do What to Check What to do • Monitoring options available to you • Install monitoring • IE settings • Set a group policy • Configure monitoring • Time synchronization • Make workstations a member of the domainCopyright 2013 AvailTek LLC – All Rights ReservedVisit: http://www.SharePointShepherd.com 4
    • Top 10 Non-SharePoint Technical Issues That Can Doom Your 3/3/2013Implementation Thank You Rob Bogue Shepherd@SharePointShepherd.com (317) 572-5310Copyright 2013 AvailTek LLC – All Rights ReservedVisit: http://www.SharePointShepherd.com 5