16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Estimating Current <strong>and</strong> Future Storage Needs<br />

Chapter 9: Capacity Planning 215<br />

Estimate the size of the required content by analyzing the quantity <strong>and</strong> size of existing<br />

documents in shared folders <strong>and</strong> other existing systems. To determine your current<br />

<strong>and</strong> future storage needs, try to identify current access frequencies <strong>and</strong> patterns.<br />

Once you have determined the total size of all documents you plan to store in<br />

your SharePoint Portal Server farm, including all team sites, you can start to plan<br />

disk space requirements. You must consider the number of versions for all documents<br />

you plan to store. Multiply the number of versions you expect by the total size<br />

of all documents to get the total storage size for documents.<br />

The SQL Server component will be the place the documents are actually<br />

stored. It needs disk space equal to twice the total size of all documents, including<br />

versions, you want to store in all your portal sites. This free disk space is required on<br />

the drive where the SQL Server databases reside. Also, the storage requirement does<br />

not include any operating system or supporting system software. If you plan on storing<br />

large quantities of files, you should store the SQL Server databases that Share-<br />

Point Portal Server uses on a storage area network (SAN). You should refer to SQL<br />

Server documentation for information on what SAN products are compatible with<br />

SQL Server.<br />

Note SQL Server does not support storing database files on Network-<br />

Attached Storage (NAS), so the free storage requirement must be met on a<br />

local physical disk on the SQL Server or on a SAN.<br />

Once you have determined total document storage for SQL Server, you must<br />

determine the total size of documents being indexed. Take the total size of each<br />

content source—file shares, exchange public folders, <strong>and</strong> websites—that you want<br />

to index, <strong>and</strong> add that sum to the total size of all files stored in the server farm. This<br />

number is the total size of all documents to be crawled. Take this number <strong>and</strong> divide<br />

it by two. That is the total storage required on each indexing server in your farm.<br />

Then divide the number by two again. That is the total space required on each<br />

search server in your farm.<br />

In a single-server environment, all components run on the same system. This<br />

means you need all the storage space on a single system. A single-server environment<br />

needs free space equal to 2.75 times the total size of all documents stored if<br />

there are no external content sources. A small server farm separates the SQL Server<br />

storage component from the other components. In a small server farm, the SQL<br />

Server component needs twice the total size of documents to store in free space <strong>and</strong><br />

the server that runs the SharePoint Portal Server components needs to have .75 times

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!