Sharepoint 2013 Servers Architecture

Hi
Our current architecture of SharePoint 2013 Farm is
1. WFE server (ip - 10.10.10.10)
2. A server which is Application server and Database server (ip - 10.10.10.11)
3. Application server (Central Admin) (ip - 10.10.10.12)
Load on the site has increased tremendously (Users =5000)(concurrent users =1000 approx.), we would have to now implement a Load balancer to retain the performance of the application.
Now the important question is CAN THIS LOAD BALANCER BE CONFIGURED BETWEEN THE WFE(ip - 10.10.10.10) AND THE Application/Database Server(ip - 10.10.10.11).
Please suggest.
Regards
Paru

Regd your questions:
1) As all its said earlier, Microsoft SharePoint Foundation Web Application service should be configured and running on any server which you want to work as WFE. Other than that, you can place whatever services you like to place on WFE. Its totally
a matter of design/architecture. You need to analyse existing resource consumption on the servers and then making a decision based on data.
2) You can have SQL 2008 R2 SP1 for SP2013 as backend. It need to be minimum running on windows server 2008 R2 SP1.
You may want to go through minimum software and hardware requirements for SP2013 at:
https://technet.microsoft.com/en-us/library/cc262485.aspx
You may want to go through minimum software and hardware requirements for SQL 2008 R2 at:
https://msdn.microsoft.com/en-us/library/ms143506(v=sql.105).aspx
Thanks
Mohit

Similar Messages

Do Sharepoint 2013 servers require an internet connection?

Hi All,
Do Sharepoint 2013 servers require an internet connection? I ask as I believe the apps catalog needs to look at Microsoft.com for the store?
Thanks

If you're going to use the App Catalog, yes it does require an Internet connection. Otherwise, no it does not. If you do prevent access to the Internet, you'll want to make sure to follow this process: http://support.microsoft.com/kb/2625048
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint 2013 Hybrid Architecture

Hi,
I've a requirement that my client wants to migrate their existing system into SharePoint. The existing system is web based asp.net and it contains some documents for storage and also for collaboration. Now they want to use SharePoint OOTB support
and migrate the existing documents into SharePoint 2013. They're preferring to use SharePoint online and in some cases they want to use on-premises. Actually, they're having some confidential and non-confidential documents. They want to move non-confidential
documents into online and confidential to on-premise. Now, I'd like to know how to design the solution. Please answer my below clarifications.
1) Some users have access to Office 365 and some users have access to on-Premise. If the user hits the company url, how to redirect the user. Do we need to design the solution like custom code or need to configure at both environment?
2) If user has access to both environment, Do we need to show two url's? Based on user selection, system we need to redirect the site?
Please share your approaches...
Balaji -Please click mark as answer if my reply solves your problem.

I don't think "Hybrid" works the way you're thinking it does.
Hybrid just means that SOME webapps (URLs) live out in the cloud, and SOME webapps live on-prem... and the service apps that need to cross between them (such as getting O365 search results from an on-prem server) are performed using service app connections.
There is no magical "the same URL goes to one or the other depending on whether the user is on prem or not"
There is no magical "files categorized as [x] are kept on O365, and files categorized as [y] are kept on-prem"
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

How scale the services for 4 SharePoint 2013 servers?

Hi,
I have in my new farm 4 Sharepoint servers. We are more than 1K users but less than 20K users.
WFE1 just with IIS
WFE2 just with IIS
APP_Serv1 with CA and all the services except for Search Services
App_Serv2 with just Search Services.
Is this correct? Is this considered best practices?
Thanks.

Best Practices would normally suggest moving some services like Search Query, Managed Metadata, and User Profiles to the WFEs. But there isn't just a single design that works or is the best. Take a look at the following article. It suggests
which services to put on which servers.
http://technet.microsoft.com/en-US/library/jj219591(v=office.15).aspx
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Global Architectural design for SharePoint 2013??

Hi Friends,
i am trying to pursue SharePoint 2013 global Architectural design before we implement SharePoint 2013 farm. FYI, Our Current SharePoint 2010 farm is three tier farm (2 web servers + 2 App servers + cluster Sql server) and total users 1,000 and its
located in one data center. From this farm we are serving now SP site to five different countries in the world via WAN. But as our company growing rapidly, we want share point will provide robust performance. As our company globalized, how many data center
we will need? Can we have one centralized farm in USA and other regional SharePoint farms into different countries? According to my business scenario, what will be the best architectural design?
Any help will be appreciated!!

