SharePoint disk capacity planning

Recently, a friend asked me how to plan the disk capacity of a Sharepoint system? If the required disk capacity cannot be determined during system planning in the early stage, it is likely that three months after the system is launched, an embarrassing situation occurs when the server disk is insufficient.

There are some related documents and white papers on the Microsoft technet website, such as capacity planning and sizing for Microsoft SharePoint products and technologies. However, if you are too lazy to read the white paper, you can give some brief parameters based on which you can quickly estimate the approximate disk capacity required by a Sharepoint system.

1. First, you need to estimateTotal storage capacity. If the total capacity of the entire system increases with the running of the system (this is often true ), then you can think about how long you want the entire system to be online without upgrading the disk capacity, and then estimate the total size of the content stored by the system within this period of time.

For example, every month, all users upload about 10 Gb of documents to the Sharepoint Server. If you want the SharePoint system to upgrade capacity in the next two years, the SharePoint system will store a total of GB of documents in the past two years.

Because SharePoint 2007 document management has "version control" and "recycle bin" features, do not forget to estimate the disk capacity that these two features will occupy when you estimate.

For example, in the entire system, if you estimate that about 5% of the files will be stored in the document library with version control enabled (Note: normally, not all files require version control. Many files are completed at one time or do not need to retain previous versions. You should exercise caution when using the version control function for the document library where the file is located ), in addition, the document library settings limit that only 10 major versions can be retained, and each major version can only keep up to 5 minor versions (NOTE: For document libraries with the document version enabled, you also need to set the secondary versions of the most major versions to avoid unnecessary increase in the number of versions, you need to add a capacity of 240 GB * 5% * 10*5 = GB.

In this way, the total capacity space calculated is: 240 GB + 600 GB = 840 GB.

2. Because SharePoint stores all website content in the SQL Server database, you must prepareThe total capacity of all content is multiplied by 1.2-1.5 times.To the SQL Server database.

For example, for the total size of the content calculated in step 1 is 840 GB, we need to prepare 840 GB * 1.5 = Tb of disk space for the SQL Server database.

3. Because index services in SharePoint will create index files for all content, you also need to prepare sufficient disk space for the index files. The disk space occupied by the index file.(Total Content capacity * (5-12%) * 3 timesThis formula is used for calculation.

For the ratio of 5-12%, you need to adjust it according to the content type stored in shareponit. For example, for the content (.doc、.docx0000.xls0000.xls0000.xlsx0000.pdf) of the document, the proportion of the space occupied by the index file must be higher than that of the image file. If your SharePoint system mainly stores the content of the document category, you need to increase the proportion appropriately, that is, closer to 12%.

For example, if only one part of the content is of the document type, we need to prepare 840 GB * 8% * 3 = GB space for the index file.

Note: If the indexing service runs on an independent Index Server in your Sharepoint Server Farm, you need to prepare such a large disk space on the Index Server.

4. If the query service is not running on the same server as the index service in the Sharepoint Server Farm, sharePoint automatically copies the index file from the Index Server to the server running the query service. Therefore, you also need to prepare sufficient disk space on all servers running the query service, left to the index file. The size of the disk space to be prepared. The calculation method is the same as that of the index file.

5. Finally, to avoid being too optimistic during estimation and you have enough budget, you may wish to calculate all the above resultsMultiply by 1.5-3 times(The multiples can be determined based on your budget ). For example, prepare 2 TB disk space for the SQL Server database and GB disk space for the index file.

Finally, we will introduce two SharePoint capacity planning tools. The first is Microsoft's SharePoint capacity planning tool, which relies on system center capacity planner 2007. Based on my experience, I personally think this tool is too fancy and has little practical value. :)

The second tool is HP ProLiant sizer for Microsoft Office Sharepoint Server 2007, a tool released by HP. I have no experience in using this tool.