Resizing Traditional Volumes, Netware 5.1

[gillis]

Hi,

Hindsight says my SYS volume is way too small. There are a couple of programs I can remove from it; however it still should be larger. I have 4 other partitions created as separate volumes, each with plenty of extra space. Is there a way to reallocate some of this space from one existing volume to increase the SYS vol. size. If so, can it be done on the fly or with everyone off the network? (probably a dumb question!)

I tried NWCONFIG / Disk Options / Modify Disk Partitions / Create Netware Disk Partition but received the message "Four partitions are already on this drive" and it wouldn't let me continue.

Thanks, jgiles

 

[TheLad]

You cannot decrease the size of an existing volume easily without deleting and recreating it (backing up and restoring as well of course!) unless you use a program like ServerMagic (similar to Partition Magic).

And no, this cannot be done on the fly. If you had unallocated diskspace, you could add this to SYS on the fly, but you are talking about resizing partitions -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[gillis]

Thanks for your response - actually I have some money in the budget to purchase additional disk space. So do I understand that I could then allocate some of that to the SYS volume?

jg

 

[TheLad]

You could allocate some of the new diskspace to SYS if you wanted to. It does no harm to have your SYS volume spanning over two logical volumes (or whatever config you have), it just means that you have to have the resiliency there on your second set of disks (RAID5, mirroring etc..) so that if a disk fails it does not take the whole server with it.

Just remember, once allocated you cannot remove it without deleting the volume. I usually recommend a SYS volume no smaller than 3Gb but it depends on the size of your NDS etc... -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[gillis]

Once again, I appreciate the response. It sounds like the SYS volume isn't necessarily too small (it is 3 Gb); unfortunately, our vendor installed Groupwise there (2.3Gb)so as my userbase grows (and people save emails), the SYS volume shrinks. Do you think reinstalling Groupwise on another volume is feasible or too complicated to consider?

Thanks again.

jgiles

 

[Breezeman]

No need to reinstall Groupwise. I had same situation as I inherited a system that had Grpwise on Sys. Copy the entire Grpwise directory to a separate volume/disk (perhaps one you just bought) and redirect the pointers in the poa mta (and any other ncf's that are pointing to current location) config files to the new location

 

[gillis]

Hard to believe it could be that simple The only reference I see in the Autoexec.ncf file is GRPWISE.ncf which contains two command lines:
Load sys:\system\gwpoa "po name".poa
and
Load sys:\system\gwmta "@domain.mt1

I'm afraid this confuses me since the Groupwise directory is SYS:\Grpwise ; however, the above commands are in the System directory and don't seem to give pointers to anything in the GRPWISE directory.

Sorry - but I admit to being a greenhorn in this territory.

jg

 

[LyallJ]

Maybe that it is just my system, but I am not able to delete or move any groupwise componets. I will try to move some or remove some and all looks good, bu then GroupWise puts it back!! One thing you can try, because I have run into the same problem, is have your clients archive the email to a CD or there HD. Or maybe one thing that I just thought of is to get a second drive, set up "home directorys" for your clients, and have them archive there emails to that directory. Not sure if that would work, but I think that I might try it. But just be warned, that in groupwise they are compressed. 10 mb of space in the user for groupwise would equal about 75mb of space archived. You can look in the path "yourservername\sys\grpwise\gwpo\ofuser" This is the compressed accounts. To find out who's is who's look at your NDS for the groupwise ID. It will be 3 letters/numbers. IE "I90", and on your server it would be "userI90.db". Then you could tell the client that they need to clean out there emails. Hope this helps.

 

[GaryBlake]

JG

The .poa and .mt1 file are configuration files used by GroupWise when the agents load. If you edit these you will find a string similar to this:

/home-\\ServerName\Sys\GRPWise

Once you have changed these config files you will also need to change the NWAdmin objects to point to the new locations also, once this is done you can reload the agents.

If you want to discuss further or require further help let me know.