I have done the 'homework' and understand that 80GB is a reasonable starting
point for the C: drive for SBS 2008.

If the C; drive also holds a VM structure and child SBS2008 and the SQL
element is 80Gb still sufficient (for now).

I do recognise that historically the program files have grown and goodness
only knows what size will be necessary if 5 year's time, but that is a risk
we are all taking, I guess!

IanB

IanB <IanB@newsgroup> wrote:

> I have done the 'homework' and understand that 80GB is a reasonable
> starting point for the C: drive for SBS 2008.
>
> If the C; drive also holds a VM structure and child SBS2008 and the
> SQL element is 80Gb still sufficient (for now).

Nope, I wouldn't say so! And I'm presuming you mean you're going to be
using VMWare to host SBS, SQL, etc - not that SBS2008 itself will be running
VMWare and hosting VMs.

>
> I do recognise that historically the program files have grown and
> goodness only knows what size will be necessary if 5 year's time, but
> that is a risk we are all taking, I guess!

Hence you should overestimate.

>
> IanB

Come off the fence LW; suggest a number!

IanB

"Lanwench [MVP - Exchange]" wrote:

> IanB <IanB@newsgroup> wrote:

> > I have done the 'homework' and understand that 80GB is a reasonable
> > starting point for the C: drive for SBS 2008.
> >
> > If the C; drive also holds a VM structure and child SBS2008 and the
> > SQL element is 80Gb still sufficient (for now).

>
> Nope, I wouldn't say so! And I'm presuming you mean you're going to be
> using VMWare to host SBS, SQL, etc - not that SBS2008 itself will be running
> VMWare and hosting VMs.

> >
> > I do recognise that historically the program files have grown and
> > goodness only knows what size will be necessary if 5 year's time, but
> > that is a risk we are all taking, I guess!

>
> Hence you should overestimate.

> >
> > IanB

>
>
>
>

FWIW, I chose to install on a fixed size VHD of 120 GB for my SBS 2k8 C:
drive. With most things moved off of C: using the wizards, I expect that to
be sufficient for a while.

--
Charlie.
http:/msmvps.com/blogs/xperts64


"IanB" <IanB@newsgroup> wrote in message
news:F443A761-6D09-4DCD-A3F1-DBA86CC06FC9@newsgroup

>
> Come off the fence LW; suggest a number!
>
> IanB
>
> "Lanwench [MVP - Exchange]" wrote:
>

>> IanB <IanB@newsgroup> wrote:

>> > I have done the 'homework' and understand that 80GB is a reasonable
>> > starting point for the C: drive for SBS 2008.
>> >
>> > If the C; drive also holds a VM structure and child SBS2008 and the
>> > SQL element is 80Gb still sufficient (for now).

>>
>> Nope, I wouldn't say so! And I'm presuming you mean you're going to be
>> using VMWare to host SBS, SQL, etc - not that SBS2008 itself will be
>> running
>> VMWare and hosting VMs.

>> >
>> > I do recognise that historically the program files have grown and
>> > goodness only knows what size will be necessary if 5 year's time, but
>> > that is a risk we are all taking, I guess!

>>
>> Hence you should overestimate.

>> >
>> > IanB

>>
>>
>>
>>

IanB <IanB@newsgroup> wrote:

> Come off the fence LW; suggest a number!
>
> IanB

LOL. I'm not trying to be evasive. I just think I'd want a lot more -
depends on whether you're using ESX, and whether your SQL box will require a
lot of space. I would agree with Charlie's 120GB but that's just a guess on
my part./

>
> "Lanwench [MVP - Exchange]" wrote:
>

>> IanB <IanB@newsgroup> wrote:

>>> I have done the 'homework' and understand that 80GB is a reasonable
>>> starting point for the C: drive for SBS 2008.
>>>
>>> If the C; drive also holds a VM structure and child SBS2008 and the
>>> SQL element is 80Gb still sufficient (for now).

>>
>> Nope, I wouldn't say so! And I'm presuming you mean you're going to
>> be using VMWare to host SBS, SQL, etc - not that SBS2008 itself will
>> be running VMWare and hosting VMs.

>>>
>>> I do recognise that historically the program files have grown and
>>> goodness only knows what size will be necessary if 5 year's time,
>>> but that is a risk we are all taking, I guess!

>>
>> Hence you should overestimate.

>>>
>>> IanB