Hosted SharePoint

Part 3/3: Office Live as a WSS solution

Speaker Namespeaker@microsoft.comhttp://blogs.msdn.com/speaker Microsoft Corporation

Hosted SharePoint

Agenda

• What is Office Live?• Sharing and questions regarding

– Topology– Capacity & server utilization– WSS as a platform– Authenticated (private) sites– Anonymous (public) sites– Migration from WSS v2 to v3– Monitoring and operations– “Dos” and “Don’ts” of large WSS deployments

What is Office Live?

• IT for small business hosted by Microsoft• Built on Sharepoint:

– Public web site and domain– Small business applications– Vanilla hosted Sharepoint– Platform for third-party partners to build applications

• Web site traffic reports• Company-branded e-mail• Sales and marketing services

Sign up – it's Free!

• http://officelive.fr in France• Basics: free• Essentials: free during Beta• Premium: free during Beta

Public Site Topology

• Anonymous access internet web site• 2 clusters• 4 Sharepoint V3 Web Front End Machines• 2 SQL 2005 Mirrored Machines

Private Site Topology

• Authenticated access intranet web site• 2 clusters• 4 Sharepoint V3 Web Front End Machines• 2 SQL 2005 Mirrored Machines• 1 Sharepoint V3 WFE Search indexer/query machine• 1 SQL 2005 Search database machine

Topology

Web Front End Hardware

• HP ProLiant DL385• 2x 2.4Ghz dual core AMD® O280 CPU• 4GB PC3200 SDRAM• 2x 146GB 10k SCSI HDD Raid 1• Dual port PCI-X Gigabit Ethernet

SQL Server Hardware

• HP ProLiant DL585• 4x 2.2Ghz dual core AMD® O848 CPU• 4GB PC2700 SDRAM• Dual port embedded Gigabit Ethernet• 2x 72GB 15K SCSI (RAID 1: OS partition)• 28*300 10K SCSI

– RAID 10: 1.9TB data (14 drives)– RAID 1: 270GB SQL logs (2 drives)– Raid 5: 1TB temporary DB (5 drives)– Raid 5: 1TB temporary DB (5 drives)

Capacity• Same for Public and Private

– 2 clusters– 5 content DBs per cluster– 1.8 TB storage per cluster– Roughly 150 GB used per cluster

• Current public cluster usage– 240k sites– 24k sites per content DB

• Current private cluster usage– 40k sites– 4k sites per content DB

Server Utilization

SQL Back EndsCPU Usage Log Disk

UtilizationData Disk Utilization

Private 3% 1% 15%Public 3.6% 2.5% 35%

Web Front Ends

CPU Usage

Request Execution Time

Disk I/O Utilization

AppPool Recycle

Recycle Period

TCP Connections

Private 0.5% 0.5 sec 2% 1.2 GB 6 hours 27

Public 9% 0.3 sec 11% 1.2 GB 6 hours 160

WSS Integration

• ASP.NET Membership Provider for Windows Live ID– Replaces built-in Windows authentication– Required special hooks to enable search

• Automated backup/restore mechanism– SQL backup of content DBs– Group user-initiated restore requests by content DB

• Backup DB is temporarily loaded and sites are restored– Implements backup retention policy

• Purges old backups no longer required• Consistent with various legal and privacy policies

• Storage and Bandwidth limiting features built on WSS base functionality

WSS in Public Sites

• UI Rendering is straight ASP.NET; not WSS• WSS storage API for sites• WSS host-header mode for domains• WSS utility API for string normalization, etc.• FPRPC/DAV access enables customers to bring their own

sites

WSS in Private Sites• Hosted WSS is a natural fit for our customers• Office Live ships additional small business applications

– Generally implemented as SharePoint templates– Event Handler DLL to enforce referential integrity between lists

• Partner/developer story– Full WSS web service API– WSS Templates– Sharepoint Designer 2007– Office Client applications– No server code execution

Monitoring

• Monitoring– MSN’s TMF monitors http requests from outside the datacenter– Perf counter monitoring of Windows, SQL, and Office Live (not

WSS)– Eventlog monitoring of all technologies– ULS used for all logging

• Incident Response– Tier 1 ops: MSN datacenter– Tier 2 ops: Office IPO team– Product team

"Do's"

• Enable App Pool recycling• Move to 64 bit when you can• Plan WSS migration carefully• Write WSS apps in a way that can be patched• Plan for heavy SQL I/O• Use SQL 2005 SP1 Mirroring• Practice patching with 0 downtime

"Don’ts"

• Invent process on the fly• Have any manual steps in deployment• Neglect monitoring of partner dependencies• Under-spend on search hardware

QUESTIONS?End of Part 3/3