S
serverguy
<<REPLY NOT CROSS-POSTED>>
The only way to answer this is to know what the server will be doing. What
is it's purpose in life? Is it going to run a single application that does
random interval file serving (SUS for example)? Then it could probably
handle thousands of clients. Is it going to run an enterprise database like
SQL and crunch millions of transactions daily? Then it is going to live a
short life. Please enlighten us on the purpose. Also, the network topology
is a significant factor in how many clients can reasonably connect to a
server at the same time, but you fail to mention anything about your
network.
As for the array, you were misinformed. You can always add drives to an
array if there are available slots and/or ports, but you need to know a
little about raid levels and how many drives you need to obtain the desired
performance/redundancy. You then create a new logical drive that appears to
the o/s as unallocated space which you can format as needed. If you are
talking about adding space to the system partition, then a full backup would
be suggested before you add the drive to the array, then you can do a full
restore after. Another option is extending dynamic volumes but that has
many dependencies (for example, you can't extend a volume in 2003 server
that was fomerly a 2000 server basic volume that was converted to a dynamic
volume, etc....)
BTW, having the o/s on it's own array is the best practice, but again it
really depends on what the server will be doing.
The only way to answer this is to know what the server will be doing. What
is it's purpose in life? Is it going to run a single application that does
random interval file serving (SUS for example)? Then it could probably
handle thousands of clients. Is it going to run an enterprise database like
SQL and crunch millions of transactions daily? Then it is going to live a
short life. Please enlighten us on the purpose. Also, the network topology
is a significant factor in how many clients can reasonably connect to a
server at the same time, but you fail to mention anything about your
network.
As for the array, you were misinformed. You can always add drives to an
array if there are available slots and/or ports, but you need to know a
little about raid levels and how many drives you need to obtain the desired
performance/redundancy. You then create a new logical drive that appears to
the o/s as unallocated space which you can format as needed. If you are
talking about adding space to the system partition, then a full backup would
be suggested before you add the drive to the array, then you can do a full
restore after. Another option is extending dynamic volumes but that has
many dependencies (for example, you can't extend a volume in 2003 server
that was fomerly a 2000 server basic volume that was converted to a dynamic
volume, etc....)
BTW, having the o/s on it's own array is the best practice, but again it
really depends on what the server will be doing.