Restoring a backup on to a new server from old.

[mw2com]

I am moving all the data from an old server HP Netserver. to a new Compaq Proliant ML330 all seems to go well with the install untill i restore the backups

i restore the /u and all the user directorys are there

then i restore the root the all the programs and users are in the database and all seems ok untill i access over the network

the network card has gone but the one out of the old server is there !!!!!

and when i change anything in the hardware and relink the kernel all heck breaks loose..... i get a load of errors listing down the page and when i go to reboot, it can not see the scsi hard drive anymore...

is there any way to restore the data files and user database but not any of the old hardware ??

THIS IS URGENT PLEASE HELP

 

[edfair]

Better to rebuild with current hardware and restore programs and data only. Hardware stuff that root tries to carry over will give you fits. Probably better to generate new users also. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[mw2com]

i only wish i could i dont know what is programs and what is hardware

i have restored the following dirs without problems

system
bin
comms
dev
etc
ibin
lib
lost+found
mnt
once
tcb
swap
shlib

but when i restore my \opt dir i can not sem to relink the kernel

 

[edfair]

Some in /etc is user specific, some in /etc/default is hw dependent, and lots in /dev is hardware dependent.
I suspect that the /dev is critical on the scsi problem.
I've done what you are trying on several systems and fought with every one for various reasons. Response has been to document the install sequence on any machine I build up so I can duplicate it totally with any other hardware I have to use, since the replacement will be different, just because of the passage of time. Documentation has user, program, printers and ports information since any of it may be obsolete or broken and need to be replaced.
Know this isn't a help now, but maybe it will help on the rebuild so the next occurance won't be as bad. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[Megabitman]

There is a fairly good tech note (at least there was prior to the Caldera changeover) on the SCO web site regarding organizing your file systems for easier migration. All tech notes (and personal experience) indicate that SCO really wants you to reload the OS and recreate the device drivers and merely transport the programs and data files from installation to installation. The user information can be transported via the ap command (review the man pages on that command for help), but you will need to figure out where your software and data files reside and tar them off. One side note, many times you can guess as to many of the files via the ls -lt command ( it will list files in a directory in chronological order and as a GENERAL rule, most os files will not be altered, you might be able to discern the non-SCO files and/or directories, exceptions being files like /etc/passwd or /etc/ttytype or /etc/inittab, but you probably get the idea).

Good luck.