Create backup w2k domain controller

Our primary w2k server is on it's last legs. We need to
create a backup and than fail the primary over. Any
pointers to getting this done quickly?

Bill

Either using your backup software or with the built in backup do a backup of
your domain controller including the System State which is very important as
the System State contains Active Directory data.

http://support.microsoft.com/default...b;en-us;240363

Install your new server. Point it to the existing domain controller as it's
preferred dns server, then dcpromo it to be an additional domain controller
in an existing domain. Active Directory will replicate to the new dc during
dcpromo. Go to AD Sites and Services and make the new dc a global catalog
server. Configure your new dc to point to itself as it's preferred dns
server with the old dc as second in the list after at least thirty minutes
have gone by. Check Event Viewer to make sure things look good with no dns
or replication problems and verify that the domain dns zone and the _srv
records show on the new dc in dns mmc. You can use the support tools
netdiag, dcdiag, replmon, and gpotool to verify health/configuration of the
domain and domain controllers. Change to other domain members to point to
the new dc as their preferred dns server either by changing their tcp/ip
config if statically assigned and changing dhcp scope option for dns server.
Once you are satisfied that the new dc is working well you can either
transfer the five fsmo roles to the new dc either via GUI such as AD Users
and Computers/Domains and Trusts/Schema mmc, using ntdisutil utility, or by
dcpromo to demote the old dc to member server if you do not want it to be a
dc anymore. Ideally you should have at least two domain controllers and a
backup plan to backup domain controllers including System State on a regular
basis. Good luck! --- Steve

http://support.microsoft.com/default...en-us%3B263532 -- hope
you don't need this, but just in case.
http://support.microsoft.com/default...lurb031902.asp


"Bill" <> wrote in message
news:0fbe01c4f578$c5cccaf0$...
> Our primary w2k server is on it's last legs. We need to
> create a backup and than fail the primary over. Any
> pointers to getting this done quickly?

Steven L Umbach

Hire a qualified system admin he will know how to back up your server.


"Bill" <> wrote in message
news:0fbe01c4f578$c5cccaf0$...
> Our primary w2k server is on it's last legs. We need to
> create a backup and than fail the primary over. Any
> pointers to getting this done quickly?

Robert Waters

Good answer mate! Maybe you should be an instructor

--
Wayne McGlinn
Brisbane, Oz

"Strange women lying in ponds distributing swords is no basis for a system
of government. Supreme executive power derives from a mandate from the
masses, not from some farcical aquatic ceremony"
- Dennis (sometime in the middle ages)

"Steven L Umbach" <> wrote in message
news:...
> Either using your backup software or with the built in backup do a backup
> of your domain controller including the System State which is very
> important as the System State contains Active Directory data.
>
> http://support.microsoft.com/default...b;en-us;240363
>
<snip>

Wayne

We have tried to hire someone but he clearly didn't have
the knowledge even though he had the certification. Can
you recommend someone in the Ft. Lauderdale, Fl area?
>-----Original Message-----
>Hire a qualified system admin he will know how to back up
your server.
>
>
>"Bill" <> wrote in message
>news:0fbe01c4f578$c5cccaf0$...
>> Our primary w2k server is on it's last legs. We need to
>> create a backup and than fail the primary over. Any
>> pointers to getting this done quickly?
>
>
>.
>

Bill

