What is best use of additional disk on Netware 5.1 Server 1

[gillis]

We are currently running a Netware 5.1 LAN with a single 18Gb hard disk divided into a SYS and 4 other volumes. The SYS volume is approx. 85% full. Other 4 are in good shape.

I've purchased two additional 18Gb drives to be delivered soon and am contemplating what is the best use of these disks? My only contingency right now is a daily tape backup.

Is mirroring one of the new disks with the existing one to gain some redundancy the best use of resources or is there a better option to consider? What are the ramifications of spreading a volume across 2 or more drives in order to gain some breathing room in the SYS volume?

Any suggestions or comments would be welcomed and greatly appreciated.

Thank you,
JGILES

 

[salserocito]

If you could also purchase a RAID Controller, you would be better off configuring all 3 drives in a RAID5 array. Out of the 3 18Gb drives, you would have 36Gb of usable space and completely fault tolerant. If one of the drives does happen to fail, the other two will continue to fuction without loss of data.

I do not recommend spanning a volume across multiple drives. If one of those drives fail, the entire volume is lost.

Yes, you could mirror 2 of the drives and leave one on its own, and yes, that would make THOSE drives fault tolerant, but leaves the other drive without anything to fall back on.

Spend the extra money to get the RAID5 Controller, or only configure 2 mirrored drives in your Server. Leave the 3rd drive as a spare... just in case!

Good luck!

 

[gillis]

Thanks 'salserocito'

After giving this some thought and making some calls, I've decided to follow your suggestion and purchase a RAID5 controller AND purchase a fourth drive. I'm going to use 3 of the drives to setup a RAID5 environment and use the 4th as a "hot spare". That certainly has to be better than my current situation (one drive, period!)

Thanks again, JGILES

 

[TheLad]

You could always maximise your diskspace by RAID 5 all 4 drives? If one fails the system runs in interim mode until the failed disk is replaced. Then the data restripes.

The only reason you would want a hot spare in a 4 disk config is to be extra careful. With a hot spare, two of the three live disks could fail and it would still work. You might as well RAID 5 all disks otherwise you will only get 36Gb. All four raided would give you .... er .... 54Gb approx. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[gillis]

As you so eloquently said it, "It's true...."

Thanks for the input. I'm getting a crash course in RAID and want to get the most out of our available resources.

While I'm thinking of it - the server manufacturer (Gateway) suggested I might need to reinstall Netware to accomplish this. They're incorrect, aren't they? Will the RAID controller have software allowing setup so the additional drives will be recognized? I assume they will need to be low-level formatted; is there something else I'm missing?

Thanks again,

jg

 

[salserocito]

Basically, yes, in not so many words, they kinda do have to be low-level formatted, but that will done with the RAID utilities. So any data that is currently on those drives will be erased!!!!

There is a DSMAINT procedure that you can go through when dealing with Hardware related upgrades. It will essentially suck NDS off of the Server and allow you to restore the NDS info after you have upgraded your hardware... Granted, the Server MUST have the same File Server Name and Internal NetWork Number (Server ID).

Be prepared and make sure that you have a full and complete backup prior to beginning this task!

I would be happy to forward to you the DSMAINT hardware upgrade procedures if you would like them. Just let me know!

Good Luck!

 

[TheLad]

I also agree with rebuilding the server in this instance. You can get utilities such as Server Magic, but in order to start afresh I would go for the rebuild. If you were to use Server Magic, you would have to extend the NetWare partition and any existing volumes you wished to be made bigger. Probably better (for the server and you - extra experience in building a server from scratch) to rebuild.

Get the DSMAINT procedures from salserocito and go for it. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[gillis]

salserocito

If you don't mind I would appreciate your offer of forwarding the DSMAINT procedures. Is this what TheLad is referring to as "rebuilding the server"?

Basically, our Netware LAN is housed on one 18Gb drive. When all is said & done, I want to 1) gain some drive space, 2) build in some redundancy and 3) increase the size of each volume. Is what you're suggesting going to do that for me?

