Storage (SAN configuration) Recommendation for MOSS 2007 Farm
Scenario: We have plan to install MOSS 2007 farm. Initially, we will install MOSS 2007, webserver, search & indexing on one box and SQL 2005 on another box. Afterwards, according to need we will add another server for search and indexing. We also have fiber channel card on our boxes.
We have a SAN solution (Pillar Data Systems) also.
Requirement: I need a suggestion about storage for MOSS 2007 and SQL 2005, i.e. Do we need to install MOSS 2007 on local hdd? If on local then which files should be on SAN? Which files of SQl 2005 should be SAN? Which files need what type of RAID configuration?
Please help me in this regard.
We have a SAN solution (Pillar Data Systems) also.
Requirement: I need a suggestion about storage for MOSS 2007 and SQL 2005, i.e. Do we need to install MOSS 2007 on local hdd? If on local then which files should be on SAN? Which files of SQl 2005 should be SAN? Which files need what type of RAID configuration?
Please help me in this regard.
ASKER
Thanks St3veMax.
In fact we are planning small farm consisting of webserver and DB server. If we are planning MOSS 2007 for 200 users so initially what will be the size of your suggested volumes for both MOSS indexes and DB server's 4 volumes?
In fact we are planning small farm consisting of webserver and DB server. If we are planning MOSS 2007 for 200 users so initially what will be the size of your suggested volumes for both MOSS indexes and DB server's 4 volumes?
Size of volumes is difficult as it depends on your current data volume and projected growth. Ideally you need to ensure your SAN has enough raw capacity to last 3yrs (assuming 3yr financial write-off).
You need to consider what you MOSS implementaion is going to be used for....Document Storage, Workflow sites, Intranet, etc.
On our MSF; we have a 2TB LUN for Data; 600GB for Logs, 100GB for TempDB, 500MB for Quorum (which is way over what it really needs). Our farm is split over 20 x content databases; with a 60GB Month-On-Month growth.
Other considerations are how mission critical is your setup? i.e. do you really need a SQL Cluster? MOSS 2007 will work with Database Mirroring; but it's a manual failover from a SharePoint perspective.
I would also reccomend creating a DNS CName for your SQL Connection; i.e. SQLMOSS.YourDomain.net which points to your DB Server; thus meaning when you need to move the DB; you just move it, move the logins and repoint the DNS - something I found out the hard way...
HTH
You need to consider what you MOSS implementaion is going to be used for....Document Storage, Workflow sites, Intranet, etc.
On our MSF; we have a 2TB LUN for Data; 600GB for Logs, 100GB for TempDB, 500MB for Quorum (which is way over what it really needs). Our farm is split over 20 x content databases; with a 60GB Month-On-Month growth.
Other considerations are how mission critical is your setup? i.e. do you really need a SQL Cluster? MOSS 2007 will work with Database Mirroring; but it's a manual failover from a SharePoint perspective.
I would also reccomend creating a DNS CName for your SQL Connection; i.e. SQLMOSS.YourDomain.net which points to your DB Server; thus meaning when you need to move the DB; you just move it, move the logins and repoint the DNS - something I found out the hard way...
HTH
ASKER
We are not planning for SQL clustering. We have a plan for 200 users who will not interact with MOSS aggressively. We will host document storage, workflow and intranet as well. So what is the final recommendation for the following SAN attached volumes:
Webserver:
Indexes = ?
SQL Server:
TempDB = ?
Data Files = ?
Logs = ?
Webserver:
Indexes = ?
SQL Server:
TempDB = ?
Data Files = ?
Logs = ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I didn't get first part of the message (Webserver) I am cleared in SQL Server.
You mean if I install MOSS 2007 locally on Webserver then What is Data? You mean local HDD space? and Index Data should be on SAN attached volume?
You mean if I install MOSS 2007 locally on Webserver then What is Data? You mean local HDD space? and Index Data should be on SAN attached volume?
Your Index server will crawl all your content and then propogate the index file (flat file) upto your webserver; hence the need for a reasonable size SAN disk on both the Index and Web server.
ASKER
Currently I have only 72 GB (Raid 5) on my Local server. Isn't enough I think?
Do you have any existing content to migrate into MOSS?
If so, how big is it currently?
If so, how big is it currently?
ASKER
Remember our Index and Webserver is same.
ASKER
Yes we have but not much.
We have a "Medium Server Farm"; two web front ends; one index and two sql (Clustered); all connected to a SAN.
Web:
Install MOSS Locally and have a SAN Attached drive to house your indexes that are propogated up from the index server
Index:
Again - Install MOSS Locally and have a SAN Attached Drive to hold your indexes
SQL:
Install SQL Locally; Configure 4 x SAN Drives (Data, Log, TempDB, Quorum). Depending on your requirements; Use RAID 1+0 for Log, TempDB, Raid 5 for Data, Quorum.
HTH