"It depends" would be the answer with the information given. It depends on how much content is accessed at any one location, if a WAN accelerator could alleviate any issues end users at the remote locations were seeing, and if the company can take on the
added complexity, extra licensing, and hardware cost that are associated with SharePoint farms.
It would also depend if you want to replicate content (e.g. Metalogix Replicator) or if each farm will have its own unique content targeted at the specific region.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Sharepoint 2013 Upgrade Job failed.

Hello everybody,
I would like some help with a litle problem that occured after I installed November CU on all of Sharepoint 2013 servers, 1 app, and 2 WFE. I'm unable to get Timer Job Service working on my app server, and that is a big problem. Everytime I restart Timer
Job Service I get this error - Upgrade Job Appserver :00:00 Failed 12/16/2014 1:33 PM.. And in Event viewer -
System
Provider
[ Name]
Microsoft-SharePoint Products-SharePoint Foundation
[ Guid]
{6FB7E0CD-52E7-47DD-997A-241563931FC2}
EventID
6398
Version
15
Level
1
Task
12
Opcode
0
Keywords
0x4000000000000000
TimeCreated
[ SystemTime]
2014-12-16T11:33:37.846840300Z
EventRecordID
41822872
Correlation
[ ActivityID]
{CD50D69C-AE16-00AA-3D5F-ECACB6C25BFE}
Execution
[ ProcessID]
11368
[ ThreadID]
3216
Channel
Application
Computer
AppServername
Security
[ UserID]
S-1-5-21-1708537768-1425521274-1417001333-40380
EventData
string0
Microsoft.SharePoint.Administration.SPUpgradeJobDefinition
string1
13096a33-a91b-4c73-ae6c-e0ba750c5d4e
string2
Object reference not set to an instance of an object.
And, also from Sharepoint Log file -
Updating SPPersistedObject SPUpgradeJobDefinition Name=job-upgrade. Version: -1 Ensure: False, HashCode: 16745860, Id: 13096a33-a91b-4c73-ae6c-e0ba750c5d4e, Stack: at Microsoft.SharePoint.Administration.SPJobDefinition.Update()
at Microsoft.SharePoint.Administration.SPTimerStore.CheckEnterUpgradeMode(SPFarm farm, Object& jobDefinitions, Int32& timerMode) at Microsoft.SharePoint.Administration.SPTimerStore.InitializeTimer(Int64& cacheVersion, Object&
jobDefinitions, Int32& timerMode, Guid& serverId, Boolean& isServerBusy) at Microsoft.SharePoint.Administration.SPNativeConfigurationProvider.InitializeTimer(Int64& cacheVersion, Object& jobDefinitions, Int32& timerMode,
Guid& serverId, Boolean& isServerBusy)
Updating SPPersistedObject SPUpgradeJobDefinition Name=job-upgrade. Version: 2925660 Ensure: False, HashCode: 16745860, Id: 13096a33-a91b-4c73-ae6c-e0ba750c5d4e, Stack: at Microsoft.SharePoint.Administration.SPJobDefinition.Update()
at Microsoft.SharePoint.Administration.SPTimerStore.CheckEnterUpgradeMode(SPFarm farm, Object& jobDefinitions, Int32& timerMode) at Microsoft.SharePoint.Administration.SPTimerStore.InitializeTimer(Int64& cacheVersion, Object&
jobDefinitions, Int32& timerMode, Guid& serverId, Boolean& isServerBusy) at Microsoft.SharePoint.Administration.SPNativeConfigurationProvider.InitializeTimer(Int64& cacheVersion, Object& jobDefinitions, Int32& timerMode,
Guid& serverId, Boolean& isServerBusy)
Created upgrade job definition id 13096a33-a91b-4c73-ae6c-e0ba750c5d4e, mode InPlace, entering timer upgrade mode
Queued timer job Upgrade Job, id {13096A33-A91B-4C73-AE6C-E0BA750C5D4E}
Updating SPPersistedObject SPUpgradeJobDefinition Name=job-upgrade. Version: 2925663 Ensure: False, HashCode: 6922919, Id: 13096a33-a91b-4c73-ae6c-e0ba750c5d4e, Stack: at Microsoft.SharePoint.Administration.SPJobDefinition.Update()
at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId) at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition.ExecuteAdminJob(Guid targetInstanceId) at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition
jd, Guid targetInstanceId, Boolean isTimerService, Int32& result) at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)
The Execute method of job definition Microsoft.SharePoint.Administration.SPUpgradeJobDefinition (ID 13096a33-a91b-4c73-ae6c-e0ba750c5d4e) threw an exception. More information is included below. Object reference not set to an instance of an object.
And after that it all fails and Timer Jobs ain't working on App server, on WFE servers eveyrthing is allright and working as it needs to be.
I searched a lot of forums and different, but none of offered solutions ain't working, and that is not good.
PS. On development server eveything worked fine, looked through log files and this job run without any errors - Dev server is one in all installation, though.
If there is somebody who can help me with this, I would appreciate your help.
TY!