Thank you for your advise. I mentioned our server was on
it's last legs and part of that is the tape unit stopped
working, so no backups... which is driving me nuts. As an
alternative we have been copying win2K files over to our
linux box. We moved the DNS services off and use a netgear
router with our telco provider handling DNS. I would
prefer to put Domain Controller on samba (linux) but not
sure what other issues I would discover. We easily got off
exchange and use a linux product called bynari. We need
help but having a tough time fining qualified Microsoft
folks in our area. Would something like Ghost work if I'm
forced to stay with win2K? thanks again.
>-----Original Message-----
>Either using your backup software or with the built in
backup do a backup of
>your domain controller including the System State which is
very important as
>the System State contains Active Directory data.
>
>http://support.microsoft.com/default...b;en-us;240363
>
>Install your new server. Point it to the existing domain
controller as it's
>preferred dns server, then dcpromo it to be an additional
domain controller
>in an existing domain. Active Directory will replicate to
the new dc during
>dcpromo. Go to AD Sites and Services and make the new dc a
global catalog
>server. Configure your new dc to point to itself as it's
preferred dns
>server with the old dc as second in the list after at
least thirty minutes
>have gone by. Check Event Viewer to make sure things look
good with no dns
>or replication problems and verify that the domain dns
zone and the _srv
>records show on the new dc in dns mmc. You can use the
support tools
>netdiag, dcdiag, replmon, and gpotool to verify
health/configuration of the
>domain and domain controllers. Change to other domain
members to point to
>the new dc as their preferred dns server either by
changing their tcp/ip
>config if statically assigned and changing dhcp scope
option for dns server.
>Once you are satisfied that the new dc is working well you
can either
>transfer the five fsmo roles to the new dc either via GUI
such as AD Users
>and Computers/Domains and Trusts/Schema mmc, using
ntdisutil utility, or by
>dcpromo to demote the old dc to member server if you do
not want it to be a
>dc anymore. Ideally you should have at least two domain
controllers and a
>backup plan to backup domain controllers including System
State on a regular
>basis. Good luck! --- Steve
>
>http://support.microsoft.com/default...en-us%3B263532
-- hope
>you don't need this, but just in case.
>http://support.microsoft.com/default...lurb031902.asp
>
>
>"Bill" <> wrote in message
>news:0fbe01c4f578$c5cccaf0$...
>> Our primary w2k server is on it's last legs. We need to
>> create a backup and than fail the primary over. Any
>> pointers to getting this done quickly?
>
>
>.
>

Bill

"Bill" <> prattled ceaslessly in
news:1b1101c4f5b9$b90676e0$:

> Thank you for your advise. I mentioned our server was on
> it's last legs and part of that is the tape unit stopped
> working, so no backups... which is driving me nuts. As an
> alternative we have been copying win2K files over to our
> linux box. We moved the DNS services off and use a netgear
> router with our telco provider handling DNS. I would
> prefer to put Domain Controller on samba (linux) but not
> sure what other issues I would discover. We easily got off
> exchange and use a linux product called bynari. We need
> help but having a tough time fining qualified Microsoft
> folks in our area. Would something like Ghost work if I'm
> forced to stay with win2K? thanks again.
>>-----Original Message-----
>>Either using your backup software or with the built in
> backup do a backup of
>>your domain controller including the System State which is
> very important as
>>the System State contains Active Directory data.
>>
>>http://support.microsoft.com/default...b;en-us;240363
>>
>>Install your new server. Point it to the existing domain
> controller as it's
>>preferred dns server, then dcpromo it to be an additional
> domain controller
>>in an existing domain. Active Directory will replicate to
> the new dc during
>>dcpromo. Go to AD Sites and Services and make the new dc a
> global catalog
>>server. Configure your new dc to point to itself as it's
> preferred dns
>>server with the old dc as second in the list after at
> least thirty minutes
>>have gone by. Check Event Viewer to make sure things look
> good with no dns
>>or replication problems and verify that the domain dns
> zone and the _srv
>>records show on the new dc in dns mmc. You can use the
> support tools
>>netdiag, dcdiag, replmon, and gpotool to verify
> health/configuration of the
>>domain and domain controllers. Change to other domain
> members to point to
>>the new dc as their preferred dns server either by
> changing their tcp/ip
>>config if statically assigned and changing dhcp scope
> option for dns server.
>>Once you are satisfied that the new dc is working well you
> can either
>>transfer the five fsmo roles to the new dc either via GUI
> such as AD Users
>>and Computers/Domains and Trusts/Schema mmc, using
> ntdisutil utility, or by
>>dcpromo to demote the old dc to member server if you do
> not want it to be a
>>dc anymore. Ideally you should have at least two domain
> controllers and a
>>backup plan to backup domain controllers including System
> State on a regular
>>basis. Good luck! --- Steve
>>
>>http://support.microsoft.com/default...en-us%3B263532
> -- hope
>>you don't need this, but just in case.
>>http://support.microsoft.com/default...esks/webcasts/
> wc031902/wcblurb031902.asp
>>
>>
>>"Bill" <> wrote in message
>>news:0fbe01c4f578$c5cccaf0$...
>>> Our primary w2k server is on it's last legs. We need to
>>> create a backup and than fail the primary over. Any
>>> pointers to getting this done quickly?
>>
>>
>>.
>>

