Considering virtualizing both network servers (with AD)

S

SFinch

We have a small client that has tight regulatory compliance requirements to
meet regarding disaster recovery. They currently run two (2) Windows Server
2003 boxes. Both are domain controllers. One also runs SQL Server and
Pervasive databases and the other hosts an SMTP mail server. All servers and
workstations are in the same physical building, so we need to assume that a
disaster would destroy all existing hardware.

We're considering virtualizing in order to maximize portability and
recoverability to dissimilar hardware in the event of a disaster. We would
use Windows Server 2008 Enterprise R2 with Hyper-V as the host.

I've read up on the tips about running all DCs as virtuals and am
considering the option to join the physical host to the domain hosted by the
virtuals, but NOT make the physical box a DC.

Is this a safe, stable, supported configuration? Also, does anyone have
experience with restoring a setup like this to dissimilar hardware?

Thanks very much,

Steve
 

My Computer

R

RCan

Hi SFinch,

I personally would test the your workloads before you go productive
especially the SQL and Exchange one. The general overall performance will
strongly rely to the available disk subsystem's delivered I/O performance.

In addition I would NOT add your host to the domain, when all DCs are
virtualized and running on the same host ! a.e. can generate long logon
times till all hyper-v services are started and domain controller services
is up and running.
Also try to migrate your customer as soon as possible to windows 2008 cause
2008 and higher are really optimized for running virtualized workloads on
top of an hypervisor.

The restore on a different hardware is generally one of the benefits of
virtualization. As everywhere else you should test an sucessful
backup/restore before you go productive ;-)

Regards
Ramazan

"SFinch" <[email protected]> wrote in message
news:[email protected]

> We have a small client that has tight regulatory compliance requirements
> to
> meet regarding disaster recovery. They currently run two (2) Windows
> Server
> 2003 boxes. Both are domain controllers. One also runs SQL Server and
> Pervasive databases and the other hosts an SMTP mail server. All servers
> and
> workstations are in the same physical building, so we need to assume that
> a
> disaster would destroy all existing hardware.
>
> We're considering virtualizing in order to maximize portability and
> recoverability to dissimilar hardware in the event of a disaster. We
> would
> use Windows Server 2008 Enterprise R2 with Hyper-V as the host.
>
> I've read up on the tips about running all DCs as virtuals and am
> considering the option to join the physical host to the domain hosted by
> the
> virtuals, but NOT make the physical box a DC.
>
> Is this a safe, stable, supported configuration? Also, does anyone have
> experience with restoring a setup like this to dissimilar hardware?
>
> Thanks very much,
>
> Steve
 

My Computer

J

Jonny

I like this guys blog about virtualising DCs

http://www.petri.co.il/domain-controller-virtualization-options.htm

I wonder what the groups feedback is to this? I've implemented his method
of having two virtual DCs

"RCan" <[email protected]> wrote in message
news:[email protected]

> Hi SFinch,
>
> I personally would test the your workloads before you go productive
> especially the SQL and Exchange one. The general overall performance will
> strongly rely to the available disk subsystem's delivered I/O
> performance.
>
> In addition I would NOT add your host to the domain, when all DCs are
> virtualized and running on the same host ! a.e. can generate long logon
> times till all hyper-v services are started and domain controller services
> is up and running.
> Also try to migrate your customer as soon as possible to windows 2008
> cause 2008 and higher are really optimized for running virtualized
> workloads on top of an hypervisor.
>
> The restore on a different hardware is generally one of the benefits of
> virtualization. As everywhere else you should test an sucessful
> backup/restore before you go productive ;-)
>
> Regards
> Ramazan
>
> "SFinch" <[email protected]> wrote in message
> news:[email protected]

>> We have a small client that has tight regulatory compliance requirements
>> to
>> meet regarding disaster recovery. They currently run two (2) Windows
>> Server
>> 2003 boxes. Both are domain controllers. One also runs SQL Server and
>> Pervasive databases and the other hosts an SMTP mail server. All servers
>> and
>> workstations are in the same physical building, so we need to assume that
>> a
>> disaster would destroy all existing hardware.
>>
>> We're considering virtualizing in order to maximize portability and
>> recoverability to dissimilar hardware in the event of a disaster. We
>> would
>> use Windows Server 2008 Enterprise R2 with Hyper-V as the host.
>>
>> I've read up on the tips about running all DCs as virtuals and am
>> considering the option to join the physical host to the domain hosted by
>> the
>> virtuals, but NOT make the physical box a DC.
>>
>> Is this a safe, stable, supported configuration? Also, does anyone have
>> experience with restoring a setup like this to dissimilar hardware?
>>
>> Thanks very much,
>>
>> Steve
>
 

My Computer

Top