Upload
michael-noel
View
2.512
Download
0
Embed Size (px)
DESCRIPTION
Citation preview
SETEMBRO, 2010 | SÃO PAULO
Michael NoelPartnerConvergent Computing
Arquitetura e topologias do SharePoint 2010
CÓDIGO DA SESSÃO: OSP301
3
Michael Noel
• Author of SAMS Publishing titles “SharePoint 2010 Unleashed,” “SharePoint 2007 Unleashed,” “SharePoint 2003 Unleashed”, “Teach Yourself SharePoint 2003 in 10 Minutes,” “Windows Server 2008 R2 Unleashed,” “Exchange Server 2010 Unleashed”, “ISA Server 2006 Unleashed”, and many other titles .
• Partner at Convergent Computing (www.cco.com / +1(510)444-5700) – San Francisco, USA Bay Area based Infrastructure/Security specialists for SharePoint, AD, Exchange, Security
4
AgendaWhat we will cover
Physical SharePoint Server ArchitectureArchitecture Planning ChangesSharePoint DatabasesService Applications
Virtual SharePoint Server ArchitectureVirtual Host GuidelinesVirtual Guest GuidelinesSample Virtual Environments for SharePoint 2010
5
SharePoint 2010 Architecture Planning Changes
6
• Capacity planning is similar to MOSS2007• Usage now broken down by workload• A workload is defined by the usage
characteristics and the user base. • We still need the following:
• Total Users (estimated)• Active Users• % Active Users• Peak concurrent users• % Peak concurrent users
• Don’t use the SharePoint System center capacity planning tool!!!
SharePoint 2010 Architecture PlanningUser Workloads
7
• Try not to over/undersize deployment
• Determine peak demand benchmark
• Plan for unplanned peak ‘spikes’
• Use reference architectures as a starting point
• Stay within Microsoft recommended boundaries
(http://technet.microsoft.com/en-us/library/cc262787.aspx)
Model
Design
Pilot, Test,
OptimizeDeploy
Monitor and
MaintainSharePoint Server 2010Capacity Management
Model
SharePoint 2010 Architecture PlanningCAPACITY MODEL
8
SharePoint 2010 Infrastructure Improvements
9
SharePoint 2007 SharePoint 2010
Windows SharePoint Services (WSS) 3.0 SharePoint Foundation 2010
Microsoft Office SharePoint Server (MOSS) 2007: Standard
SharePoint Server 2010: Standard Client Access License
Microsoft Office SharePoint Server (MOSS) 2007: Enterprise
SharePoint Server 2010: Enterprise Client Access License
SharePoint Internet Connector License SharePoint Server 2010 for Internet Sites, Standard
* SharePoint Server 2010 for Internet Sites, Enterprise
FAST Search for SharePoint* FAST Search Server 2010 for SharePoint
SharePoint Designer 2007 SharePoint Designer 2010
Office Groove 2007 SharePoint Workspace 2010
SharePoint 2010 Infrastructure ImprovementsVersion and Edition Changes
10
• SSP concept replaced with Service Applications• Each service runs independently, providing
application isolation• All SSP functionality moved to databases, so
they can be consumed from multiple servers more easily
• New products use this framework• Get-SPServiceApplication cmdlet shows list of
Service Applications
SharePoint 2010 Infrastructure ImprovementsService Applications
11
• Stores farm configuration data• Mostly unchanged from 2007 ConfigDBConfig• Used to store documents, sites, lists, etc.• Mostly unchanged from 2007, Central Admin also has Content DBContent• Used by Usage and Health Data Collection Service• Temporarily stores health monitoring and usage data for use in reportsLogging• Created for the Search Service, 2007 equivalent was SSP DB• One Admin DB created per Search applicationAdministration• Also used for Search Service• Stores crawled propertiesProperty• Also used for Search Service, 2007 equivalent was Search DB• Drives crawl component, hosts crawled dataCrawl• Used by Web Analytics Service to analyze traffic• Stores fact data, queued batch data, and asset metadataStaging• Also used by Web Analytics Service• Stores report data, diagnostics info, etc.Reporting
SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part I)
12
• Used by Managed Metadata Service• Stores Managed Metadata for use data layerTerm Store• Used by the State Service• Stores temporary state info for InfoPath Forms ServicesState• Part of the User Profile Service• Stores user and associated informationProfile• Used by User Profile Service• Stores Configuration and Staging Data for Prof SyncSynchronisation• Also used by User Profile Service• Stores social tags and notes from usersSocial Tagging
• Used by Business Connectivity Service to store external objectsBCS• Used by Secure Store Service to map credentials• Replaces SSO DB in 2007, can be used by ERP/DRM SystemsStore• Not a SharePoint Database, but included in this list as it is critical to SP• Highly critical for performance! Do not underestimate!tempDB
• Other Services Databases (Others)
SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part II)
13
• New database size recommendations• Collaboration or write-heavy workloads: 200 GB• Document management or read-heavy workloads:
1 TB• Rule of thumb for sizing content databases is
0.75 IOPS per GB. (separate spindles to achieve IOPS!!)
• Consider using Remote BLOB storage (RBS): • Sites that contain large files that are infrequently
accessed, such as knowledge repositories.• Sites with terabytes of data.• Sites that host video or media files.
SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part III)
14
• Isolation of data, operational services, and management• Partitioning of Data• Usage Isolation• Administrative Isolation• Customisations• Operations
• New functionality targeted at hosting SharePoint sites• More centralised control over hardware and data storage• Simplified management and scriptability• Block setup of ‘rogue’ SharePoint deployments• “Site subscriptions” group site collections based on tenants • Features and services mapped to tenants
SharePoint 2010 Infrastructure ImprovementsMulti-tenancy – A Quick Overview
15
• The ability to uniquely separate each customer on a shared environment
WA
SC SC SC SC SC
Tenant 1
SC SC SC
Tenant 2
SC SC
21
SA
SharePoint 2010 Infrastructure ImprovementsSharePoint 2010 Databases (Part I)
16
SharePoint 2007 vs. SharePoint 2010 Server Architecture Models
17
2007
SharePoint 2007 vs. 2010 RolesDedicated SQL Database Server (Also Similar)
2010
18
2007
SharePoint 2007 vs. 2010 RolesSmallest Highly Available Farm
2010
19
SharePoint 2010 ArchitectureMedium Sized Farm
20
SharePoint 2010 ArchitectureLarge Farm
21
Restructuring SharePoint Content
22
• Change new SP2010 Farm to model of distributed content databases, within reason (more than 50 per SQL instance is not recommended)
• Distribute content across Site Collections from the beginning as well
• Allow your environment to scale and your users to ‘grow into’ their SharePoint site collections
• Consider MultiTenancy for hosting
Content Database and Site CollectionsRearchitecting for Scalability
23Sam
ple
SP Lo
gica
l Arc
hite
ctur
e
24
• In-Place upgrade (not recommended)• Visual upgrade• Database Attach Upgrade• STSADM –Export of sub-webs• Third-Party Migration Tools
• Metalogix• Quest• AvePoint• Etc…
RESTRUCTURINGUPGRADE / MIGRATION
25
SharePoint 2010 Virtual Farm Architecture
26
Can you Virtualize SharePoint 2010 Production Servers?
Answer is yes, you can (it is supported), but with caveatsMust architect the environment properly!Not taking into account Disk/Proc/Mem, and other host and guest environments can make a virtualized environment run slowly
27
Virtual Host Guidelines• Dedicated hosts for SharePoint Virtual Guests• Assume 1GB of memory taken by host OS
(Hyper-V), 3rd party varies• No Software on Host OS! (Except A/V or Backup)
General
• Allocate Direct / Passthrough NICs when possible• Create dedicated NIC for Management• Create dedicated NIC for Failover
NICs
• Dedicated spindles for SharePoint• Dedicated volume for Host OS• Dedicated volume for Guest OS VHDs• Dedicated volume for Databases and Logs
Disk
• Do not overallocate (applies to memory as well)• No more than 2 vCPUs for every Core on host• Ideally closer to 1:1 for most critical systems
2:1 Core/vCPU Ratio
28
SP2010 Role Virtualization
• Excellent Virtualization Candidate• Can be easily provisioned via templatesWeb
• Higher proc/mem requirements, but still good candidate• Often paired with SP2010 Web Role• Requires 2nd Disk for Index
Query/Crawl
• Higher proc/mem requirements, but still good candidate• Low disk requirements compared to other rolesApp
• Requires the most memory, proc, and disk IO• Be cautious when virtualizing, make sure host is scaled• If virtual, be sure to use pass-through or fixed size disks
DB
29
vCPU RAM (Minimum)
RAM (Recommended)
Web Only* 2 6GB 8GB
Service Application Roles Only
2 6GB 8GB
Search/Query Only 2 8GB 10GB
Combined Web/Query/Service Apps
4 10GB 12GB
Database* 4 10GB 16GB
SharePoint Guest Guidelines
30
SharePoint Role VM Guidelines• Fixed size Disk a minimum• Pass-through (raw) disk is recommended, but not
required.• Address Disk I/O (Dedicated spindles, etc.)
Disk
• Created dedicated virtual switch for SharePoint• Use VLAN tagging for Security• Ensure host has redundant network links• Highly consider passthrough NICs
Network
• Load balance like servers across hosts• Install Integration components on servers
(Win2008 R2 automatically does for Hyper-V)General
31
SQL Server VM Guidelines• Passthrough Disk (Raw) strong recommendation
• Dedicated volumes for Logs, DB, OS• Follow best practices for tempDB, others
Disk
• Install in same virtual switch as SP Roles• Use multipathing on hosts• Ensure host has redundant network links• Passthrough NICs dedicated to SQL Important
Network
• Be sure your hosts have the necessary capacity, or you will have performance bottlenecks
• SQL Mirroring and Clustering now supported on virtual guests (KB 956893)
General
32
Sample SharePoint 2010 Virtualized Farm Architecture
33
Allows Organizations that wouldn’t normally be able to have a test environment to run one
Allows for separation of the database role onto a dedicated server Can be more easily scaled out in the future
Virtualized Farm ArchitectureCost-effective Virtual Environment / No HA
34
Server Memory Processors Disk
Virtual host 24GB RAM 2 quad-core (8 cores)
C drive: OS - Windows Server 2008 R2 with Hyper-V; 50GB dedicated volume
D drive: dedicated volume for OS VHDs E drive: 500GB dedicated volume for SQL
Database VHDs F drive: 100GB dedicated volume for SQL
Logs VHDs.
SQL server 10GB RAM 4 virtual processors
C drive: OS - 100GB fixed-size VHD D drive: fixed-size VHD (100GB) dedicated
for SQL logs E drive: fixed-size VHD (500GB) dedicated
for SQL Data
SharePoint Web/Query/App
10GB RAM 4 virtual processors
C drive: OS and Transport Queue Logs; 100GB fixed-size VHD
E drive: 100GB fixed-size VHD for Index/Query
Virtualized Farm ArchitectureCost-effective Virtual Environment / No HA
35
High-Availability across Hosts
All components Virtualized
Uses only two Windows Ent Edition Licenses
Virtualized Farm ArchitectureHighly Available Farm with only Two Servers
36
Server Memory Processor DiskVirtual hosts 48GB RAM 2 quad-core (8
cores) C drive: OS; Windows Server 2008 R2 with
Hyper-V; 50GB dedicated LUN D drive: dedicated LUN for VHDs Raw volume: 100GB dedicated LUN for SQL
Logs Raw volume: 2TB dedicated LUN for SQL
Databases
SQL Servers 16GB RAM 4 virtual processors
C drive: OS; 50GB fixed-size VHD D drive: pass-through dedicated LUN
(100GB) for SQL Logs E drive: pass-through dedicated LUN (2TB)
for SQL Data
SharePoint Web/App Servers
12GB RAM 2 virtual processors
C drive: OS; 100GB fixed-size VHD
SharePoint Search/Query Servers
12GB RAM 2 virtual processors
C drive: OS; 100GB fixed-size VHD D drive: 200GB fixed-size VHD for
Index/Query
SQL Witness Server
2GB RAM 1 virtual processor
C drive: OS; 50GB fixed-size VHD
Virtualized Farm ArchitectureHighly Available Farm with only Two Servers
37
Highest transaction servers are physical
Multiple farm support, with DBs for all farms on the SQL cluster
Virtualized Farm ArchitectureBest Practice Virtual/Physical with HA/Perf
38
Virtualized Farm ArchitectureLarge Virtual Farms
39
NUMA Memory Guidelines
40
NUMA Example: 2x Quad Core, 64GB RAM
8GB 8GB 8GB 8GB
Proc 1
8GB 8GB 8GB 8GB
Proc 2
41
NUMA Example: 2x Quad Core, 8GB RAM
1GB 1GB 1GB 1GB
Proc 1
1GB 1GB 1GB 1GB
Proc 2
42
Virtualization Performance Monitoring
43
Processor<60% Utilization = Good60%-90% = Caution>90% = Trouble
Available Memory 50% and above = Good10%-50% = OK<10% = Trouble
Disk – Avg. Disk sec/Read or Avg. Disk sec/Write
Up to 15ms = fine15ms-25ms = Caution>25ms = Trouble
Virtualization Performance MonitoringPerformance Counters and Thresholds on Hosts
• Network Bandwidth – Bytes Total/sec– <40% Utilization = Good– 41%-64% = Caution– >65% = Trouble
• Network Latency - Output Queue Length– 0 = Good– 1-2= OK– >2 = Trouble
44
Processor (N/A)Available Memory
50% and above = Good10%-50% = OK<10% = Trouble
Disk – Avg. Disk sec/Read or Avg. Disk sec/Write
Up to 15ms = fine15ms-25ms = Caution>25ms = Trouble
Virtualization Performance MonitoringPerformance Counters and Thresholds on Guests
• Network Bandwidth – Virtual NIC Bytes Total/sec– <40% Utilization = Good– 41%-64% = Caution– >65% = Trouble
• Network Latency - Output Queue Length– 0 = Good– 1-2= OK– >2 = Trouble
45
SharePoint Virtualization Support
46
Microsoft Support of SharePoint Virtualization
Microsoft’s official SharePoint support stance is that any SharePoint role or service is supported for hardware Virtualization, including SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2. There are only three requirements for Virtualization that must be satisfied, these are as follows:
Hardware-assisted Virtualization, which is available in processors that include a Virtualization option—specifically processors with Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) technology. Hardware-enforced Data Execution Prevention (DEP) is available and enabled.Either deployed on Microsoft Hyper-V (RTM or R2 version) or a validated third-party hypervisor that is part of the Server Virtualization Validation Program (SVVP) – KB 897615
47
Windows Server 2008 R2 Hyper-V
48
Hyper-V R2 for SP2010Overview
• Hyper-V Introduced shortly after released of Windows Server 2008 RTM
• Hyper-V R2 included with Windows Server 2008 R2• Installs on any edition (Std., Ent, Datacenter)
Versions
• 4x Hyper-V v1 Performance• Support for up to 384 Guests or 512 VPs, whichever
comes first• Core Parking to reduce resource consumption
Performance
• Hot Add Storage• Processor Compatibility (Intel-Intel or AMD-AMD)Flexibility
• Multipathing for network availability• Cluster Shared Storage Support• Live Migration host high availability with VMM 2008• Active/Active failover with no guest downtime
Availability
49
System Center Virtual Machine Manager 2008 R2
50
Virtualization Host and Guest Management PlatformPart of the System Center Management Suite, which includes the following:
System Center Operations Manager 2007System Center Data Protection Manager 2007System Center Configuration Manager 2007 R2System Center Mobile Device Manager 2007System Center Essentials 2007System Center Capacity Planner 2007System Center Service Manager 2010
System Center Virtual Machine Manager (VMM)
51
New version out (VMM 2008 R2)VMM 2008 R2 has P2V (Physical to virtual migration) and V2V (VMware Guest migration to Hyper-V) toolsFor SharePoint, allows for creation of SharePoint template servers that can be quickly provisioned for test farms or for new farm members in productionCan manage both Hyper-V and VMware guests (though must ‘go through’ a Virtual Center server to manage VMware guests.)Self-Service Portal allows end users and remote admins to be able to provision their own virtual machines based on templatesPowerShell support allows for scripted provisioning of SharePoint 2010 or other servers into a farm
System Center Virtual Machine Manager (VMM) 2008 R2
52
Quick SP2010 Farm Provisioning with VMM 2008 R2
1. Create new Virtual Guest (Windows Server 2008 R2)2. Install SP2010 Binaries. Stop before running Config
Wizard3. Turn Virtual Guest into Template, modify template to
allow it to be added into domain4. Add PowerShell script to run on first login, allowing SP
to be added into farm or to create new farmVoila! 15 minute entire farm provisioning…
53
Quick Farm Provisioning with VMM 2008 R2
54
Farm Provisioning Script(Thanks to Muhanad Omar, MVP)$configType = read-host "Do you wish to join an existing Farm? (Y/N)"if ($ConfigType -eq "Y") { $DatabaseServer = read-host "Sounds good. Please specify the name of your SQL Server"; $ConfigDB = read-host "Next, specify the name of your Farm Configuration Database"; $Passphrase = read-host "Finally, please enter your Farm passphrase" -assecurestring } else { $DatabaseServer = read-host "In that case, let's create a new Farm. Please specify the name of your SQL Server"; $FarmName = read-host "Please specify a name for your Farm (ex. SP2010Dev)"; $ConfigDB = $FarmName+"_ConfigDB"; $AdminContentDB = $FarmName+"_Admin_ContentDB"; Write-Host "Please enter the credentials for your Farm Account (ex. CONTOSO\SP_Farm)"; $FarmAcct = Get-Credential; $Passphrase = read-host "Enter a secure Farm passphrase" -assecurestring; $Port = read-host "Enter a port number for the Central Administration Web App"; $Authentication = read-host "Finally, specify your authentication provider (NTLM/Kerberos)"; }if ($ConfigType -eq "Y") { Add-PSSnapin Microsoft.SharePoint.PowerShell; Connect-SPConfigurationDatabase -DatabaseName $ConfigDB -DatabaseServer $DatabaseServer -Passphrase $Passphrase} else { Add-PSSnapin Microsoft.SharePoint.PowerShell; Write-Host "Your SharePoint Farm is being configured..." New-SPConfigurationDatabase -DatabaseName $ConfigDB -DatabaseServer $DatabaseServer -AdministrationContentDatabaseName $AdminContentDB -Passphrase $Passphrase -FarmCredentials $FarmAcct}Initialize-SPResourceSecurityInstall-SPServiceInstall-SPFeature -AllExistingFeaturesNew-SPCentralAdministration -Port $Port -WindowsAuthProvider $AuthenticationInstall-SPHelpCollection -AllInstall-SPApplicationContentWrite-Host "Your SharePoint 2010 Farm has been created!"if ($ConfigType -eq "N") { $WebAppCreation = read-host "Would you like to provision a Web Application using the default Team Site Template? (Y/N)"; if ($WebAppCreation -eq "Y") { $HostHeaderQ = read-host "Would you like to specify a host header? (Y/N)"; if ($HostHeaderQ -eq "Y") { $HostHeader = read-host "Please specify a host header for your Web Application (ex. intranet.contoso.com)"; $URL = "http://"+$HostHeader; Write-Host "Creating your Web Application..."; New-SPWebApplication -Name "SharePoint 2010 Team Site" -Port 80 -HostHeader $FQDN -Url $URL -ApplicationPool "Content_AppPool" -ApplicationPoolAccount (Get-SPManagedAccount $FarmAcct.UserName) -DatabaseServer $DatabaseServer -DatabaseName $FarmName+"_TeamSite_ContentDB_01"; New-SPSite $URL -OwnerAlias $FarmAcct.UserName -Language 1033 -Template "STS#0" -Name "Team Site"; Write-Host "Configuration completed."; } else { Write-Host "Creating a Web Application using the default Team Site Template..." } } else { Write-Host "Configuration completed."; } }Write-Host "Press any key to continue..."$x = $host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")
55
Summary
Understand how to use the Service Application architecture of SharePoint 2010Plan for a distributed data model, especially for document management enviromentsIf considering virtualization of SharePoint, make sure to architect host/guest environment properly
56
Dúvidas?Michael NoelTwitter: @MichaelTNoelwww.cco.com
Por favor preencha a avaliação
© 2008 Microsoft Corporation. Todos os direitos reservados. Microsoft, Windows, Windows Vista e outros nomes de produtos são ou podem ser marcas registradas e/ou marcas comerciais nos EUA e/ou outros países.Este documento é meramente informativo e representa a visão atual da Microsoft Corporation a partir da data desta apresentação. Como a Microsoft deve atender a condições de mercado em constante alteração, este
documento não deve ser interpretado como um compromisso por parte da Microsoft, e a Microsoft não pode garantir a precisão de qualquer informação fornecida após a data desta apresentação. A MICROSOFT NÃO DÁ QUALQUER GARANTIA, SEJA ELA EXPRESSA, IMPLÍCITA OU ESTATUTÁRIA, REFERENTE ÀS INFORMAÇÕES DESTA APRESENTAÇÃO.