Farm Management Basics

(1)

Farm Management Basics

SharePoint Saturday-Omaha

June 13, 2015

Bill Lang

Senior Analyst, ECM

Lincoln Electric System

(2)

Agenda

 LES Information  Farm Landscape  Tools  Components  Outsource

(3)

(4)

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

(5)

Myself

Senior Analyst, ECM

 Information Infrastructure & Governance Department within Technology Services Division

 SharePoint since 2008

– Administration – Development – Support

(6)

(7)

(8)

Typical SharePoint Farm

• Components

 WFE – Web Front End  APP – Application

 DB – Database

 Others depending on requirements

• Configurations

 All-In-One

(9)

LES SharePoint Farms

On-premises; virtual servers

 SharePoint 2007 MOSS

 SharePoint 2010 Foundation  SharePoint 2010 Server

 SharePoint 2013 Enterprise  Support and management

(10)

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

(11)

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)

(12)

(13)

(14)

Tools

Variety of tools available

 Windows Server  SharePoint  SQL  3rd _Party

Usage

 Manual  Scripts  Automated

(15)

Tools

Windows

 Events  IIS  WMI

SharePoint

 Central Administration

(16)

Tools

SQL

 System and custom queries

3

rd

Party

 ControlPoint  Diagnostic Manager  DocAve  SPDocKit  Etc.

(17)

Tools

Examples:

 Windows – Events – IIS – WMI  SharePoint – CA – ULS – ULS Viewer

(18)

Tools

Usage

 Manual

– View page; open log file

 Script

– WMI example

 Automatic

– Diagnostic Manager – SPDocKit

(19)

(20)

Components

Management Categories

 Health checks  Backups  Server updates  SharePoint updates  Report and manage

(21)

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

(22)

Components – Health Checks

All servers

 Each server is available

 Utilization: cpu, disk, memory

SharePoint

 Central administration  ULS

 Pages (CA, key pages, load times, etc.)

SQL

(23)

Components – Health Checks

Examples:

 CA Health  ULS

– Long running jobs; permissions; etc.

 Script

– WMI gather data

 Diagnostic Manager

– Dashboard

(24)

Components – Health Checks

(25)

Components – Backups

Types

 Server file system  SQL

 SP Content  VM Snapshot

Frequency

 Full and incremental  Retention cycles

(26)

Components – Backups

Examples:

 Servers (OS, Data, etc.)

 Databases (SQL compression and backup)  SharePoint (GUI, CA, Scripts)

Retention

 Replicated to multiple locations  Full and incremental

(27)

Components – Backups

(28)

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)

(29)

Components – Server Updates

Windows Server Update Services (WSUS)

(30)

Components – Server Updates

Windows Server Update Services (WSUS)

(31)

Components – Server Updates

Example:

 Schedule  Process

(32)

Components – Server Updates

Schedule:

March 1

Sunday Monday Tuesday Wednesday Thursday Friday Saturday

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 April 1 2 3 4 12:00 AM ‐ 6:00 AM Day 0: Patch Tuesday 3:00 PM ‐ 5:00 PM Day 14: P1 Group Installs 3:00 PM ‐ 5:00 PM Day 21: P2 Group Installs Day 7 ‐ 8: Verify Operation 1:00 PM ‐ 3:00 PM Day 6: D1 Group Installs Day 10 ‐ 13: Verify Operation Day 10 ‐ 13: Verify Operation Day 22 ‐ 23: Monitor and Confirm Operation Day 15 ‐ 16: Monitor and Confirm Operation Example Patch Process Calendar 8:00 AM ‐ 5:00 PM Day 3: Initial Research; Send Report 8:00 AM ‐ 5:00 PM Day 13: Final Research; Send Report 4:00 PM ‐ 5:00 PM Day 6: D1 Group Restarts and Validation 6:00 PM ‐ 9:00 PM Day 14: P1 Group Restarts and Validation 9:00 PM ‐ 11:00 PM Day 21: P2 Group Restarts and Validation 12:00 AM ‐ 8:00 AM  WSUS downloads MS updates  Servers download specific updates Day 1 – 2: Identify updates to be installed) 1:00 PM ‐ 3:00 PM Day 9: D2 Group Installs 4:00 PM ‐ 5:00 PM Day 9: D2 Group Restarts and Validation

(33)

Components – Server Updates

(34)

Components – SP Updates

Types

 Service Packs (SP)

 Cumulative Updates (CU)  Windows Update (KB)

(35)

Components – SP Updates

Example:

 Not automatically installed on release

 Treat as a project; cycle through environments  Tasks

– Research – Plan

– Trial

– Test and verify

(36)

Components – Report and

Manage

 SharePoint  SQL  Scripts  3rd _Party

(37)

Components – Report and

Manage

Examples:

 SQL (DB growth)

 Scripts and task schedules  Tools

– ControlPoint – SPDocKit – SYDI

(38)

(39)

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

(40)

(41)

Thank You

Bill Lang

 Senior Analyst, ECM  (402) 467-6898