Operating system (at least RAID 1 or better)
SMS (at least RAID 1 or better)
SQL Server (at least RAID 1; RAID 5 if the SMS database is on the same drive)
SQL Server transaction logs (at least RAID 5)
Software and image packages (at least RAID 5)

WRT line 1, Can an OS be installed on raid 5 etc? What is the better thing here (duplexing?)

Also what is 'at least raid 5'? As per my google searches, RAID 5 is very good and beats raid 10 at times.)

Also how many of your have such an SMS/SCCM or similar software installed on a this type of hardware (with 12 hdd in it!).

BTW the text is from the book MASTERING SCCM 2007, Sybex press, Chris Mosby,
Ron Crumbaker and Christopher W. Urban

MOderators please move the topic elsewhere if more suitable
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


The OS should be on a Mirror (0+1), it's a waste of disk to stripe it (Raid 5) and will slow performance.
Raid 5 is enough for the other stuff, but SQL logs and data should be on separate spindles due to the way data writes to the disks.

The boxes I usually configure are SMS\SCCm only writing to a Production SQL on a separate box\VM due to the configuration requirements for SQL to get max performance.

Doing a single server implementation means sacrificing performance in either SCCM\SMS or SQL (although it's less noticible in smaller environments).
Answered 08/09/2009 by: DeployTech
Orange Senior Belt

Please log in to comment
That's a tiny bit backwards.

Raid 0 = Striped (High performance especially in database access time, low reliability, does not reduce available storage, do not use if you care at all about the data on this volume)
Raid 1 = Mirrored (No performance boost, high reliability, reduces total available storage by 50%)
Raid 0+1 or 1+0 = Both! Requires four disks minimum, but is both fast and reliable

Raid 5 = Striped with parity, this one is a little more complicated, but it basically is very good at sequential reads/writes (IE, large single files) and is still redundant and therefore reliable, and reduces available storage by the value of one disk. Raid 5 is typically best for file servers.

If the server you're talking about has 12 disks, and you want to put your SQL backend, SMS database, SQL transaction logs, and a distribution point on the same box, this is how I would configure it off the top of my head:

Operating system: Two disks @ Raid 1
SQL database: Four disks @ Raid 1+0
SQL transaction logs+ Distribution point: 6 disks @ Raid 5

The SQL transaction logs are kind of a throwaway, they could be placed on either the OS volume or the DP volume, as if you're running your entire SMS site from a single physical, I would imagine that you won't begin to run into scaling issues with log sizes. If your site is larger than I'm imagining it (5k+ clients) then I would recommend instead using a 4 disk Raid 5 for the distribution point, and having a dedicated 2 disk Raid 1 for the transaction logs. The key is to keep them off of the SQL database volume, you want your access time to be as fast and responsive as possible for a SQL database, as the number of writes/reads is much more important than the throughput for that application.
Answered 08/11/2009 by: Jsaylor
Second Degree Blue Belt

Please log in to comment