As far as I know or according to my experience you should be creating Site Collections for departments and let each department have there own content database as a best practice.
Web applications should be created on the basis of mode of authentication.
I would recommend you to go through these topology diagrams provided by Microsoft to understand the ...
As it turned out, this was not an easy task.
Clone Search Topology
At fisrt I tried clone the search topology, replace the failing Index Component, and activate the clone topology - like this following the technet guide Manage the index component in SharePoint Server 2013:
if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) ...
IMO, You need to try one more time on changing the Search Topology.
The following list provides an overview of the tasks involved to change from the default search topology, without any content in the SharePoint Server 2013 search index, to a new search topology.
Ensure that no crawls have been started and that the search index is empty.
Start a ...
While the scope of your question is really too broad and many answers can fit to suit as needed, I would share a starting point specific to determine the need of site collection vs web application.
SharePoint Factors : As thanby added , A web application is generally a high level abstraction in the "arrangement of your portal sites". Generally they are ...
I happen to have a great exposure working with the Content Deployment in an authoring and production topology:
Authoring and production farm
The two-farm topology is a standard Internet site topology, and it is typical of topologies that are used to publish an Internet site. It includes two server farms: one to host the authoring site collection along with ...
In general it is advisable to keep it as simple as possible. You'll only want to split your content across multiple web apps if security is a huge concern or if you have enough serious traffic that you'll want to load-balance. For performance, the best way to load balance it to start by splitting administrative tasks like timer jobs and search indexing onto ...
As a short answer: The server that hosts Central Administration in the farm is the Application Server.
Front-end web server role
The fundamental role of a front-end web server is to host web pages, web services, and the Web Parts that are required to process requests from users. The web server directs these requests to the application server, ...
The process is:
Clone the existing topology
Add the components to the new Search Server
Activate the topology
More or less, it'll look something like this:
$si = Get-SPEnterpriseSearchServiceInstance -Local
$clone = $sa.ActiveTopology.Clone()
New-SPEnterpriseSearchAdminComponent -SearchTopology $clone -SearchServiceInstance $si
The issue seemed to be down to the size of the Index Partition. We reduced the number of items in the index using crawl rules and were able to get it down to about 8 million items from 12 million.
We were able to then make changes to the search topology.
What was interesting was the SharePoint Search Service on the rogue Crawl server would take about 90 ...
Query Server == Application Server.
A "query server" is an application server with only the search service (in this case the query role) role enabled.
You could also have a "Access Server" if you would only enable the Access Services role on the server because you have large loads of Access documents being processed. The query server and the search index ...
•Query server. A query server hosts query components and index
Query components return search results. Each query component is part
of an index partition, which is associated with a specific property
database that contains metadata associated with a specific set of
crawled content. You can make an index partition redundant by adding
I would think that a 3 stage environment would make a lot of sense if you were developing an internet. The staging environment gives you complete control over the page authoring environment. As you indicated you have a separate set of permissions for the users involved with authoring. In addition, when the pages are approved in the staging environment, ...
I know it's an old thread but for others benefit I'm going to attempt to answer your 2nd part of the question (which does not seem to be addressed directly). There should not be any downtime for just adding a new server to the farm.
Its depends on the SharePoint version.
If you are using the SharePoint 2010 or older version then SharePoint Store copy of document every time a new version is created. I.e. A document of 10MB with 10 version will be 100MB in storage.
But if you are using the SharePoint 2013 or 2016 then you can take the advantage of Shredded storage, which mean every time ...
Did some googling and this will work, there's even a blog post describing your problem step by step:
Here's how I see it: his should work, because in the end it all comes down to service identities.
As long as all service accounts used to run services on each server in the farm are from the domain trusted (DOMAINB) by the DMZ domain it should work. Seeing ...
The advantages of multiple instances are limited in the scenario you've given.
You are correct in what you're implying - that you could simply have one farm, with no content deployment. Editors could see unpublished content, and other users see published.
Or, as the document you linked to says, you could have one instances and deploy to a different site ...
SharePoint can be configured a number of ways, though I have to admit that this is the first time I've seen Authoring before Testing. Typically, when a dedicated Authoring site is in the mix, it is there for one of 2 reasons: 1) it has different authentication requirements (i.e. Authoring is NTLM but the production site is Forms-Base/Anonymous) or 2) there ...
It solely depends on what your requirement is.
If you are looking for evaluating SharePoint 2010 on a single system for checking foundation features you can install using Standalone mode with SQL Express with no additional overheads. In a 8 GB RAM system it should work just fine.
Power User and Enterprise Features
Incase there is a need to ...
You can install SP2010 on DC but it is not recommended. If you don't have possibility to add more servers then you can go with the following architecture:
SharePoint Server 2010 and Applications on one server.
Domain controller and Microsoft SQL Server 2008 running on another
You can even deploy SharePoint Server 2010/SQL Server in a single server farm ...
This topology uses an enterprise services farm that delivers enterprise-wide services to other farms within the company. Typical services are the user profile service, managed metadata and of course search. The colored lines between the farms point to the consumed services in another farm.
The other farms consume services from the enterprise services farm ...
I had the exact same issue as you described where the index component was broken after an Index Reset.
I was ready to roll my sleeves up and work through your detailed steps (thank you by the way) when I resolved it by using the Pause/Resume option.
Why did I try Pause/Resume? Well after I did an IISRESET I found that the Content Sources were stuck on "...
I saw this question little late. I think you already done with it but i am sharing the my experience here.
to install the pre requisites and SharePoint Bits under a account which is local admin on the server( we used the install account), this account will do the future updates as well. So in your case SPfarm account.
When you run the PSconfig wizard it ...
I think you miss the train and now the only option is rebuild the farm on new domain.For rebuilding you have to two options.
Options 1 as you TFS DB server still have all the content DBs..
build a new farm on new domain
Create & configure all the web application & service applications
Now attach the old content DB to right web app.
Now you have to ...
Its depend how big the servers in term of Memory and CPU. As Query components required more resources then it is advisable never configure it on web front end.
Use the WFE for web applications only
Use App server for all applications.
Please check this topology diagram recommended by MSFT.
True! When you created a farm using minrole, your search severs will run the following (search) services:
Search Administration Web Service
Search Host Controller Service
Search Query and Site Settings Service
SharePoint Server Search
No other server will run any other search service, meaning that the entire search topology will run on those two search ...
For 800 users (more important, how many concurrent?), I would suggest the smaller of the two topologies for now using the shared MinRoles.
With the size of the index, I would suggest, in the future, looking at adding 2 or more additional Search servers (either App+Search, or stand alone Search).
Microsoft has a bunch of different designs for extranets : http://technet.microsoft.com/en-us/library/cc263513.aspx
I have a sharepoint extended application . The default port is used by our internal users and the extended ...
Try this through Powershell:
$hostA = Get-SPEnterpriseSearchServiceInstance -Identity "myserver1"
$ssa = Get-SPEnterpriseSearchServiceApplication
$topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa
New-SPEnterpriseSearchIndexComponent -SearchTopology $topology -SearchServiceInstance $hostA -IndexPartition 1
Here is more about managed Index ...