Upload
matija-blagus
View
138
Download
0
Embed Size (px)
DESCRIPTION
SharePoint 2013 Best Practices session at Windays 14
Citation preview
Matija BlagusMSCE: SharePoint 2013Acceleratio d.o.o.
Kako izvući (naj)više od vašeg SharePointa 2013
Inspirirani ljudima.
Ugasite mobitele. Hvala.
Inspirirani ljudima.
Sadržaj
Hardver i virtualizac
ija
SQL Server
SharePoint Alati
Inspirirani ljudima.
Hardver i virtualizacija
Hardverski zahtjevi za SharePoint 2013
http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx
Hardverski zahtjevi za SQL Server
http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx
Virtualizacija• Dobro isplanirajte okolinu• NE korisiti dinamičku memoriju! (Distributed
Cache, Search)• Instalirajte Integration services• Ne koristiti legacy mrežne adaptere• Uključiti Jumbo frameove na mreži
http://technet.microsoft.com/en-us/library/ff621103(v=office.15).aspx
Virtualizacija• Koristite VLAN-ove• Isključite time synchronization za SharePoint
virtualke
• RAID 5/10
http://technet.microsoft.com/en-us/library/ff621103(v=office.15).aspx
Topologije
http://technet.microsoft.com/en-us/library/ff607811.aspx
Inspirirani ljudima.
SQL Server
Osnove• UVIJEK koristiti dediciranu instancu za SharePoint• Allocation Unit size za SQL server treba biti 64k
(default 4k)• Postaviti inicijalne vrijednosti baza na planirane
vrijednosti (default 5MB)• Autogrow treba biti u MB, a ne u %• MAXDOP = 1, MAX/MIN memorija • Koristiti alias za pristupanje bazi• < 20 ms izvršenje operacija za TempDBhttp://channel9.msdn.com/Series/Tuning-SQL-Server-2012-for-SharePoint-2013
Optimizacija SQL-a za SharePoint• Collation SQL servera (instance) treba biti
LATIN1_GENERAL_CI_AS_KS_WS• LOG fileovi trebaju biti smješteni na drugi
disk• TempDB treba biti na najbržim diskovima• TempDB treba imati broj fileova jednak broju
logičkih procesora (ne više od 8)• TempDB treba biti u SIMPLE recovery modeu• TempDB bi trebao biti veličine cca. 10%
Content baze
Optimizacija i održavanje SQL-a za SharePoint• Podesiti ModelDB prema vašem okruženju• Baze kreirane kroz Central Administration
neće preuzeti Autogrow vrijednosti od ModelDB baze
• 200 GB po Content bazi• Full backup baza + defragmentacija +
reorganizacija indexa + DBCC CHECKDB = SQL Maintenance plan
• Izbjegavati korištenje Auto-Shrinka• Preporučena verzija SQL 2012 SP1
Inspirirani ljudima.
SharePoint
Osnove• Koristiti PowerShell instalaciju• Servisni računi
(http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=391)• Upoznati se sa limitima SharePointa• SharePoint logovi bi trebali biti na drugom disku• Distributed Cache mora obavezno raditi• Miminalno 2 farme (produkcijska i DEV/TEST/QA)• HTTPS za povezivanje sa Office Web Apps serverom• Isključiti Loopback check
(http://blogs.technet.com/b/sharepoint_foxhole/archive/2010/06/21/disableloopbackcheck-lets-do-it-the-right-way.aspx)
Servisni računiAccount name Role Domain rights Local SharePoint
Server rights neededSQL rights needed
sp_install Used to install SharePoint binaries. Domain User Local administrator on all SharePoint boxes
public, dbcreator, and securityadmin SQL roles. Need to be SysAdmin on SQL when installing the Workflow Manager
sp_farm Farm account. Used for Windows Timer Service, Central Admin and User Profile service
Domain User Local Admin during UPS provisioning, log on locally right
None
sp_webapp App pool id for content web apps Domain User None None
sp_serviceapps Service app pool id Domain User None None
sp_content Default account used by Search Service Application to crawl content
Domain User None None
sp_userprofile1 Account used by the User Profile services to access Active Directory
Must have Replicating Change permissions to AD. Must be given in BOTH ADUC and ADSIEDIT. If domain is Windows 2003 or early, must also be a member of the "Pre-Windows 2000" built-in group.
None None
Distributed Cache• Ako ne radi dobro očekujte probleme sa user
profilima, searchom i autentifikacijom• Ne kombinirati sa Excel, Search, User Profile
servisnom aplikacijom, Project serverom i SQL-om• Za manje farme 2 GB, za srednje i velike između 8
i 16 GB• Otvoriti portove na firewallu – 22233 do
22236+ICMP inbound• Imati pokrenuti Remote Registry servis
Optimizacija SharePointa• Uključiti BLOB i Page output cache• Isključiti Verbose logging ako nije nužno potreban• Premjestiti Search Index na drugi disk• Razdvojiti servisne aplikacije na više servera• Ispravno podesiti antivirus
(http://support.microsoft.com/kb/952167)• Developer Dashboard• Pratiti korištenje resursa i intervenirati prema
potrebi
Update• Instalirati zadnji March 2013 Public Update• NE (još) instalirati Service Pack 1
• Distributed Cache instalirati Cumulative Update 4 za AppFabric 1.1 (nakon što se riješi problem sa SP1)
• Stop-SPDistributedCacheServiceInstance -Graceful
Ostalo• Pratite SharePoint blogove• Napravite load i disaster recovery testove• Ako radite upgrade sa prijašnjih verzija sve
detaljno istestirajte• http://social.technet.microsoft.com/wiki/
contents/articles/12438.sharepoint-2013-best-practices.aspx
Inspirirani ljudima.
Alati
Kako pratiti sve te stvari?• Perfomance Monitor – za praćenje servera• Developer Dashboard – za praćenje brzine
učitavanje stranica SharePointa• Wireshark – analiza mrežnog prometa• ULS Viewer – praćenje SharePoint logova u
čitljivom formatu• Koristiti 3rd party alate za nazdor
servera/mreže/SharePointa
SPDocKit
Zaključak• Optimizacija SharePointa je dugotrajan
proces koji uvelike ovisi o početnom planiranju
• Treba biti proaktivan i ne zanemarivati „male greške”
• Dokumentirajte sve postavke• Naučiti PowerShell
Inspirirani ljudima.
Pitanja i odgovori.
Prezentacija dostupna na:slideshare.net/
Hvala na pažnji!
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.