TY for your response,
I used the script to update timer job config, but that isnt helping, and, also, this isnt a timer job that is already in timer job definitions. Its the one, that's created and after execution gets deleted, because its grayed out in timer job history page
and I cant access it. if you look closer at log files I have pasted, you will see that the timer job that is created gets deleted almost immediatily and isnt executed and after that all timer jobs on my App server aint working and this happens every time after
I restart Timer Service on App server, event ID is 6398, but timer job config cache isnt the problem.
And, as much as I cant tell from logs - Object reference not set to an instance of an object. - I recieve this error because there is no timer job with ID, that is shown in error, because of this:
Deleting the SPPersistedObject, SPUpgradeJobDefinition Name=job-upgrade.
Maybe this information cansomehow help:
The Execute method of job definition Microsoft.SharePoint.Administration.SPUpgradeJobDefinition (ID 910fbcdc-2691-490e-a9e9-563ae767612e) threw an exception. More information is included below. Object reference not set to an instance of an object.
After previous error:
Exception stack trace: at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId) at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition.ExecuteAdminJob(Guid targetInstanceId)
at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)
And after that Upgrade timer job gets deleted and thats it, App server aint working like it nedds to and no Timer job are executed.
I hope this can help to narrow this problem down to a specific component or help resolve this error.
Rihards

Install SharePoint 2013 database on SQL server 2012 SP1 cluster

Good Day all,
We are trying to install SharePoint 2013 database on a SQL server 2012 Enterprise with SP1 cluster (configured for mixed mode) but the connection is not working (times out). We can telent the SQL cluster network name on port 1433 and we made
a UDL connection file, test the connection via windows authentication and it is working, but if we use the sql authentication it is not working.
Also we have two SharePoint 2013 servers connected via NLB.
Any idea about this issue guys?

event if 3355 means 3 things:
The SQL Server might be offline.
The SharePoint Foundation database access account might not have the necessary permissions to communicate with the SQL Server.
A firewall that runs on either the local server or on SQL Server might be blocking network communications.
Big question, how you trying to connect SQL windows or sql authentication? is it throwing error on Config wizard or somewhere else?
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Installed SQL Reporting Services 2012 on SharePoint 2013 Server. SQL Reporting Service not available In the list of runnning services or new service applications

