Install Win2K Server to a different Root directory
I am writing up and testing a Disaster Recovery Plan. A few servers we use are Win2K Servers that we have backed up using NTBACKUP. In understand how to restore (I think), from research, I have determined:
1. Install Win2K with same service pack to a different root like C:\TMPNT
2. Run Restore from NTBACKUP and restore all files and registry, overwriting all files.
3. Boot and Test.
My questions are:
How do I install to a different root? The install from the box gives me no option, is this in the boot.ini file or something and I need to change it and create a new CD?
Can I delete C:\TMPNT when I am done?
Thanks
WG
1. Install Win2K with same service pack to a different root like C:\TMPNT
2. Run Restore from NTBACKUP and restore all files and registry, overwriting all files.
3. Boot and Test.
My questions are:
How do I install to a different root? The install from the box gives me no option, is this in the boot.ini file or something and I need to change it and create a new CD?
Can I delete C:\TMPNT when I am done?
Thanks
WG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So far so good. I changed the TXTSETUP.SIF Default Path.
I also managed to slipstream the SP4 onto the Install disk (2 steps in 1).
I will bump the points if anyone wants to answer:
I did the restore with overwriting all files (I had backed the system state and chose it on the restore).
Why do I get the "Windows 2000 could not start because the following file is missing or corrupt \WINNT\SYSTEM32\CONFIG\SYS
I restored the system state. I see talk on google of renaming system to system.old and renaming system.alt to system, but none of the above exists???
Upon the Repair option, I can login into TMPNT or WINNT
What files to copy at that poiint?
I also managed to slipstream the SP4 onto the Install disk (2 steps in 1).
I will bump the points if anyone wants to answer:
I did the restore with overwriting all files (I had backed the system state and chose it on the restore).
Why do I get the "Windows 2000 could not start because the following file is missing or corrupt \WINNT\SYSTEM32\CONFIG\SYS
I restored the system state. I see talk on google of renaming system to system.old and renaming system.alt to system, but none of the above exists???
Upon the Repair option, I can login into TMPNT or WINNT
What files to copy at that poiint?
So, if I understand what you have done:
- You sucessfully installed Win2K in a non-default directory ( C:\TMPNT)
- You then restored a backup. This include the entire C: volume *and* the system state, right?
- boot then fails with the message you show above
What is the size of the restored \WINNT\SYSTEM32\CONFIG\SYS
- You sucessfully installed Win2K in a non-default directory ( C:\TMPNT)
- You then restored a backup. This include the entire C: volume *and* the system state, right?
- boot then fails with the message you show above
What is the size of the restored \WINNT\SYSTEM32\CONFIG\SYS
ASKER
I am developing the DR plan for the company. We use V2i for most servers, but a few are NTBACKUP'd.
ALL on TEST system
I have wiped the drive and re-installed Windows in a C:\TMPNT directory. I was lead to believe I could restore and reboot, then remove the old directory (c:\tmpnt)
I have installed using that and done the restore, it asks for a reboot and then tells me the registry is corrupt or missing. I have gone into restore mode and renamed the c:\WINNT\SYSTEM32\CONFIG\S
I also tried using the c:\winnt\repair\regback\sy
Finally I tried copying the system and/or the system.alt (renaming) from c:\tmpnt\system32\config over to the winnt side....again I get innaccesible boot device blue screens.
SO I took your advice and clean installed to c:\winnt and did the restore. It did not prompt for reboot, but I did one anyway.
I have had to reload all my drivers (which they were all there, I just deleted the devices in Device Manager and they re-acquired), I also get messages about duplicate names on the network. It is NOT part of the domain (so it would appear anyway). Also, the Antivirus isn't starting (likely because the registry isn't right)....
HELP. (I've upped the points)
WG
ALL on TEST system
I have wiped the drive and re-installed Windows in a C:\TMPNT directory. I was lead to believe I could restore and reboot, then remove the old directory (c:\tmpnt)
I have installed using that and done the restore, it asks for a reboot and then tells me the registry is corrupt or missing. I have gone into restore mode and renamed the c:\WINNT\SYSTEM32\CONFIG\S
I also tried using the c:\winnt\repair\regback\sy
Finally I tried copying the system and/or the system.alt (renaming) from c:\tmpnt\system32\config over to the winnt side....again I get innaccesible boot device blue screens.
SO I took your advice and clean installed to c:\winnt and did the restore. It did not prompt for reboot, but I did one anyway.
I have had to reload all my drivers (which they were all there, I just deleted the devices in Device Manager and they re-acquired), I also get messages about duplicate names on the network. It is NOT part of the domain (so it would appear anyway). Also, the Antivirus isn't starting (likely because the registry isn't right)....
HELP. (I've upped the points)
WG
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
1. Understandable how that could happen. Once I do the regular install it shouldn't matter.
2. We are assuming same hardware. I had to "uninstall" all of the devices that weren't sure of drivers, do a scan and miraculously it found all the drivers in winnt\inf, etc.
3. Obviously we have to remove the PC/Server from AD so that on reinstall it can be the only one with the name.
4. AVG Antivirus Network doesn't want to initialize or something.
I have since removed and re-added to the network and it isn't working still.
Cany someone send me there recovery process using NTBACKUP?
Thanks
WG
2. We are assuming same hardware. I had to "uninstall" all of the devices that weren't sure of drivers, do a scan and miraculously it found all the drivers in winnt\inf, etc.
3. Obviously we have to remove the PC/Server from AD so that on reinstall it can be the only one with the name.
4. AVG Antivirus Network doesn't want to initialize or something.
I have since removed and re-added to the network and it isn't working still.
Cany someone send me there recovery process using NTBACKUP?
Thanks
WG
#3....ah, you have made a mistake here. When you restore the system state, you restore the complete registry including the SID of the original system. You should not remove the machine from AD....the restored machine will look exactly like the original to AD (aside from a machine password that could be out of date). This is a bit tricky for testing...you should take the original machine offline before booting up the restored machine, or have a test copy of the domain.
ASKER
Still same problems exist. It told me Duplicate name problem. Still no AV working, other Service based items simply not there.
I have had to go to a different model whereby I rebuild the server. Seems like it will take less time.
I have had to go to a different model whereby I rebuild the server. Seems like it will take less time.
My experience is that rebuilding servers from scratch just is not realistic for most organizations. Very few organizations are able to keep track of everything they have done to set up their servers. Restoring from complete backups is the only realistic option in most cases. It's not easy, but it's the only thing that really works.
What exactly is the message you are getting about "duplicate names"?
ASKER
Since the original issue was creating a different root, EZRA got points. The addition of the DR issue, though never resolved (mainly due to time constraints) was addressed by Carlo.
I thank you both for the time you spent. It seemed like SUCH an easy task, but obviously it just didn't create the solution I was looking for. Sorry it took so long to accept and award.
WG
I thank you both for the time you spent. It seemed like SUCH an easy task, but obviously it just didn't create the solution I was looking for. Sorry it took so long to accept and award.
WG
If restoring over top of a new install, the new install must be the same language and edition (W2K Server, W2K Advanced Server, W2K3 Web, W2K3 Enterprise, etc.) as the system you are restoring. I would also recommend that the service pack level of the new install be the same or *older* than the system you are restoring.
Does your recovery plan assume you will have identical hardware? Trying to restore a Windows system onto different hardware introduces a very unpredictable set of problems.