Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 499
  • Last Modified:

Changing name of Netware 5.0 and transferring to new hardware

Hey folks,

My NW6.5 upgrade is delayed another few months so this is what I plan to do this week:

- Duplicate the NW boot volume and boot up on the new hardware;
- Install/replace device drivers (Ethernet and SCSI controller).
  Hopefully, I can find compatible drivers for the Adaptec 2120S controller and the Gigabit Ethernet card);
- Copy the entire contents of my current server across the wire (The server name will be different)
  Should I do this from ConsoleONE (drag and drop) or is there a better tool?
- Once everything is done, shut down the old server and change the server name of the new one.

Steps involved in changing a NW 5.0 server name:
- Edit the AUTOEXEC.NCF file, and restart the server;  
- Run SETUPNLS to set up NLS with the new server name;
- Change the NDS volume name in ConsoleOne

My greatest concern is driver compatibility, however...

My question is: Are there any other potential 'kinks' in the above plan?

Later on, I plan to perform an in-place upgrade from Netware 5.0 to 6.5.

Thank you for your input!
SDC

I also have a few other high value questions:
http://experts-exchange.com/Web/Graphics/Q_21418476.html  - 250pts
http://experts-exchange.com/Hardware/Handhelds_Wireless/Q_21418424.html  - 250pts
http://experts-exchange.com/Hardware/Q_21411451.html  - 300pts
http://experts-exchange.com/Web/Browser_Issues/Q_21406038.html  - 125pts
http://experts-exchange.com/Operating_Systems/Win2000/Q_21379033.html - 125pts
http://experts-exchange.com/Storage/Q_21419457.html  - 175pts
0
Shawn Connelly
Asked:
Shawn Connelly
  • 7
  • 4
  • 2
  • +2
4 Solutions
 
ShineOnCommented:
Too bad the Migration Wizard won't do 5.0 to 5.0 hardware migration.  Essentially, what you're doing is an across-the-wire hardware migration, manually.

The biggest problem you'll face doing it the way you plan is trustee rights.  Be sure to back up the trustees on the old one, and then restore them to the new one, or you'll have some very disappointed users.  I believe you can do that using trustee.nlm (or is it trustees.nlm?)  - you can check www.novell.com/coolsolutions for tools to back up NetWare volume trustees.

Do the file copy and rename the server before restoring the trustee rights.  Be sure to run trustee(s?).nlm on each volume on the old server, and copy the backup files to the new server to restore the rights from.

When you're ready to restore the rights, first blow away any trustee rights that might have gotten applied during the migration process.  After that's done, use trustee(s?).nlm to restore the rights for each volume.

Make sure you do plenty of DSREPAIRs throughout the process to make sure NDS stays healthy.

Is this a single-server tree, or ?
0
 
ShineOnCommented:
Oh, and rather than duplicating the NW boot volume, you should probably do a fresh install to the new server, and apply the last SP5 support pack, before you do the copying and the personality swap.
0
 
umang505Commented:

1.Duplicate the NW boot volume and boot up on the new hardware;
For this the best tool available is Portlock StorageManager, even Novell uses this tool to make images for "Digital Airlines CD"
If possible get a single server lic from Portlock,Image the  NW boot volume first.
Restore the Image on the new Hardware.
Once the image is restored, preform step 2. because without SCSI controller drivers your volumes won't mount assuming they are on SCSI Hard disks.

2.- Install/replace device drivers (Ethernet and SCSI controller).
  Hopefully, I can find compatible drivers for the Adaptec 2120S controller and the Gigabit Ethernet card);---->Sure you can find.

3.- Copy the entire contents of my current server across the wire (The server name will be different)
  Should I do this from ConsoleONE (drag and drop) or is there a better tool?
As i already told above use StorageManager to image the entire server.You won't loose anything (user rights on files etc. etc. )

4.- Once everything is done, shut down the old server and change the server name of the new one.

Best of luck.
 P.S. I am recommending Portlock because i am one of their satisfied existing customer
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
pgm554Commented:
Here is a simple method that has worked for me using Server Magic from Symantec(PowerQuest)

Install Smagic on the old server.

Make a Server Magic IP boot disk using the Smagic utility.

On the new server ,boot the server using the IP boot disk.

Then use Smagic to find the target server and you can then copy whatever partitions you want migrate(and resize them) to
fit on the new server.(At least a 4 Gig Sys for NW6.5 and a 200 meg or larger for your DOS)

Reboot and reconfigure your hardware drivers and your done.

A real no brainer.  
0
 
Shawn ConnellyTechnical WriterAuthor Commented:
Thank you everyone!

umang505: Thank you for this! Are you telling me that Portlock will allow me to duplicate an entire server across the wire?

SDC
0
 
Shawn ConnellyTechnical WriterAuthor Commented:
pgm554: Intriguing! I shall look at this too.

Question: I have always (and successfully) used an IDE hard drive for the DOS Netware boot volume. The reason is that this volume can be easily duplicated and stored as a hot pluggable hard drive in a vault. The contents never change unless service packs are applied (which is irrelevant at least with Netware 5.0) so this serves as a quick and easy disaster recovery tool in the event of a system failure.

