Extend a Netware partition on new Harddisk

[Guest_imported]

I'm having a Netware 4.11 server with 2 GB harddisk. Now, I want to replace this 2 GB hd with a 20 GB hd and want to remain all the users and applications as well.

If I used Norton Ghost or PQDI image s/w, I could not use the remaining 18GB as netware partition. The only method I could do is to install a fresh Netware 4.11 into 20GB hd with recreating users, install all the applications again and copy data from the old hd.

Is there any straight forward method to do the hd migration?

Could I do the mirroring method with different size of netware partition?

Thanks for giving me some ideas.

 

[salserocito]

Check out this TID...

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10027322.htm

This TID basically explains how to use DSMAINT to backup and restore your NDS when you are doing Server Hardware Upgrades.

Here are the General Steps involved...
1. FULL AND COMPLETE BACKUP OF YOUR SERVER!!!!!
2. Print a copy and make a copy of your AUTOEXEC.NCF and STARTUP.NCF. You will need this for reference later.
3. Load DSMAINT.NLM
4. Select "Prepare Directory for Hardware Upgrade" - when this is run, a file call BACKUP.DS is created in your SYS:SYSTEM Directory. Directory Services will immediately close. Copy the BACKUP.DS file to your local Harddisk.
5. Down the Server and replace the hard drive.
6. Re-install NetWare, give it the same SERVER NAME and IPX INTERNAL NETWORK ADDRESS! BUT... When it comes time to install Directory Services and insert the Server into a Tree, CREATE THE SERVER IN A NEW TREE!!!
7. Once NetWare has been completely installed, install the latest Support Pack for NW 4.11 (NW4SP9A).
8. When you have successfully installed the Support Pack and you have re-booted your server, login to this Server as Admin and copy the BACKUP.DS file from your Harddisk to the SYS:SYSTEM Directory.
9. LOAD INSTALL and REMOVE DIRECTORY SERVICES. Close INSTALL.
10. LOAD DSMAINT
11. Select "Restore Directory after Hardware Upgrade" - this will effectively re-install the DS that was running on your old Server.
12. Restore any pertinant data from Tape Backup such as User data, applications, etc.

Good Luck!

 

[yizhar]

HI.

Check the symantec site for a specific Ghost for NetWare version.
They had such product in Beta but I don't know if they have finished and published it.

I'm also in favor of the backup & restore method.
There are at least 2 advantages:
* This is a great chance to test and prove for yourself what your backup is worth, and to do a very important practice that will help you with disaster recovery in the future.
* Anyway you must create a good backup before the upgrade, so why not use it now..

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[Bluenose]

Or if you're feeling brave try Partition Magic. This utility allows you to change partition sizes.
The backup and restore is the least risky way though.

 

[TheBoySmith]

For our customers I use servermagic.

quick step guide.
1. Install new 20gig into server.
2. Make sure server boots of original disk and can see new disk.
3. From dos create a dos partition on new disk, same size or bigger than original one.
4. xcopy c:\*.* d:\*.* /s/e/v
5. bring up server from original disk.
6. with server magic mirror existing disk netware partition to new drive. (Yes it will create a 2gig partition on new disk but hold on)
7. When the mirror is completed restart server and check the mirror is synchronised.
8. If all mirroring is good take down server.
9. Remove old 2gig disk from system and make sure the new 20gig disk is bootable (If scsi ensure the ID is 0 or 1. If ide make sure it is a master)
10. Load server from new disk. (The server will load and be as it was on old disk.
11. With servermagic increase the netware partition from 2gig to 20gig or what ever the maximum is.
12. With servermagic sort out the size and placement of the existing volumes.
13. Go home and have a drink.

That is the summary way I do it and has saved me hours if not days of messing about re-installing, re-patching getting drivers etc etc etc Lee Smith
Associated Network Services
Snr Systems Engineer
Lee.Smith@ANSPLC.Com

 

[cyberdyne]

This is what I found at

http://mft.ucs.ed.ac.uk/novell/faq/nvfaq-h3.htm

H.29 Spanning a volume across multiple hard drives

There are probably only two situations where you want to do this:

- If you have redundancy, in the form of RAID, mirroring, or duplexing
- If you simply don't care about the data you're putting on that volume.

If you span a volume across multiple hard drives, essential information such as the file allocation tables, the directory entry tables, and even the files themselves will be split across the drives. The loss of any single drive destroys the _entire_ volume, as some of each of the above types of data will be lost. That's right - not just the data on that one drive, but the _whole_ thing. Probably not what you want!

Keep in mind also that the MTBF (Mean Time Between Failure) of a number of identical drives is the MTBF of one drive divided by n. That means n times as many failures, on average, in any given period, and each one of those failures takes your whole volume with it. Each time it fails, you'll be recreating the volume and restoring all that data. Oh, and if it's your SYS: volume, you'll have to reinstall NetWare first.
From:
Apoorva Gala
You can mail me at apoo1972@rediffmail.com