Farm Management Basics SharePoint Saturday-Omaha June 13, 2015 Bill Lang Senior Analyst, ECM Lincoln Electric System 1
Agenda LES Information Farm Landscape Tools Components Outsource 2
LES Information 3
Lincoln Electric System (LES) Municipal electric utility serving approximately 200 square miles within Lancaster County, NE (Lincoln area) 131,900+ Retail Customers 470+ Employees Generation resources: Coal, Renewable, Gas & Oil, and Wholesale Purchases Rates are among the lowest in the nation Overall average rates in lowest 12% in recent nationwide survey of 106 cities 4
Myself Senior Analyst, ECM Information Infrastructure & Governance Department within Technology Services Division SharePoint since 2008 Administration Development Support 5
Farm Landscape 6
Typical Farm 7
Typical SharePoint Farm Components WFE Web Front End APP Application DB Database Others depending on requirements Configurations All-In-One Single or multiple servers for components 8
LES SharePoint Farms On-premises; virtual servers SharePoint 2007 MOSS SharePoint 2010 Foundation SharePoint 2010 Server SharePoint 2013 Enterprise Support and management 9
LES SharePoint Farms SharePoint 2007 MOSS Production (2-WFE, 2-APP, 2-DB) Sandbox (1-WFE/APP, 1-DB) Developments (6-single server) SharePoint 2010 Foundation ExtraNet (1-WFE/APP, 1-DB) SharePoint 2010 Server Development (single server) 10
LES SharePoint Farms SharePoint 2013 Enterprise Production (2-WFE, 2-APP, 1-DB) QA/Staging (2-WFE, 2-APP, 1-DB) Sandbox (1-WFE/APP, 1-DB) DEV/Test (1-WFE, 1-APP, 1-DB) Developers (2-single server) 11
Tools 12
Tools 13
Tools Variety of tools available Windows Server SharePoint SQL 3 rd Party Usage Manual Scripts Automated 14
Tools Windows Events IIS WMI SharePoint Central Administration Unified Logging System (ULS) 15
Tools SQL System and custom queries 3 rd Party ControlPoint Diagnostic Manager DocAve SPDocKit Etc. 16
Tools Examples: Windows Events IIS WMI SharePoint CA ULS ULS Viewer SQL Database growth 17
Tools Usage Manual View page; open log file Script WMI example Automatic Diagnostic Manager SPDocKit 18
Components 19
Components Management Categories Health checks Backups Server updates SharePoint updates Report and manage 20
Components Frequency depends on: Production, Development, etc. How critical to business SLA Identify importance for operation Can t check everything everyday due to time and expense Identify most critical Adjust over time 21
Components Health Checks All servers Each server is available Utilization: cpu, disk, memory SharePoint SQL Central administration ULS Pages (CA, key pages, load times, etc.) DB growth 22
Components Health Checks Examples: CA Health ULS Long running jobs; permissions; etc. Script WMI gather data Diagnostic Manager Dashboard ControlPoint Queries, manage, reports 23
Components Health Checks Diagnostic Manager: 24
Components Backups Types Server file system SQL SP Content VM Snapshot Frequency Full and incremental Retention cycles Replication 25
Components Backups Examples: Servers (OS, Data, etc.) Databases (SQL compression and backup) SharePoint (GUI, CA, Scripts) Retention Replicated to multiple locations Full and incremental 26
Components Backups SP Backup: 27
Components Server Updates Windows Server Update Services (WSUS) Downloads updates and hotfixes from the Microsoft Update website Manual release or rules for automatic release Distributes released updates/hotfixes to computers on a network Installation on servers depends on Windows configuration (automatic, admin control) 28
Components Server Updates Windows Server Update Services (WSUS) Example from WSUS 29
Components Server Updates Windows Server Update Services (WSUS) Example from SP server 30
Components Server Updates Example: Schedule Process 31
Components Server Updates Schedule: Example Patch Process Calendar Sunday Monday Tuesday Wednesday Thursday Friday Saturday March 1 2 3 4 5 6 7 8 9 10 11 12 13 14 12:00 AM 6:00 AM Day 0: Patch Tuesday 12:00 AM 8:00 AM WSUS downloads MS updates Servers download specific updates Day 1 2: Identify updates to be installed) 8:00 AM 5:00 PM Day 3: Initial Research; Send Report 15 16 17 18 19 20 21 1:00 PM 3:00 PM Day 6: D1 Group Installs 4:00 PM 5:00 PM Day 6: D1 Group Restarts and Validation Day 7 8: Verify Operation 1:00 PM 3:00 PM Day 9: D2 Group Installs 4:00 PM 5:00 PM Day 9: D2 Group Restarts and Validation Day 10 13: Verify Operation 22 23 24 25 26 27 28 Day 10 13: Verify Operation 8:00 AM 5:00 PM Day 13: Final Research; Send Report 3:00 PM 5:00 PM Day 14: P1 Group Installs 6:00 PM 9:00 PM Day 14: P1 Group Restarts and Validation Day 15 16: Monitor and Confirm Operation 29 30 31 April 1 2 3 4 3:00 PM 5:00 PM Day 21: P2 Group Installs 9:00 PM 11:00 PM Day 21: P2 Group Restarts and Validation Day 22 23: Monitor and Confirm Operation 32
Components Server Updates Process: 33
Components SP Updates Types Service Packs (SP) Cumulative Updates (CU) Windows Update (KB) 34
Components SP Updates Example: Not automatically installed on release Treat as a project; cycle through environments Tasks Research Plan Trial Test and verify Continue with next environment 35
Components Report and Manage SharePoint SQL Scripts 3 rd Party 36
Components Report and Manage Examples: SQL (DB growth) Scripts and task schedules Tools ControlPoint SPDocKit SYDI 37
Outsource 38
Outsource Reasons I was doing minimal health checks and basically installing all updates; minimal research Reactive; not proactive FTEs allocated to other areas SP2013 migration project Use internal staff for projects, support, and project management Use external resources for repetitive operations, research, expertise 39
Q & A 40
Thank You Bill Lang Senior Analyst, ECM (402) 467-6898 blang@les.com 41