Like I have stated, I have never run into technical problems doing it this way since Netware 4 (IDE failures are covered by IDE RAID 1). I am asking if there are any reasons why I should not use an IDE drive for the DOS boot partition especially now that I am preparing new hardware for an eventual upgrade to Netware 6.x.  
0
 
ShineOnCommented:
The reason I suggested a fresh install on the new server is so you don't have to do an after-the-fact adjustment to partition sizes, but to create them fresh with adequate sizes for 6.5 for both C: and SYS: partitions.  Also, keep in mind that NW6x should have SYS: on its own partition in its own NSS pool, separate from your data volumes' NSS pool(s).  

If the upgrade to 6.5 will be happening within the next month or 2, I'd just put this off until then, and do an across-the-wire upgrade, rather than having to do an in-place upgrade.  However, if you have the hardware sitting there idle, and the 6.5 upgrade won't happen for a year or 2 (probably will be OES/NW7/SLES10 by then) it makes perfect sense to do what you're planning, and budget new hardware for it, too, so you can do an across-the-wire.  The server won't be wasted, 'cause you can install as many NetWare 6.x servers as you want, with the 6.x licensing model, and not pay another dime for server licenses.
0
 
pgm554Commented:
My personel opinion is to use RAID 5 .

IDE disks are not as reliable as SCSI(HDA on SCSI have a better MTBF than most IDE,the exception being the WD Raptor and you will pay equivelent $$ vs SCSI).

I would go for a RAID controller with a battery backup for the cache memory($150 bucks Xtra on the 21xx).

If for some reason or other the system hangs or loses power and the data is not written to disk ,you will either lose that data or it will get corrupted.
0
 
ShineOnCommented:
The DOS boot partition in NetWare does hold the NetWare registry.  Any settings change that is not done via a SET command in STARTUP.NCF or AUTOEXEC.NCF will be stored in the NetWare registry.  I prefer having all my volumes on a RAID5 array, and using tape backup for disaster recovery.

Having a separate, IDE "boot drive" is so... Gateway.
0
 
Shawn ConnellyTechnical WriterAuthor Commented:
>Having a separate, IDE "boot drive" is so... Gateway.

:-)

0
 
umang505Commented:
Hi sconnell
Yes Portlock can image your entire server over the Network.No need to install anything on the new server.i have replaced hardware  for my netware server successfully using this.

pls have a look at the following question regarding portlock if that helps.

http://www.experts-exchange.com/Networking/Netware/Q_21385281.html
0
 
BigBadFletchCommented:
If this was my project, I would build the new 6.5 server the way I wanted it to be and then upgrade my 5.0 to 5.1 then use Novell's Server Consolidation utility to migrate the data only. the latest can be found at:

http://download.novell.com/Download?buildid=MT4w81MihYE~

good luck
0
 
Shawn ConnellyTechnical WriterAuthor Commented:
Hello BigBadFletch,

Thank you for the tip!  The only problem is that version 4.0 (from your link) doesn't link to a downloadable file, Novell responds with, "The file you are trying to download is currently unavailable. System administrators have been notified. Please try your request again later."

I can download version 3.0 from http://download.novell.com/Download?buildid=m6JyOqHsILs~ but where is 4.0 and/or what is the difference between the two versions (and what is with the wacky urls)?

- I am still looking at the other options such as portlock.
0
 
BigBadFletchCommented:
sorry about the link. you can get to the same place by going to :

http://download.novell.com/index.jsp

and searching on the keyword: nwsc.exe  ( you don't need to select a product or a software version or anything )

two items show up in the result window :
Novell NetWare Server Consolidation Utility 3.0        Oct 27, 2004          19.2 MB
Server Consolidation Utility 4.0                                 Apr 6, 2005         19.7 MB

as for the differences:
Server Consolidation Utility 4.0 adds two significant new features:

    * You can consolidate data from NetWare® and Windows* servers to Open Enterprise Server (OES) servers running on either NetWare 6.5 or SUSE® LINUX Enterprise Server 9. The destination server must have the NCPTM Server component installed, and destination volumes must be Novell Storage ServicesTM (NSS) volumes.
    * When consolidating file system data from NT servers, the Server Consolidation Utility now copies ownerships for NTFS files and folders in addition to copying the permissions.

*note all of the documentation on this product can be found at: http://www.novell.com/documentation/servercon40/
good luck.


0
 
Shawn ConnellyTechnical WriterAuthor Commented:
Sorry... just a quick note.... I'll get back to this question on Tuesday Aug. 2..
0
 
Shawn ConnellyTechnical WriterAuthor Commented:
Sorry folks.... my bad, this one went off my RADAR again.  I've printed this out and I shall award points tomorrow.
0
 
Shawn ConnellyTechnical WriterAuthor Commented:
I hope I was fair with the grading!  Thanks everyone!
0

Featured Post

[Webinar] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 7
  • 4
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now