Hi I'm trying to setup SQL reporting services in a SharePoint 2013 farm consisting of:
4 WFE's
4 App Servers (NLB Central Admin x 4 servers)
4 App Severs for SSRS (Light limited SharePoint services running)
I've installed SSRS 2012 SP1 by following the guide (http://msdn.microsoft.com/en-us/library/gg492276.aspx) on one of the SSRS SharePoint 2013 servers and ensuring Reporting Services - SharePoint and Reporting Services Add-in for SharePoint Products is selected.
All completed without errors and I have even upgraded to SP2 for troubleshooting but no joy.
I've then gone into SharePoint Central Admin and I cannot see SQL Reporting Service available In the list of runnning services on the server I have just installed SSRS on and going to manage service applications I cannot see in the new dropdown menu SQL
Reporting Services.
I have ran the following commands in the SHarePoint management shell:
Install-SPRSService and Install-SPRSSeviceProxy
and
get-spserviceinstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance
The reply was that the service was already online on the server.
So in powershell all seems ok but it does not appear in central administration.
I have also moved Central Administration to the SSRS SharePoint server too.
Any other suggestions? Here is the same problem but in SP2010 (http://social.technet.microsoft.com/Forums/office/en-US/6a21cc05-1f9b-49ad-a9bb-44aa5b3ce312/action?threadDisplayName=after-installing-sql-reporting-services-service-for-sharepoint-2012-service-is-not-in-the-list-of)
In my lab environment of a 4 server SP2013 farm it worked immediately when i installed it on the app server (CA host) so I dont think it is my install strategy.
I guess my next attempt is to install SSRS on an app server with central administration hosted.
Thanks

I had the same issue on 2 different environments.
I had 2 application servers. One had Central Administration. I installed SSRS on the other one and it never appeared in the Service Applications in SharePoint.
When I also provisioned Central Administration on the other application server and went to the service applications using Central Admin on that server, the SSRS service application was there.
Since then I always install SSRS on the server which hosts Central Admin. No issues then.

SharePoint 2013 Server is uable to crawl sites in another domain which is trusted

Hello,
I have 2 SharePoint 2013 servers. The 2 servers are in different domains, domainA and domainB.
The domains are trusted. On one of the servers (Server A), I have set up enterprise search, where it is supposed to get search results from Server B in the other domain.
Local search results is working good, but Server A is unable to crawl sites on Server B.
I have a domain search account like domainA\SharePointSearch for SharePoint Server A and domainB\SharePointSearch for the SharePoint Server B.
This is used for the SharePoint search services. I have the website address for the sites that are on Server B in the list for SharePoint to crawl and index, but Server A is not finding the Server B and is unable to crawl the sites
on Server B.
Any suggestions on what I can do to get sites on Server B crawled and indexed from Server A?
Thanks,
Paul

Are you receiving errors in the crawl log? Does the crawl account in farm A have a
Full Read user policy on the web applications in farm B that you are crawling?
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

14 hive folder in SharePoint 2013 environment?

Hi, I have two separate standalone SharePoint 2013 setup one is development and one is production.
My problem is when I go to “C:\Program Files\Common Files\microsoft shared\Web Server Extensions\14” location in development server then I see below folders as per below screenshot:
But if I go to Production server then having only below folders:
Even if I go to “14\TEMPLATE\controltemplates” folder in Production then all the ASCX files are not there but in Development all default ASCX files are available.
Why this mismatch in Production and development?
How to match my Production and development?

Hi,
I would be concerned that you may be missing additional files as well, you should have the 7 top level Folders that you show in your first screen shot on all SharePoint 2013 Servers. You should repair the PRD installation.
Also, why would you use the Stand Alone installation for production. A better approach would be to download the SQL 2012 SP1 Express Edition with Tools and install SharePoint using the Complete installation. However, this is not the reason you are missing
the folders...
-Ivan

SharePoint 2013 Central Admin says port 80 for three web applications, but IIS says they have different ports

Hello,
I have three web applications on a SharePoint 2013 servers. In Central Administrators on the Application Management page where it lists all of the web applications, it shows Port 80 being used 2 3 sites. When I go to IIS, 2 of the 3 are using
different ports, 81 and 82. So, only one site IIS says is using port 80. Why is this? The host file has no entries in it. Where these web applications extended?
Thanks,
Paul
Paul

Hi Paul,
From the URL of the web application in Central Administration in the image, you have configured the Alternate Access Mapping for the web applications.
And the URL configured is by default using port 80 if you don’t
assign other ports for the web application, so the port is changed to 80 in Central Administration.
To be able to access the web application, you need to add binging for the web application in IIS(please make sure that you have added the host name in DNS).
For example, SharePoint – 32298, you need to create the binding for the web application in IIS as the image below:
Best regards.
Thanks
Victoria Xia
TechNet Community Support

SharePoint 2013 Sync two Sites

I have one farm with two SharePoint 2013 servers: server1 and server2,I have the same site on both servers, server1 and server2, I need to sync Power view reports between Server1 and Server2, can you help me how implement it?
Thanks
Farm
Server1 | Server2
| |
MySite MySite

PowerView reports are standard content, just like any other document. The file is stored in the SQL database and displayed via the browser. You just need a network load balancer for Server1 and 2 in order to route users as required.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint 2013 three-tier architecture

Hi all, I am going to install SharePoint 2013 in a three-tier farm environment.
I understand that the only difference between web server and app server is whether or not the "Microsoft SharePoint Foundation Web Application" service application is running or not. If yes = web server, if no = app server. App server is also where
CA is installed. Both web server and app server will have connection to DB. When web server serves web page requests from users, it will go to DB directly to get the page content.
However, the real three-tier architecture actually means that only app server should have access to DB. Web server will get the information it needs from the app server.
Is my understanding correct so far? Why is there a difference between three-tier architecture when it is applied in SharePoint context?

No, all SharePoint servers directly interface with databases for services that they host (with some exceptions). 3 tier just means you have a "WFE" which end users interact with, and it doesn't matter what services are on that "WFE",
another SharePoint server which may do the same or other things, but users don't directly interact with, and of course the SQL Server.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint 2013 Architecture Concepts Help

I'm mainly a SharePoint 2010 administrator. Recently I've taken on a role that requires many SharePoint hats including figuring out to architect our SharePoint 2013 environment. I'm the only one here that knows anything about SharePoint that
is dedicated to this project - and while I'd like to think I know a lot, I'm not an architect. I've been researching and researching, and I have a few questions:
- SAN? (or DAS or NAS) Is it necessary? How does this relate to the storing of databases in SQL?
- We are going to have about 25,000 users total, 7,000 concurrent, moderate use of search, and 11 department site collections (needs to be 3 content databases to segregate data for 2 departments). Should I follow diagrams for a medium or large farm?
- I'm looking at the diagrams for a virtualized environment and they have more WFEs than the non-virtualized, why is this? Is there a reason why they have two servers on one host?
- It says 500 GB for index storage, is this per database or total? I'm used to auto-generating content databases as you configure, I've never created the database first then assigned it to the service. Do all the search functions go into this
single 500GB databse?
Thank you so much for your help in advance! Please let me know if you'd like to know what I have for architecture so far...

Depending on your needs for High Availability, some approaches require that the SQL Servers are connected to the same SAN/NAS via Fiber Channels. The idea is that your database files live on the SAN/NAS and can be served by more than one SQL Server. Therefore,
if one SQL Server goes down for any reason, the other can step in. More information on SQL Server 2012 High Availability:
http://technet.microsoft.com/en-us/library/ms190202.aspx
There are a lot of factors that play into deciding the topology that would best fit your use-case. Things to take into consideration include types of activities (publishing/reading or highly collaborative), response time requirements, availability requirements,
patterns of usage (spikes and distribution). The good news is that you can convert a Medium topology into a Large topology with additional hardware when needed.
They have two servers on a single host for redundancy in the case that 1 of the VMs goes down. With virtualization there are little arguments against taking advantage of this with very minimal trade-off in performance.
The Search index lives on the file system and the size will highly depend on what type of content you are crawling. (Example, a Word file has a lot more data to index than a JPEG image with only the metadata). The 500GB starting point is for the farm.
Dimitri Ayrapetov (MCSE: SharePoint)

In a Sharepoint 2013 Server farm how far away can the backup of failover cluster servers be located away from the primary servers

Hello Community
    When you setup a Sharepoint 2013 Server farm
if you want to provide failover clustering, can
the servers that the Sharepoint 2013 Server farm
failover to be located off-site in a different
location (i.e. how far away can the servers the
the primary server in the Sharepoint 2013 Server
farm be away from the failover cluster of backup
Sharepoint 2013 Server farm servers in distance?
    Thank you
    Shabeaut

Hiya,
this article describes in detail the different aspects of creating a highly available SharePoint 2013 server farm.
Create a high availability architecture and strategy for SharePoint 2013
http://technet.microsoft.com/en-us/library/cc748824%28v=office.15%29.aspx

Sharepoint 2013 Servers Architecture

Similar Messages

Maybe you are looking for