ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual Server 2005

Recent Virtual Server 2005 posts

* hyper-v - teaming recommded at physical host ?
* SCVMM and perimeter host
* Hyper-V -sharing modem for sbs server - How do you connect a com port to a named pipe
* The security settings for the Virtual Server event log were change
* DVD ISO size limited to 4GB?
* iSCSI and Public/Private network problem when clustering with Hyper-V
* Understanding and Optimizing Virtual Networks in Hyper-V
* Hyper-V and Physical RAID
* backup hyper-v guests using dpm
* point me in the right direction
* VMServer benchmarks
* Backing up Hyper-V cluster with Data Protection Manager 2007
* Hyper-v events
* Windows Datacenter 2008
* hyper-v. question
* Any way to manage Hyper-V from other OSes?
* VS2005R2 on W2K3 Web edition ?
* Hyper-V memory allocation error
* Virtual Machine Manager and ISO images
* Hyper-V Server 2008 Backup

Add Solution

Hyper-V clustering, Quick Migration and virtual domain controllers

Source: microsoft.public.virtualserver
Sent: 03/05/2009
From: Kimpsu
Message:

Hi!

I have understood that running active directory domain controllers is
supported by MS when run with their own virtualization solutions. What I
would like to know is how about when having multiple domain controllers and
using Hyper-V quick migration? It saves the state of the VM, moves it to
another host, and then resumes it.

Does this result in data synchronization issues between domain controllers?

Are there any MS documents or articles discussing this scenario? Best match
I could find was about Virtual Server 2005, but I am particularly interested
in the quick migration part of Hyper-V.

Thank you.

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Hyper-V clustering, Quick Migration and virtual domain control

Sent: 03/05/2009
From: Kimpsu
Message:

But since it is basically paused for that 10 seconds or so, it's clock etc
don't run for that time. How does it address this issue, or does it sync the
clock after resuming it on the other machine?

Since syncing the clock with the host is not recommended for domain
controllers anyway, the possible difference in the clock between the DC and
possibly the two Hyper-V hosts the machine is migrated from and to should not
affect the DC, but the DC (and often DNS, perhaps DHCP and WINS too) does
lose 10 seconds. And I was wondering if it would perhaps sync data with other
DCs wrong after this migration.

"Danny Sanders" wrote:

Show quoted text

> > Hi!
> >
> > I have understood that running active directory domain controllers is
> > supported by MS when run with their own virtualization solutions. What I
> > would like to know is how about when having multiple domain controllers
> > and
> > using Hyper-V quick migration? It saves the state of the VM, moves it to
> > another host, and then resumes it.
> >
> > Does this result in data synchronization issues between domain
> > controllers?
>
>
> The domain controllers are designed to be able to work and recover from a DC
> being out for a period of time without affecting replication. This is not
> any different from rebooting the DC or turning it off over a weekend because
> the building is having power issues and turning the DC on again on Monday
> morning.
>
>
> hth
> DDS
> "Kimpsu" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hi!
> >
> > I have understood that running active directory domain controllers is
> > supported by MS when run with their own virtualization solutions. What I
> > would like to know is how about when having multiple domain controllers
> > and
> > using Hyper-V quick migration? It saves the state of the VM, moves it to
> > another host, and then resumes it.
> >
> > Does this result in data synchronization issues between domain
> > controllers?
> >
> > Are there any MS documents or articles discussing this scenario? Best
> > match
> > I could find was about Virtual Server 2005, but I am particularly
> > interested
> > in the quick migration part of Hyper-V.
> >
> > Thank you.
>

Re: Hyper-V clustering, Quick Migration and virtual domain controllers

Sent: 03/05/2009
From: "Danny Sanders" <(email address - cut out)>
Message:

> Hi!

The domain controllers are designed to be able to work and recover from a DC
being out for a period of time without affecting replication. This is not
any different from rebooting the DC or turning it off over a weekend because
the building is having power issues and turning the DC on again on Monday
morning.

hth
DDS
"Kimpsu" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

>
> I have understood that running active directory domain controllers is
> supported by MS when run with their own virtualization solutions. What I
> would like to know is how about when having multiple domain controllers
> and
> using Hyper-V quick migration? It saves the state of the VM, moves it to
> another host, and then resumes it.
>
> Does this result in data synchronization issues between domain
> controllers?
> Hi!
>
> I have understood that running active directory domain controllers is
> supported by MS when run with their own virtualization solutions. What I
> would like to know is how about when having multiple domain controllers
> and
> using Hyper-V quick migration? It saves the state of the VM, moves it to
> another host, and then resumes it.
>
> Does this result in data synchronization issues between domain
> controllers?
>
> Are there any MS documents or articles discussing this scenario? Best
> match
> I could find was about Virtual Server 2005, but I am particularly
> interested
> in the quick migration part of Hyper-V.
>
> Thank you.

Re: Hyper-V clustering, Quick Migration and virtual domain control

Sent: 03/05/2009
From: "Danny Sanders" <(email address - cut out)>
Message:

I would have the PDC emulator in the root domain of the forest a phsycal
server. Other DCs will get their time from it at startup.

I would have at least 1 DC in each domain in your forest as a physical
server housing DNS. This way if you ever had to shut down your virtual
enviorment, having a physical DNS server that you can start up before your
virtual servers would significantly speed up the process, especially if
Exchange is involved, there is no reason that these DNS DCs in each domain
can't be the PDC emulator also.

