6 replies
by jose mir
Netware have migration utilities wich you can use to perform a proper migration. You could migrate data and the NDS from server to server or using a workstation as midle storage.
If you are on a hurry, and if you have instaled correctly the old system, you could (almost 99.99% of the times) install the old disks in the new server (you will need to lad the new interface card drivers) and make the corrections, patchs, and drivers updates whit time and wiselly!
Maybe you could invite some windows managers friends and give them a good impression!
Jose P. Mir.-
by jimbb
Do not use the same disks in the new server. Bad idea. Unless you're sure you're using the same hardware, and I doubt that will be the case.
In stead, try the following:
-Install the DL380 in a dummy tree. use the same softwares and service pack as on the 1600.
-Transfer all data using whatever tool you feel comfortable with. Explorer is good enough, if you're connected to both trees/servers at the same time. Never mind about access rights, not yet.
-Download tback3.exe from Novell, and run it on all your volumes (in a DOS box on a workstation), to make a backup of your trustees (=file- and directory rights). Copy the result files (trustees.bat) to the new server too.
-on a workstation, log in into both trees as Administrator equivalent.
-On the 1600, do NWCONFIG|Directory options|Directory backup and restore options|save local NDS information before hardware upgrade. Follow the instructions, and place the created file on your workstation. ***Warning*** As from this moment the 1600 is no longer accessible, NDS does not run on it anymore!
-Copy the file to SYS:\SYSTEM on the DL380
-On the DL380, run NWCONFIG|Directory options|Remove Directory Services from this server (to get rid of the dummy tree).
-On the DL380, run NWCONFIG|Directory options|Directory backup and restore options|Restore local NDS information after hardware upgrade. Point to the file you just placed in SYS:\system. Restart your server to double-check DS loads properly.
-Run the result-batchfiles from TBACKUP (made earlier). If your volumes have a different name or so, you may have to adapt them first.
And that's it. Beware, don't do this during office hours, and do not even start a thing without being sure of having a proper backup.
Jim
by cfrost
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending