Restore Netware from one server to another. 2

[NetworkDOC]

The goal: To bring in a new server hardware to replace an older server nw 5.1 whose hardware is showing signs of wear (failed drives etc). I am thinking it would be faster to perform a restore from tape to the new server (not sure yet how to do this) as opposed to the 6.5 nw migration tool. This isn't an upgrade just switching server hardware.

I did run the nw migration tool, with 80+ Gb of data the file copy portion took about 12 hrs. Then it failed when I tried to edit the config files (autoexec.ncf and hosts files). Wouldn't let me complete the move without resolving that. Not sure why it wouldn't write it either. Anyway I ran out of time in my window.

So that brings me to a question: Couldn't I do a restore from veritas (9.1) to a new server and get it done quicker? The backups take 8 + hrs to do. I figure a restore shouldn't be that much different.

Any suggestions/feedback/gotcha's? NW 5.1, veritas 9.1, all are patched to latest.

 

[nwoliver]

I also would be interested in getting definitive tips on the best way to migrate from an older box to a new one, but remaining on NW5.1 There are some pretty serious DS issues when moving from one box to another and can't afford to waste time screwing it up two or three times

 

[marvhuffaker]

Here's a way I like to do a NW5.1 to NW5.1 hardware upgrade...

Leave server #1 running. don't mess with it for now. Install NetWare 5.1 on Server #2, insert into tree. It should get a complete replica of the entire tree (assuming small environment). If not, add the replicas to match what Server #1 has.

Use BEYOND COMPARE from

http://WWW.SCOOTERSOFTWARE.COM

to get a complete copy of data from Server #1 to Server #2. You can use it during the process for any changed data as well. Put SYS: From Server #1 into a safe location on Server #2 -- don't overwrite SYS: on Server #2.. You just want a backup in case you miss any files.

Use TRUSTBAR.NLM to make trustee assignment backups.. Make sure to copy the resulting file(s) to the new server.

Remove Server #1 from tree. Clean up NDS if necessary. Rename server #2 to server #1. Do a TRUSTBAR to restore trustees.

You may have to deal with some services, for example printing.. the queues would have to be recreated if you use them. If you're using NDPS, you can pretty much just move the manager and it will take care of it for you.

There may be other things to consider. But this would work in a majority of situations where the server is doing file/print and not much else. When all said and done, users should not even know there has been a server change.



Marvin Huffaker, MCNE

http://www.redjuju.com

 

[nwoliver]

Very cool, thanks very much. This is precisely what I was after.
nwo

 

[marvhuffaker]

The nice thing about doing it this way is that you don't have to mess with trying to do an NDS backup/restore... The simple act of replication will give server #2 everything it needs.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[NetworkDOC]

Great suggestion...

When you rename a NW 5.1 server, can't you just edit the autexec.ncf, hosts and hostname files? If so then the down time is minimal.... I like it a lot.

 

[marvhuffaker]

Technically you can do that with any NetWare server, even NetWare 6.x... The problem you run into is that many of the new web based services have separate configuration files that specify the ip address to listen on. Add GroupWise and there are even more things to change.

But for basic NCP, you can usually get away with just editing the AUTOEXEC.NCF and the Hosts file, reboot and you're done.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[ITsmyfault]

so when you make the name and IP match, the whole TLS/KMO etc etc thing takes care of itself? Or do you generally have to do some PKIDIAG stuff post-move?

 

[marvhuffaker]

Um...

I forgot all about those

PKIDIAG will usually do the trick though.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[nwoliver]

I know that this is probably dumb question of the week, but now that I have the new server loaded, the movement of files across to the new one from the old one using the Beyond Compare application is no more than a typical copy from one machine to the other, correct?

Assuming that is the case, then restoring the files from a backup tape would be just as good, maybe better, and the Beyond Compare can be used to merely determine whether things are synchronized or not.

Then the trustbar.nlm would be used to remake the trustee assignments on the new server and then that is it (with the exception of server name changes, etc. of course)

 

[marvhuffaker]

Yes, you're just doing a simple file copy. So however you can get the files there the fastest is great..

Your tape may also put the trustees in place too, but you should verify that before you skip trustbar.

The great thing about Beyond Compare is that you can look at two different file systems and easily find any differences in the two. You can't do that with Windows Explorer. I use Beyond Compare anytime I am moving data.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[nwoliver]

Thanks.. I don't plan on skipping trustbar in any case. It will be the last thing done before pulling the plug on the old server and bringing the new one online for my users. Now I have to find a NW6 cd from which to pull the utility. Thanks very much for all your assistance.
nwo

 

[LLindsay]

Marvin is dead on and I would like to add to his thread. I hope not to offend anyone if I post what may be obvious to most. You will get the file trustees back from tape. Veritas -Backupexec -Netbackup does support this. We recently replaced 65 servers with new hardware and found that the migration tool works great. (No tape was used) It has one problem, it can behave oddly if there are any user space restrictions. Remove them before migrating. We too have Beyond Compare, but still used the NW Mig. The tool works for migrating NDPS printers. If you're still using queues you will need to disconnect the queue first and reasign on the new server. I would migrate volumes over a three day period due to the large number of volumes and size. The migration tool takes care of the deltas and file trustees. Don't forget the trustbar for the volume level trustees. Once the volume(s) is migrated, change the DMO to redirect the users login script, and dismount or rename the old volume. There is no need to rename a server, just point to the new one. Renaming becomes a hassle, even more so when you move into the NW6 and OES environment with the "i" tools and web services.
Keys files you will want to move to the new server along with the volumes are;

trustees.xml files

*.POA (Change the server name and IP information)& GRPWISE.NCF Close the PO on the old server for the final run of the migration of the email volume. There is a procedure to suspend the PO at the MTA before completing the migration and changes to point to the IP of the new server.

TIMESYNC.CFG, SLP.CFG

NetBackup files: BP.INI and *.TGT (Change server name)