SharePoint capacity planning
-
I think that the best resource that I know for this is likely @PSX_Defector
-
I know that starting questions are going to be things like "how many users" and "how will SP be used?"
-
And, of course, how much storage do you plan to use on it?
-
This is redoing a currently working SP server which is not scaled properly to new hosting with new site changes.
I have some numbers for now
*Number of concurrent users
Average 3,540 unique visitors a day and 10,6204 visitors in a Month-
Content DB sizes(Current Size)- Added sample names of the content DBs
ContentDB1 : 1.76 GB
ContentDB2: 475 MB
ContentDB3: 1 GB
ContentDB4: 107 MB
ContentDB5: 291 MB
SP_UAT_VMDB: 341 MB -
Projected content growth
Total Database size taken from backup statistics
Jan 2014 : 19.34 GB
June 2014: 23.22 GB
Dec 2013: 24.37 GB
Jan 2015: 27.73 GB
March 2015: 29.36 GB
June 2015: 26.50 GB
Sept 215: 32.35 GB
Current Size: 34.20 GB
SP topology, the proposed solution is Streamlined topology (http://www.microsoft.com/en-us/download/details.aspx?id=37000)and i guess it could be:
-
-
With the numbers you are quoting on the backups, with the sizes of the databases, looks as though don't go through that much in changes. ~10GB of churn in a year is nothing for Sharepoint. I'm thinking you have a few numbers off. Ive seen it in clusters of 20-30 front ends with two massive database servers behind them churn 30GB a day.
Easiest way to get some scalability is to make sure your database server has enough horsepower. With that much data, a two proc/32GB machine should be sufficient. Get it into a Windows Failover Cluster, and you should have plenty of room to run.
The front ends are much easier to deal with. Load balance them using whatever and have them join the farm. Adding a web node is trivial in Sharepoint.
The rest is just knowing what you plan on doing in Sharepoint. If you are just presenting a website and using it for a CMS, nothing to it. If you are using any kind of analyitics to parse data, then there is more towards queries and database IOPS. If you are using it as a data repo, then giant database to hold the blobs would be important.
What are you running now? What seems to be bottlenecked?
-
Is it a good practice to have a firewall first between internet and WFE servers and then between WFE and Application Servers? I am looking for a design diagram for such a setup
-
Something like this https://technet.microsoft.com/ee355682.fig4_L(en-us).gif
Nice, does ML now shows image from url?
-
Yes, has for a month or two
-
Going through all technet articles, this is going to be a long night!
-
@Ambarishrh said:
Is it a good practice to have a firewall first between internet and WFE servers and then between WFE and Application Servers? I am looking for a design diagram for such a setup
Depends on your needs. For a small setup, probably unnecessary. For compliance, potentially required.
We use firewalls against every single device on our network at the VM level. Communication in and out is always monitored and we have procedures on allowing traffic through. This provides compliance and proper lockdown between machines.
Don't think of the firewall as another device. If you have a single device, additional subnets with it inspecting the traffic is sufficient.
.gif){kind=link}