You should be able to backup to a network share mapped to a drive letter
with NTBackup.

--
Catwalker
aka Pu$$y Feet
BS, MCP
MCNGP #43
www.mcngp.com

"I'm not bossy! I just know what nerbbunchanumbers should be doing!"

catwalker63

Snip girl, snip!

--
Wayne McGlinn
Brisbane, Oz

"Strange women lying in ponds distributing swords is no basis for a system
of government. Supreme executive power derives from a mandate from the
masses, not from some farcical aquatic ceremony"
- Dennis (sometime in the middle ages)

"catwalker63" <_catwalker63_@hotmamamail.com> wrote in message
news:Xns95D892513CC32catwalker63athotmail@216.196. 97.136...
> You should be able to backup to a network share mapped to a drive letter
> with NTBackup.
>
> --
> Catwalker
> aka Pu$$y Feet
> BS, MCP
> MCNGP #43
> www.mcngp.com
>
> "I'm not bossy! I just know what nerbbunchanumbers should be doing!"

Wayne

"Wayne" <> prattled ceaslessly in news:#jhEwZd9EHA.2788
@TK2MSFTNGP15.phx.gbl:

> Snip girl, snip!
>

Stop top posting and maybe I will. Maybe.

--
Catwalker
aka Pu$$y Feet
BS, MCP
MCNGP #43
www.mcngp.com

"I'm not bossy! I just know what nerbbunchanumbers should be doing!"

catwalker63

First of FYI there is a big difference between a domain controller and a
file server. If you are indeed using a Windows 2000 domain controller [as
shown in My Computer/properties/network identification] then proper dns
configuration is a must and domain controller needs to be a dns server,
point to itself as it's only preferred dns server in tcp/ip properties and
as show by Ipconfig /all , and the domain members that are Windows 2000 or
XP Pro must point to your domain controller as their ONLY preferred dns
server. If that is not the case you will experience a lot of problems on the
network and looking in Event Viewer on the domain controller will probably
show a lot of errors. The article from Microsoft in the link below explains
this more and also how to resole internet names using an internal dns server
via a forwarder or using root hints.

http://support.microsoft.com/default...en-us%3B291382

A Linux server can be used as a file server. I don't know what the ability
is as a "domain controller" so I can not comment more on that. As far as
your server being on it's last legs. Well you could replace the tape backup
and you can use ntbackup to backup data and you should do that ASAP for the
System State. When you use ntbackup, you have the option to backup to a
network drive to a .bkf file or you can backup locally to your hard drive
and than copy to a network drive or burn to a DVD. Ntbackup can also
schedule backups. Maybe our server is repairable or upgradeable. Often a bad
power supply or clogged CPU fan/heatsink can lead to poor performance and
reliability. Memory [RAM] is a cheap upgrade as may be larger hard drive or
drives. If you have networking problems a new high quality network adapter
[ Intel] may be in order. Of course a virus scan should be done using the
latest virus definition from your vendor if the computer is not working
right and a scan for parasites with something like the free AdAware SE.
Often backing up the System State and important data, then reinstalling the
operating system [with the same Windows components - dns, wins, DHCP, etc as
used now] to a formatted system drive using the same tcp/ip address,
installing the same service pack, restoring the System State by booting into
Directory Services repair mode, then installing your applications and data
[after scanning for viruses on restore media] , and going to Windows Updates
to install critical updates will do wonders for a sluggish computer. If you
would try that I would definitely do a Ghost image first just in case things
don't go as planned. Also beware that if you have any Encrypted EFS files,
make unencrypted backups BEFORE your try to reinstall any computer or you
may lose permanent access to them.

