PS 2010 capacity planning
-
19/جمادى الأولى/1433 06:06 م
We are reviewing our existing PS 2010 setup. I was looking at capacity planning document @ http://technet.microsoft.com/en-us/library/ff686784.aspx
The document suggests 100 GB min req for Hard Disk on DB server. Now what does Hard Disk refer to? C drive or the drive where SQL data goes?
- تم التحرير بواسطة pwa guy 19/جمادى الأولى/1433 07:09 م corrected typo
جميع الردود
-
19/جمادى الأولى/1433 07:13 مالمشرف that would be the driver where SQL is putting the data.
Brian Kennemer - Project MVP
DeltaBahn Senior Architect
endlessly obsessing about Project Server…so that you don’t have to.
Blog | Twitter | LinkedIn- تم وضع علامة كإجابة بواسطة pwa guy 19/جمادى الأولى/1433 07:24 م
-
19/جمادى الأولى/1433 07:24 مThanks! Does hard disk for Web server refer to C drive?
-
19/جمادى الأولى/1433 07:26 مالمشرفThat depends on where you installed the components on the Web Server. That might be C or it might be another drive. Some IT shops want only the OS on C and they put everything else on a different drive.
Brian Kennemer - Project MVP
DeltaBahn Senior Architect
endlessly obsessing about Project Server…so that you don’t have to.
Blog | Twitter | LinkedIn -
19/جمادى الأولى/1433 07:29 مgotcha! One more thing. Does the 80GB for data drive of DB stand true even if the backups, log files are put into separate drives?
-
19/جمادى الأولى/1433 07:35 مالمشرفWe are getting outside my area here but in general you might be able to start with less and then monitor closely and make adjustments. For me it always feels easier to start with a big drive and NOT use it all then to start with a small one and then have to go through the trouble of moving things to a bigger one later. But that is just me. I dont spend my days on the 'back end' so those kinds of moves are a hassle for me to deal with.
Brian Kennemer - Project MVP
DeltaBahn Senior Architect
endlessly obsessing about Project Server…so that you don’t have to.
Blog | Twitter | LinkedIn -
20/جمادى الأولى/1433 12:39 م
Capacity planning is always a fun one to get right as it will vary for each organisation. The main factors which impact disk size is typically around project sites. If you are storing large volumes of information/documentation in project sites then this will inflate the content databases rather quickly. I had one client for example upload over 7500 documents to there site over a series of days. Do this with several project sites, turn on version control and you will soon find the content databases clocking up Gigabytes of data fairly quickly. There are ways to limit and monitor this sort of usage but I find generally speaking the capacity planning doc is a good starting point. Today with virtualisation technologies, typically a decent sized organisation will allow the virtual enviornment to run on a SAN so disk space can be easily monitored and added to the virtual server. Lots to think about though and lots of ways to help mitigate over inflation. With the right amount of questions though you can give a reasonable prediction on what hardware and infrastructure will be required.
In regards to C:\ drive, I believe it is good practice to keep the C:\ drive for base software and operating system information. Things like database files (.mdf) log files are best placed on seperate disk partitions to avoid crashing the server in the event of the database inflating and running out of space. At a guess 20 to 40 GB on C:\ may be fine and throw the majority of the remaining space on the other partion/s.
Same goes for the Web Server and Backend Server. Extra partitions are often created to store log files.
Regards,
Piet Remen
http://pietremen.blogspot.com.au -
21/جمادى الأولى/1433 07:59 مالمشرفI agree with the above, except make C:\ 100GB - if the server is going to last 3-5 years, you are going to upgrade Windows and SharePoint with SP1/2/3 and goodness knows what else. Better to have lots of spare disk on this partition to play with - as Brian says, it really is difficult to expand this later on.
