SharePoint Server 2013 Infrastructure Standard
- Windows Server 2012 R2 with Update should be used as the Operating System for SharePoint hosting servers
- SharePoint 2013 SP1 (with KB2880552) should be used as the SharePoint platform for Company1 Energy unless it is well justified and approved
- SQL Server 2012 SP1 should be used as the back-end database and it has to be aligned with Company1's Database Standards
- If possible, SharePoint Servers should be created based on a pre-defined template followed by the following steps:
- Install any Windows/SharePoint Service Packs/Microsoft Updates
- Install any other SharePoint Updates
- Install add-ons or third party components, if applicable
- Install and Log/Backup/Monitoring Tool
- SharePoint Production and UA Farms should be installed and configured following three tier architecture of SharePoint farm:
- Web Tier should host WFEs (Web Front Ends) to serve web pages and Host query components
- Application Tier should host Application Servers for Central Administration, Service Applications/Services, Search/Crawl Components
- Database Tier should host Configuration Database, Content Databases, BI/Reporting Database, and Search/Crawl/Property Databases that is part of the SharePoint Farm. The databases are separated based on the services on the server. Generally Search, Content/Config and BI/Service Application Databases are separated
Services on server
- SharePoint Capacity Planning
- Small farm deployment
- A small farm deployment consists of a single database server or cluster and one or two SharePoint Server 2013–based computers. The major architecture characteristics include limited redundancy and failover, and a minimal set of SharePoint Server 2013 capabilities enabled.
- A small farm is useful to serve only limited deployments, with a minimal set of service applications enabled, a relatively small user base, a relatively low usage load (a few requests per minute up to very few requests per second), and a relatively small volume of data (10 or more gigabytes).
- Medium farm deployment
- This architecture introduces the breakdown of the topology into three tiers: dedicated Web servers, dedicated application servers, and one or more database servers or clusters. Separating the front end server tier from the application server tier allows greater flexibility in service isolation and helps balancing the load across the system.
- This is the most common architecture, and includes a wide spectrum of service topologies and farm sizes. A medium farm deployment is useful to serve environments that have the following:
- Several service applications distributed across multiple servers. A typical set of features might include the Office Web Apps Service, User Profile Service, Managed Metadata Service, and Excel Calculation Service.
- A user base of tens of thousands of users and a load of 10 to 50 requests per second.
- A data store of one or two terabytes.
- SharePoint Development servers may be used as the single server for WFE, App or DB servers
- Developer should use their own Virtual Machines for SharePoint Development
- In case of implementation of Business Intelligence features in SharePoint, a separate SharePoint Application server should be used
- If On Base or any other application needs to be integrated with Enterprise Search, a separate SharePoint Application server should be used to separate Search from other service applications
- If possible, SharePoint servers should be created from the base template rather than installing SharePoint on brand new Windows 2012 Servers
- For unattended service accounts, secure store target application IDs should be used
- Predefined SharePoint Managed Accounts should be used for SharePoint Application pools or any other services
- Scaling out a farm with server groups: In SharePoint Server 2013, the number of services and corresponding databases is greater than in previous releases. The recommendation for scaling out a farm is to group services or databases that have similar performance characteristics onto dedicated servers and then scale out the servers as a group. For example, group all client-related services onto one or two servers and then add servers to this group as needed to satisfy user demand for these services. In some cases, we might need to create a dedicated server group for a single service, such as Excel Services or Search. This model groups service applications and related components (for example, databases) into several different logical groupings that can be used as a starting point. In large environments, the specific groups that evolve for a farm depend on the specific demands for each service.
Database Server Standards
- "Security Hardening" should be implemented in SharePoint Farm.
- Blocking the standard SQL Server ports: Custom port should be used for SQL server instead of using default port which is 1433
- Use Named instances "SHAREPOINT" of Database Server instead of Default instance
- SQL Server database instances should be configured to listen on a nonstandard port
through a Non-Standard port.
- Grant SVCSPAdmin or SVCSPAdminDEV or SVCSPAdminUA (depending on the environment) dbcreator and securityadmin SQL roles
- Grant SVCSPFarm or SVCSPFarmDEV or SVCSPFarmUA (depending on the environment) dbcreator and securityadmin SQL roles
- SQL Server client aliases should be used instead of Physical Server names: A SQL Server client alias "SHAREPOINTSQL" on all SharePoint Servers should be created and used to communicate with Database Server
- Set max degree of parallelism (MAXDOP) to 1 for instances of SQL Server that host SharePoint databases to make sure that a single SQL Server process serves each request.
Important: Setting the max degree of parallelism to any other number can cause a less optimal query plan to be used that will decrease SharePoint Server 2013 performance.
Ref: http://technet.microsoft.com/en-us/library/hh292622(v=office.15).aspx
Naming Standards
- We should follow the standard naming convention across all environments and environment specific naming should not be used
- The content databases could be named starting with SP_ (followed by name format and name) and there should not be any blank spaces inside/outside of the names (e.g. Central Admin content database could be SP_Content_CentralAdmin, Intranet content database could be SP_Content_Intranet and Applications content database could be SP_Content_Applications)
Role | Name Format | Example(s) |
Configuration Database | sp_config | sp_config |
Content Database | sp_content_<function> | sp_content_admin sp_content_portal sp_content_mysites |
Single Database Service Application | sp_service_<service application name> | sp_service_mms |
Multiple Database Service Application | sp_service_<service application name>_<database name> | sp_service_ups_profile |
- While creating Sites/List/Libraries/etc. the blank spaces should be avoided and description may have blank spaces after its being created. (e.g. Architecture, TruckTransportation, CanwestPropane etc.). In this way there won't be any "%20" in the URLs
Hardware Standards
To deploy Microsoft® SharePoint® Server at Company1, we must meet the following requirements:
Hardware: 64-bit
SharePoint Server 2013 and SharePoint Foundation 2013 are 64-bit applications and can only run on a 64-bit edition of Windows Server® 2012 or 2008/2008 R2 operating systems. We must have hardware that supports the use of a 64-bit operating system and 64-bit SQL Server.
Hardware — Web servers, application servers, and single server installations
The requirements in the following table apply both to installations on a single server with a built-in database and to servers running SharePoint Server 2013 in a multiple server farm installation.
Component | Minimum requirement |
Processor | 64-bit, 4 cores (For Standard SharePoint) 64-bit, 4 quad-cores (For PowerPivot Deployment) |
Memory | 16 GB (For Standard SharePoint) 24 GB (For Single Development Server running all available services) 64 GB (For PowerPivot Deployment) |
Hard disk | OS: 120 GB (C: Drive) Logs: 20 GB (D: Drive) We must have sufficient space for the base installation and sufficient space for diagnostics such as logging, debugging, creating memory dumps, and so on. For production use, we also need additional free disk space for day-to-day operations. Recommended free space needs be of 5 times of memory. But, maintain at least twice as much free space as we have memory for production environments. |
Hardware — Database servers
The requirements in the following table apply to the database servers in production environments with multiple servers in the farm. But, this recommendation has to be aligned with Company1's Database Server policy and standards.
Component | Minimum requirement |
Processor | 64-bit, 4 – 8 cores |
Memory | 16 GB for DB Server Memory |
Hard disk | System Drive(C:) – 40 GB Binaries (D:) – 40 GB Data (E:) – 100 GB (More for Production but based on Contents) Log (F:) – 40 GB Temp (T:) - As Required Logs: Company1 standard database server Hard disk space is dependent on the size of the SharePoint content. The sample calculation is being given below. |
Database Size:
The size of SharePoint content database depends on some factors. Based on requirements and capability the size of databases or servers has to be determined.
Database size: (D.V.S) + (10 KB . (L + (V.D)))
- D: number of documents
- V: number of non-current version
- S: Average size of document
- L: list items
Ex: (200,000 . 2.250) + ((10 KB . (600,000 + (200,000 .2))) = 110,000,000 KB or 105 GB
Service Accounts
SharePoint needs some pre-defined service accounts to install and configure SharePoint. SharePoint will elevate the following accounts as necessary during installation. So, for Non Production (Dev/Test) and Production separate service accounts should be created. Like:
For Production Environment "SVCSPAdmin" will be " SVCSPAdminPRD"
For UA Environment "SVCSPAdmin" will be " SVCSPAdminUA"
For DEV Environment "SVCSPAdmin" will be " SVCSPAdminDEV"
Account name | Role | Domain rights | Local SharePoint Server rights needed | SQL rights needed |
SVCSPAdmin | Used to install SharePoint binaries. | Domain User | Local administrator on all SharePoint boxes | dbcreator and securityadmin SQL roles |
SVCSPFarm | 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 |
SVCSPWebapp | App pool id for content web apps | Domain User | None | None |
SVCSPService | Service app pool id | Domain User | None | None, unless using Office Web Apps. Them must give access to content databases manually |
SVCSPSearch | Search process id | Domain User | None | None |
SVCSPContent | Account used to crawl content | Domain User | None | None |
SVCSPUserprofile | 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 |
SVCSPPowerPivot | PowerPivot Service Account | Domain User | None | None |
SVCSPPerformancePoint | PerformancePoint Service Account | Domain User | None | None |
SVCSPExcel | Excel Services Service Account | Domain User | None | None |
SVCSPVisio | Visio Service Account | Domain User | None | None |
SVCSPSuperuser | Cache account | Domain User | Web application Policy Full Control Web application super account setting | None |
SVCSPSuperreader | Cache account | Domain User | Web application Policy Full read Web application super reader account setting | None |
DNS Names
It is recommended to use the DNS names (http://spsandbox) instead of physical server address and port number (http://MYSERVER1:80) for each web application in a SharePoint Environment. The DNS names are being used to assign the host headers for the web applications.
Environment | Web Application | DNS Name |
Company1 Team Sites | ||
Sandbox | Intranet Team Sites | |
Development | Intranet Team Sites | |
UA | Intranet Team Sites | |
Production Support | Intranet Team Sites | |
Production | Intranet Team Sites | |
Company1 Applications | ||
Sandbox | Application Site | |
Development | Application Site | |
UA | Application Site | |
Production Support | Application Site | |
Production | Application Site | |
Company1 Intranet (Inmotion) | ||
Sandbox | Intranet Publishing Site | |
Development | Intranet Publishing Site | |
UA | Intranet Publishing Site | |
Production Support | Intranet Publishing Site | |
Production | Intranet Publishing Site | |
Company1 Public Facing Corporate Site | ||
Sandbox | Internet Publishing Site | |
Development | Internet Publishing Site | |
UA | Internet Publishing Site | |
Production Support | Internet Publishing Site | |
Production | Internet Publishing Site | |
Company1 Public Facing Extranet Site | ||
Sandbox | Extranet Team Sites | |
Development | Extranet Team Sites | |
UA | Extranet Team Sites | |
Production Support | Extranet Team Sites | |
Production | Extranet Team Sites | |
Comments
Post a Comment