As far as a Ghost image. If your goal is to move your domain controller to a
new computer, then the method I described in my first reply is the best way
to go by far. A Ghost image would work if for instance you wanted to put a
bigger hard drive in your current computer. If you want to use it to build a
new domain controller that can be a risky proposition. I have had instances
where a Ghost image installed in a different computer did boot up and work.
It depends on how well plug and play works. You may also be able to try it
and if it fails, then boot from the Windows 2000 install disk to try an
inplace upgrade [ repair option after the EULA agreement] which may then get
it to work but require that you install first the service pack and then all
critical updates. If you are moving to a new server with a raid array, I
seriously doubt it would work and you may have to proceed with the disaster
recovery on dissimilar hardware route using a System State backup. If you do
try a Ghost rebuild [nothing to lose to try] to a different server make sure
it is done off the network and that the new and old computer are never
connected to the network at the same time as big conflicts would arise with
two identical domain controllers with the same computer SID and IP address
on the network. Also you would want to shut down the old domain controller
and disconnect it from the network right after the Ghost image while you
attempt to build the new one from it and if successful then place the new
one on the network keep the other one in a safe place for a while until you
are sure everything is working right. --- Steve


"Bill" <> wrote in message
news:1b1101c4f5b9$b90676e0$...
Thank you for your advise. I mentioned our server was on
it's last legs and part of that is the tape unit stopped
working, so no backups... which is driving me nuts. As an
alternative we have been copying win2K files over to our
linux box. We moved the DNS services off and use a netgear
router with our telco provider handling DNS. I would
prefer to put Domain Controller on samba (linux) but not
sure what other issues I would discover. We easily got off
exchange and use a linux product called bynari. We need
help but having a tough time fining qualified Microsoft
folks in our area. Would something like Ghost work if I'm
forced to stay with win2K? thanks again.
>-----Original Message-----
>Either using your backup software or with the built in
backup do a backup of
>your domain controller including the System State which is
very important as
>the System State contains Active Directory data.
>
>http://support.microsoft.com/default...b;en-us;240363
>
>Install your new server. Point it to the existing domain
controller as it's
>preferred dns server, then dcpromo it to be an additional
domain controller
>in an existing domain. Active Directory will replicate to
the new dc during
>dcpromo. Go to AD Sites and Services and make the new dc a
global catalog
>server. Configure your new dc to point to itself as it's
preferred dns
>server with the old dc as second in the list after at
least thirty minutes
>have gone by. Check Event Viewer to make sure things look
good with no dns
>or replication problems and verify that the domain dns
zone and the _srv
>records show on the new dc in dns mmc. You can use the
support tools
>netdiag, dcdiag, replmon, and gpotool to verify
health/configuration of the
>domain and domain controllers. Change to other domain
members to point to
>the new dc as their preferred dns server either by
changing their tcp/ip
>config if statically assigned and changing dhcp scope
option for dns server.
>Once you are satisfied that the new dc is working well you
can either
>transfer the five fsmo roles to the new dc either via GUI
such as AD Users
>and Computers/Domains and Trusts/Schema mmc, using
ntdisutil utility, or by
>dcpromo to demote the old dc to member server if you do
not want it to be a
>dc anymore. Ideally you should have at least two domain
controllers and a
>backup plan to backup domain controllers including System
State on a regular
>basis. Good luck! --- Steve
>
>http://support.microsoft.com/default...en-us%3B263532
-- hope
>you don't need this, but just in case.
>http://support.microsoft.com/default...lurb031902.asp
>
>
>"Bill" <> wrote in message
>news:0fbe01c4f578$c5cccaf0$...
>> Our primary w2k server is on it's last legs. We need to
>> create a backup and than fail the primary over. Any
>> pointers to getting this done quickly?
>
>
>.
>

Steven L Umbach