hth
DDS

"Kimpsu" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> But since it is basically paused for that 10 seconds or so, it's clock etc
> don't run for that time. How does it address this issue, or does it sync
> the
> clock after resuming it on the other machine?
>
> Since syncing the clock with the host is not recommended for domain
> controllers anyway, the possible difference in the clock between the DC
> and
> possibly the two Hyper-V hosts the machine is migrated from and to should
> not
> affect the DC, but the DC (and often DNS, perhaps DHCP and WINS too) does
> lose 10 seconds. And I was wondering if it would perhaps sync data with
> other
> DCs wrong after this migration.
>
>
> "Danny Sanders" wrote:
>
>> > Hi!
>> >
>> > I have understood that running active directory domain controllers is
>> > supported by MS when run with their own virtualization solutions. What
>> > I
>> > would like to know is how about when having multiple domain controllers
>> > and
>> > using Hyper-V quick migration? It saves the state of the VM, moves it
>> > to
>> > another host, and then resumes it.
>> >
>> > Does this result in data synchronization issues between domain
>> > controllers?
>>
>>
>> The domain controllers are designed to be able to work and recover from a
>> DC
>> being out for a period of time without affecting replication. This is not
>> any different from rebooting the DC or turning it off over a weekend
>> because
>> the building is having power issues and turning the DC on again on Monday
>> morning.
>>
>>
>> hth
>> DDS
>> "Kimpsu" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Hi!
>> >
>> > I have understood that running active directory domain controllers is
>> > supported by MS when run with their own virtualization solutions. What
>> > I
>> > would like to know is how about when having multiple domain controllers
>> > and
>> > using Hyper-V quick migration? It saves the state of the VM, moves it
>> > to
>> > another host, and then resumes it.
>> >
>> > Does this result in data synchronization issues between domain
>> > controllers?
>> >
>> > Are there any MS documents or articles discussing this scenario? Best
>> > match
>> > I could find was about Virtual Server 2005, but I am particularly
>> > interested
>> > in the quick migration part of Hyper-V.
>> >
>> > Thank you.
>>

Re: Hyper-V clustering, Quick Migration and virtual domain controllers

Sent: 03/05/2009
From: "Blake" <(email address - cut out)>
Message:

http://searchwindowsserver.techtarget.com/tip/0,289483,sid68_gci1227204,00.html

Also - snapshots are a bad idea with virtual DCs

Blake

"Kimpsu" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Hi!
>
> I have understood that running active directory domain controllers is
> supported by MS when run with their own virtualization solutions. What I
> would like to know is how about when having multiple domain controllers
> and
> using Hyper-V quick migration? It saves the state of the VM, moves it to
> another host, and then resumes it.
>
> Does this result in data synchronization issues between domain
> controllers?
>
> Are there any MS documents or articles discussing this scenario? Best
> match
> I could find was about Virtual Server 2005, but I am particularly
> interested
> in the quick migration part of Hyper-V.
>
> Thank you.

RE: Hyper-V clustering, Quick Migration and virtual domain controllers

Sent: 03/05/2009
From: Kimpsu
Message:

How about in the event that all DCs are also DNS-servers, will that cause
synchronization issues?

"Kimpsu" wrote:

Show quoted text

> Hi!
>
> I have understood that running active directory domain controllers is
> supported by MS when run with their own virtualization solutions. What I
> would like to know is how about when having multiple domain controllers and
> using Hyper-V quick migration? It saves the state of the VM, moves it to
> another host, and then resumes it.
>
> Does this result in data synchronization issues between domain controllers?
>
> Are there any MS documents or articles discussing this scenario? Best match
> I could find was about Virtual Server 2005, but I am particularly interested
> in the quick migration part of Hyper-V.
>
> Thank you.

Re: Hyper-V clustering, Quick Migration and virtual domain controllers

Sent: 03/06/2009
From: "Danny Sanders" <(email address - cut out)>
Message:

> How about in the event that all DCs are also DNS-servers, will that cause

Absolutely not. One of ADs features is Active Directory Integrated DNS. When
activated the DNS information is replicated along with AD replication. It is
encryped and secure which is an improvement over the primary - secondary
model which replicates on it's own schedule and is less secure.

We have 40+ DCs serving as DNS servers in branch offices providing DNS for
each office.

Search the MS site for Active Directory Integrated DNS.

hth
DDS

"Kimpsu" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> synchronization issues?
> How about in the event that all DCs are also DNS-servers, will that cause
> synchronization issues?
>
> "Kimpsu" wrote:
>
>> Hi!
>>
>> I have understood that running active directory domain controllers is
>> supported by MS when run with their own virtualization solutions. What I
>> would like to know is how about when having multiple domain controllers
>> and
>> using Hyper-V quick migration? It saves the state of the VM, moves it to
>> another host, and then resumes it.
>>
>> Does this result in data synchronization issues between domain
>> controllers?
>>
>> Are there any MS documents or articles discussing this scenario? Best
>> match
>> I could find was about Virtual Server 2005, but I am particularly
>> interested
>> in the quick migration part of Hyper-V.
>>
>> Thank you.

RE: Hyper-V clustering, Quick Migration and virtual domain controllers

Sent: 03/06/2009
From: Kimpsu
Message:

Thank you all for your responses, I now have more information to work with.

Thank you.

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: