Archived from groups: microsoft.public.win2000.advanced_server (
More info?)
Max,
As I mentioned before that I'm by no means an expert in this subject matter
of DHCP, but responded to your posting then I'll try to assist you to the
best of my ability. This method was suggested to another customer and works
around the behavior mentioned below by removing the checkpoint data, and
then allows you to re-create the scope with the desired data intact.
SYMPTOMS
===========
When you try to migrate DHCP scopes from a standalone Windows 2000
environment to a Windows 2000 MSCS Cluster using either DHCPEXIM or manually
by copying the service registry keys and the dhcp.mdb file all scope data is
lost. This also occurs when you try to export and import a DHCP
configuration that was initially built on a Windows Cluster.
CAUSE:
=======
In order to import and export a DHCP database is necessary to stop and start
the DHCP service. When the service is clustered it is now owned by the
cluster service, and can only be stopped using the Cluster Administrator
utility. When a service is stopped and started using the Cluster
Administrator tool, MSCS uses registry checkpoints to ensure that the
service restarts in the same condition as when it was taken offline. The
updated scope information is being erased by MSCS registry checkpoints.
WORKAROUND
===============
In order to import a Windows 2000 DHCP database onto a Cluster Server use
the following method:
1) Install Windows 2000 with the Cluster service
2) Install DHCP on both nodes
3) Start Cluster Administrator and select the cluster group you wish to
use for your DHCP
4) Add the following resources to the group:
a: Physical Disk (r:\ for instance)
b: An IP (192.168.1.1 for instance)
c: A Network Name (DHCPSRV1 for instance)
d: The DHCP Service - put the database on the root of the shared
physical disk (R:\DHCP\ for instance)
5) Bring all resources online and test moving them from one node to the
other
6) Open the DHCP snap-in from both nodes to verify that the service is up
and running
7) In Cluster Administrator, take the DHCP Service resource offline -
make sure to leave the other resources online
8) On the node that currently owns the group, run DHCPEXIM and import the
desired scopes
9) In Cluster Administrator, delete the DHCP Service resource
10) In the DHCP snap-in, restart the DHCP service; verify that the imported
scopes are still present.
11) In Cluster Administrator, re-add the DHCP Service resource and make
sure that the database is still pointed to the root of the shared physical
disk (R:\DHCP\ for instance)
12) Bring the "DHCP service" resource online, check to see if the scopes
are still present, then test moving them form one node to the other
NOTE: If Checkpoints need to be repaied, you can use the ClusterRecovery
tool to repair them. See the article reference link below:
307469 Restore registry check points stop working after you restore a server
http://support.microsoft.com/?id=307469
--
Hope this helps,
Mike Rosado
Windows 2000 MCSE + MCDBA
Microsoft Enterprise Platform Support
Windows NT/2000/2003 Cluster Technologies
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
<http://www.microsoft.com/info/cpyright.htm>
-----Original Message-----
"Max" <Max@discussions.microsoft.com> wrote in message
news:78DACC5F-A1EF-4377-9ADF-77091B21DA86@microsoft.com...
> Hello!
>
> I used the Dhcpexim.exe to export my dhcp scopes from Windows NT to
Windows
> 2000 cluster but the DHCP service on cluster stop. I migrated others
scopes
> to Windows 2000 (without cluster) and it was ok.
>
> Is there something to do on a cluster to support the migration with
> Dhcpexim.exe?
>
> Someone can help me?
> Thanks!
>
)
Facebook
Twitter
Instagram