Thanks again for the help,

JG

 

[salserocito]

Let me know where you would like me to send it.... or... actually, why don't I just write it up as a FAQ and post it here!

You should see it tomorrow!

 

[salserocito]

Here ya go!!! Hope this helps! Let me know if you have any questions.

Good Luck!



Server Hardware Upgrade Procedures

1. Perform a COMPLETE BACKUP of the entire Server (ALL VOLUMES).

2. Record the exact Server name and Internal IPX Network Address from the OLD Server.

3. Make a hard copy (printout) AND a soft copy (on diskette) of the STARTUP.NCF and AUTOEXEC.NCF files.

4. Load DSMAINT.NLM and run "Prepare NDS for Hardware Upgrade" which creates a file in the SYS:\SYSTEM directory called BACKUP.DS.

5. Once the BACKUP.DS file has been created, run “Restore NDS after Hardware Upgrade”. This will restore your DS database to the Server so you can perform the next step.

6. Copy the BACKUP.DS file from the SYS:SYSTEM directory to the hard disk of a connected workstation.

7. From DSMAINT, run “Prepare NDS for Hardware Upgrade” for a second time. This will disable the NDS database on this Server.

8. Down the Server and proceed to Step 9.

Begin fresh installation of NetWare

9. MAKE SURE THE NEW SERVER IS DETACHED FROM THE PRODUCTION NETWORK AND IT IS CONNECTED TO AN ISOLATED HUB!

10. Install NetWare v4.11 on the new Server.

11. VERY IMPORTANT!!!! - When the Installation asks, make sure to use the same exact Server Name and Internal IPX network Address as the old Server.

12. During the NDS portion of the IntraNetWare installation, create the Server in a new "temporary" NDS TREE. Creating the Server in a new tree will allow you to build the new Server with the same ServerName and IPX Internal Net Number without stepping on the existing Server in the NDS Tree with the same ServerName and IPX Internal Network Number.

13. Once the new Server installation has been completed, logon to the New NetWare Server as ADMIN, using the workstation that has the BACKUP.NDS file on it.

14. Copy the BACKUP.NDS file to the SYS:SYSTEM directory of the new server.

15. Using INSTALL.NLM, select DIRECTORY OPTIONS / “Remove Directory Services from the new server”.

16. Once Directory Services has been removed, physically attach the new Server to the production network.

17. Power up the new server without any NDS.

18. Load DSMAINT.NLM on the new server. Select and run, “Restore NDS following hardware upgrade”.

19. Restore all Volume data that was backed up in STEP#1. You can either re-install your Backup Application on the New Server, or run it from another server on the LAN.

20. Make sure that TSANDS.NLM and TSA410.NLM are loaded on the new Server

21. Verify the STARTUP.NCF and AUTOEXEC.NCF. Make modifications if necessary.

22. Hardware upgrade is completed!

23. It is recommended that you re-install the latest NetWare v4.11 Support Pack

 

[gillis]

Thanks, salse... I appreciate this greatly. At a Novell security seminar yesterday I was introduced to a potential partner for us to work with; however, they are at a distance so I need to learn how to deal with this stuff myself.

Thanks again,

jg

 

[TheLad]

salserocito - might be worth putting your last post as an FAQ if you haven't already! -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[resimpson]

In a School system we support I saw my first server to loose 2 out of 3 drives causing complete loss of data except what was on tape.

Luckily the tape was good but I would not completely discount the use of a hot swap or other near line backup solution.

Look at how much space has been used over a certain amount of time and you can possibly estimate your usage over the next X number of years with a percentage for business growth. Ask yourself whether this server will be replaced before you use up all that hard disk space.

My 2 cents...B-)

Robert Simpson
Network Engineer
Virtucom Inc.

 

[TheLad]

I think that is really an extreme circumstance that proves that having a good backup of your system is vital. Depending on how many disks you want (or how many the server can take) should really depend on the type of RAID configuration you go for.

There is no right or wrong way here, apart from making sure your backups are decent of course -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------