The document discusses effective SharePoint architecture and provides recommendations for server roles, hardware specifications, and database configuration. It recommends a farm architecture with two web front end servers, two application servers, and a SQL Server 2012 cluster with two nodes. The web front end and application servers should each have 16GB RAM, 4 CPU cores, and two hard drives. SQL servers should have 32GB RAM, 8 CPU cores, and five hard drives configured for data, tempdb, and backup files. It also provides tips for securing SharePoint such as implementing firewalls, running security analyzers, and following hardening guidance.

1. Effective SharePoint Architecture
Alistair Pugin
Datacentrix
#SPSSTHLM08, May 21st, 2016

2. 







3. 3

4. 4
How
Where do you Start
• Farm Architecture
• Virtualization??

5. 

Web Front Ends
All Application
Server Roles
SQL 2012
SQL Server installed and configured
to support SQL clustering, mirroring,
And AlwaysOn, AlwaysOn requires
SQL Server 2012.
Web Front Ends (2)
 16 GB RAM
 4 Cores CPU
 100GB HDD (C:)
 150GB HDD (E:)
All Application Server Roles (2)
 16 GB RAM
 4 Cores CPU
 100GB HDD (C:)
 150GB HDD (E:)
SQL Server 2012 (2)
 32 GB RAM
 8 Cores CPU
 100GB HDD (C:)
 500GB HDD (E:Data)
 50GB HDD (F:Temp)
 1.5TB HDD (G:Back)
SharePoint 2013 Production Environment
Web Front Ends
All Application
Server Roles
SQL 2012
SQL Server installed and configured
to support SQL clustering, mirroring,
And AlwaysOn, AlwaysOn requires
SQL Server 2012.
Web Front Ends (2)

 4 Cores CPU
 100GB HDD (C:)
 150GB HDD (E:)
All Application Server Roles (2)

 4 Cores CPU
 100GB HDD (C:)
 150GB HDD (E:)
SQL Server 2012 (2)

 6 Cores CPU
 100GB HDD (C:)
 500GB HDD (E:Data)
 50GB HDD (F:Temp)
 1.5TB HDD (G:Back)

6. 
Web Front Ends
All Application
Server Roles
SQL 2012
SQL Server installed and configured
to support SQL clustering, mirroring,
And AlwaysOn, AlwaysOn requires
SQL Server 2012.
Web Front Ends (2)
 16 GB RAM
 4 Cores CPU
 100GB HDD (C:)
 150GB HDD (E:)
All Application Server Roles (2)
 16 GB RAM
 4 Cores CPU
 100GB HDD (C:)
 150GB HDD (E:)
SQL Server 2012 (2)
 32 GB RAM
 6 Cores CPU
 100GB HDD (C:)
 500GB HDD (E:Data)
 50GB HDD (F:Temp)
 1.5TB HDD (G:Back)
Web Front End
All Application
Server Roles
Web Front End
 8 GB RAM
 4 Cores CPU
 100GB HDD (C:)
 150GB HDD (E:)
All Application Server Roles
 12 GB RAM
 4 Cores CPU
 100GB HDD (C:)
 150GB HDD (E:)
SQL Server 2012
 24 GB RAM
 6 Cores CPU
 100GB HDD (C:)
 500GB HDD (E:Data)
 50GB HDD (F:Temp)
 1.5TB HDD (G:Back)
SQL 2012

7. Operating System
• CPU – Over commit
• Memory – Dynamic?
• Network – IPV4
• Page Files – System Managed not
Auto
• Antivirus
• Disable Recycle Bin
7

8. 






 TCP 22233-22236 (Distributed
Cache)
 TCP 808 (WCF)
 TCP 5725 (FIM Sync)
 TCP+UDP 389 (LDAP)
 TCP 809 (Office Web Apps)
 TCP+UDP 88 (Kerberos)
 TCP+UDP 53 (DNS)
 UDP 464 (Kerberos)
 Make sure that the first server with
Distributed Cache has its firewall
rule set to allow for Inbound ICMP
(ICMPv4).

10. SQL/SharePoint “Did you know’s”
 SharePoint has its own Collation
Latin1_General_CI_AS_KS_WS!!
 NTFS Allocation size (chkdsk) – SQL read and
writes 64k
 How many SQL disks do you use?? Average?
Data/Log/Temp
 Fix your RAM on your SQL boxes. Why?

11.  Fill Factor. Indexing and data storage
performance – set to 80 to support growth
and minimize Fragmentation
 All DB’s are created from MODEL – Set your
DB’s autogrow size correctly from the get go
 Auto-create Statistics -- SharePoint does not
support it
SQL/SharePoint “Did you know’s”

12. SQL/SharePoint “Did you know’s”
 Other options:
 Parallelism – keep it at 1 for optimal query results
 Instant File Initialization
 tempdb size – Busiest DB so give it a decent initial size
(keep all autogrow the same across all settings)
 Configure SharePoint to Autogrow after the DB’s have
been created
 Shrinking Vs Backup Logs – Rather
backup and let it flush instead of shrink

13. SQL/SharePoint “Did you know’s”
 Compress your backups
 Recovery Mode – Simple
 SharePoint logging grows exponentially
 Create multiple Tempdb
files (.ndf) on multiple
drives or RAID 10 for drives
hosting Tempdb files
 Defragment drives
containing content
database files
 Don’t rebuild or manage
indexes of SharePoint DB’s
 NTFS block size. Does
anyone care???
 Hide SQL from other
computers
 Disable Auto-Create
Statistics
 Trace Flags

14. SharePoint DB’s
1

15. 








 Secure Store database
 Usage database
 Subscription Settings database
 Profile database
 Synchronization database
 Social Tagging database
 Word Automation Services
database
 Managed Metadata database
 Machine Translation Services
database

16. 







17. 
105GB

19. 1
Hardening

20. 








21. 





22.  Implement Firewall Layer between server layers
 Run “Best Practice Security Analyzer”
 https://technet.microsoft.com/en-us/library/hh831400.aspx
 Follow “Server Hardening Guidance”
 https://technet.microsoft.com/en-us/library/cc262849.aspx

23. On-Premises: Server Isolation
Block Unknown & Disallowed Traffic
Allow Known Traffic

24. 2
Q and A

25. Diamond
Platinum
Gold
Lunch SharePint

26. Thank you!