>
CalShare
UC Berkeley00 Implementation of MOSS 2007
Presented by
Michael Leefers
Topics
Service Evolution
Implementation the Technical
Perspective
Implementation the Business
Perspective
CalShare by the Numbers
Recouping Cost
Lessons Learned
Major Challenges
Service Evolution
Pilot
Production (Internal Customers
only)
Production Service (SharePoint
2003)
Production Service (SharePoint
2007)
Implementation the Technical
Perspective
2 Load Balanced Web Servers
Virtual Machines: VMware
ESX
1 Application Server (Search, Excel Services and Central Admin)
Virtual Machine: VMware
ESX
1 SQL Server 2005
Dell Blade 1855
Storage provided by SAN
Implementation the Technical
Perspective
Implementation the Technical
Perspective
Implementation the Technical
Perspective
Disaster Recovery
Application and Web Servers
Backed up Nightly.
Databases are fully backed
up nightly, transaction logs are dumped every 2 hours and moved to another
Disk for backup.
Backup and Restore
Currently we only offer
the built in recycle bin as a tool used for the restore of files.
Implementation the Business
Perspective
What we 00he CalShare
Team00provide.
Monitor, Manage, and Patch
the SharePoint Infrastructure.
Trouble shoot any application
issues.
Creation of a Site Collection
with 1GB of Storage.
Orientation and turnover
of new site (Handing over the Keys).
Top level application support.
Purchase and Maintain SharePoint
Server Licenses.
Implementation the Business
Perspective
What each SharePoint Site
Collection Administrator should provided.
Complete administration
of their site.
First level support for
all users issues and questions.
Keep themselves informed
on changes in the service.
Agree to conditions set
forth in SLA.
Purchase necessary CAL00
for their users.
CalShare by the Numbers
61 Site Collections and
growing
Content DB 46GB and growing
Disk Space allocated for
Content DB 100GB
Department sizes that use
the service range from 5+ people to over 200
Users per site 5 to 300
Average Bandwidth Activity
MB/day 5MB-600MB
Recouping Cost
SharePoint as a Service the Recharge
Model
Identify Costs
Hardware
Software
System/Application SA Time
Support SA Time
Lessons Learned
Support model not sustainable.
No training: Service
is dead if no one knows how to use it.
Site Collection Administrators
can not adequately support users or sites.
Users can not effectively
use application.
Users not sure where to
go for support.
Need access to some development
resources.
Major Challenges
Getting the word out about
Service.
Complex nature of educational
environment.
Operating Systems: Windows,
Mac, Unix, Linux
Browsers : IE, Firefox,
Safari
Application Integration:
No Office, Office XP, 2000- 2003, or 2007.
Licensing Model
Questions?
Contact Info
Michael Leefers
mleefers@berkeley.edu
1
2
3
Web VM00 1955 Blade. 2CPU 1GB RAM
App VM 1955 Blade 1CPU 512MB RAM
4
Web VM00 1955 Blade. 2CPU 1GB RAM
App VM 1955 Blade 1CPU 512MB RAM
5
Web VM00 1955 Blade. 2CPU 1GB RAM
App VM 1955 Blade 1CPU 512MB RAM
6
Web VM00 1955 Blade. 2CPU 1GB RAM
App VM 1955 Blade 1CPU 512MB RAM
7
8
9
Web VM00 1955 Blade. 2CPU 1GB RAM
App VM 1955 Blade 1CPU 512MB RAM
10
11
12
13
14
download Slide 1
