Change of Hardware

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Dear All,

We have an IBM Intel Server (X-350) running on Windows 2000 which is over 4
years old.

Is there a way to dump the entire backup (using Veritas Backup Exec 10) onto
a new server (X-346) – the backup containing our entire ERP Data & MS SQL
2000?
The whole problem is that this new server’s name & IP has to be identical to
the old one.

I would appreciate it if someone could kindly guide me with this! We tried
the same during this entire weekend – but unfortunately, Windows 2000 was
unable to boot up!

Rgds
Nailesh
 
Nailesh said:
Dear All,

We have an IBM Intel Server (X-350) running on Windows 2000 which is over 4
years old.

Is there a way to dump the entire backup (using Veritas Backup Exec 10) onto
a new server (X-346) - the backup containing our entire ERP Data & MS SQL
2000?
The whole problem is that this new server's name & IP has to be identical to
the old one.

I would appreciate it if someone could kindly guide me with this! We tried
the same during this entire weekend - but unfortunately, Windows 2000 was
unable to boot up!
Click to expand...

You probably can do this by doing the "restore" to the new server and then
boot from your Win2K setup disk and run a repair operation. Ignore the first
screen where setup offers a repair option, past the EULA, to the last screen
where setup detects the "old" installation and offers to repair it. Note that
this will revert the installation to the service pack level of the original
installation and you will need to reapply any subsequent service packs and
security patches after the repair operation.
 
Hey Gary,

Thanks a million for the taking the time to get back to me! Appreciate it!

Will try the same this weekend & let you know!

Rgds
Nailesh
 
Dear Gary,

I tried your suggestion. I first pressed F6 & (custom) loaded the IBM RAID
7i driver & on coming to the Recovery screen, I used the Emergency Repair
Disk.

On server restart, I got the same below error.


Windows 2000 could not start because of a Computer Disk Hardware
Configuration problem.
Could not read from the selected boot disk. Check Boot Path and Disk hardware.
Please check the Windows 2000 Documentation about Hardware Disk
Configuration and your hardware reference manuals for additional information.


Hope you can still help me! Just a small note – the earlier server was an
IBM X-350 (Raid 5i) & the new one is IBM x-346 (Raid 7i).

Rgds
Nailesh
 
Did you do the repair operation from the first setup screen or the repair
reinstall from the last setup screen? It's confusing because they're both
called repair operations. The first one basically only checks for missing
files and minor configuration problems and will not fix this problem. The
second does a complete reinstall. If you were not required to enter the
product key, you did not do this operation.
 
Gary, after the EULA screen, I get the Windows 2000 Server Setup screen where
I get to see options:
1) To setup windows 2000 on selected item, press “Enterâ€.
2) To create a partition in the unpartitioned space, press c
3) To delete the selected, press d.

If I continue & choose the 1st option, I get messages that states the below:
“You might be installing Windows 2000 on a partition that contains another
Operating System. Installing Windows 2000 on this parition might cause the
other OS to function improperly.â€

If I press C, I get 2 options:
1) To format with NTFS file system
2) Leave the current file system intact.

If I then choose the 2nd Option, I get a screen tht says the WINNT folder
already exists and then below, there are 3 options.
1) To use the folder and delete the existing windows installation in it,
press 'L'
2) To use another folder, press ESC
3) to quite setup, ise F3

If I choose Option 2, I get an option to install the Windows on a different
folder which I can specify.


As u can notice, there are no Repair options after the EULA screen. There
is a repair option before the Repair Screen. Actaully Gary, based on
previous experience, I too remember seeing a Repair option after the EULA
Screen. Anyhow, this time around, I can’t see the second repair screen.

Kindly do suggest!
 
That means that you don't have a recognizable Windows installation on the
drive. You are probably missing the Registry files. Without them, you can't
do a proper repair. Do you have a repair disk for this system?
 
Two ideas. One would be to try the other type of repair operation (the
one offered on the first setup screen) using the repair disk. This will
probably not fix the problem of the wrong drivers but it should fix the
problem of the missing Registry. If so, then try the other repair operation.

The other would be to go back to the original and either find the missing
files or start over.

I just had a third idea. Look in the System32 folder for a Repair folder
and see if there is a copy of the Registry in there.
 
Gary,

Actually, did try Idea 1 – did not work.

We then used Veritas Disaster Recovery once again & it seemed to work.

Anyhow, been live on this new server for 3 days & except for a minor RAID
Controller problem (that our IBM Hardware guys need to sort out) – the server
seems fine!

Appreciate your help, support & suggestions.

Have a nice day!

Rgds
Nailesh
 
Back
Top