Novell is now a part of Micro Focus

Freeing Up Disk Space On GroupWise 5.5 Post Offices

Novell Cool Solutions: Tip
By Tay Kratzer

Digg This - Slashdot This

Posted: 23 Jun 2000

Current Version: NSBS 5

How to free up disk space used by un-needed files in a GroupWise 5.5 Post Office.

Below is a sequence of steps to take in order to free up disk space. If you find that taking a few of the steps frees up sufficient disk space then you can stop there. Or you can use the steps that are most feasible for your environment.

Note: On NetWare volumes, deleting files does not necessarily free up disk space immediately, although your volume statistics indicates that it does. NetWare places deleted files in a limbo state, just in case you want to undelete a file that you mistakenly deleted. See document # 10012765 at for more details on this point. The short lesson is this, purge your volume after deleting files to see to it that you have enough "free blocks" in order for new files to be created on your NetWare volume.

  1. Go to the PO\OFUSER directory and delete all files that do not end with a "DB" extension. It is quite possible that you will see files with a naming convention such as *.DBA or *.DBB etc. Delete these files. The *.DBA, *.DBB, etc. files are files created when a GroupWise database is rebuilt. These files are never used again. You may also see files with a ".$DB" extension, you may delete these also.

  2. Go to the PO\OFMSG directory and delete all files that do not end with a "*.DB" extension. It is quite possible that you will see files with a naming convention such as *.DBA or *.DBB etc. Delete these files. The same concepts that applied to the PO\OFUSER directory apply here also.

  3. Look in the post office\WPCSIN and WPCSOUT directories and subdirectories for old files with an "X" at the beginning of the file name. Delete these files. These "X" files are files that were in transit to the location where you found the file. For some reason the file transfer never completed. A file in the GroupWise queues that has an "X" in it will never be touched by a GroupWise process (unless of course it's the process that's creating the file). So if a file has been sitting in a queue for anything over a couple of hours, and it's got an X at the beginning of the file name, it's time to delete that file.

  4. There are other miscellaneous directories that have files that you don't need.

    Delete any files (not directories) in the PO\WPCSOUT\OFS directory. There will be things like log files, and a WPROF50.DB file. The log files, well they're just log files! You can delete the WPROF50.DB file, but it'll most likely come back. The WPROF50.DB file is the address book for remote clients.

    These files aren't doing anyone any good. Just delete them.

    Delete any files in this directory, they aren't any good.

    Delete any files in this directory

    These are where GroupWise Remote requests are stored when users do a "Hit the Road" and other GroupWise Remote functions. The requests are held in the funny named directories off of OFDIRECT. Sometimes you'll find big ole' files there. If you find a big file in one of these directories, and you determine you want to delete the file, go ahead, but make sure to delete the entire directory structure that housed this file. For example: let's say there's a directory called OFWORK\OFDIRECT\Rd7mu7na. There's a file in that "Rd7mu7na" directory. Then delete the entire directory called "Rd7mu7na", not just the file within it.

  5. Now you need to go after the big old attachment files. You don't want to just go out and start whacking files in the Post Office\OFFILES\FDXX directories. Doing this can cause irreparable errors in GWCHECK later on. The best approach is this. Choose a file size threshold, that represents something that you do not think is a reasonable size for a file in your business environment. Let's say that threshold value is 25 Megabytes. Now that you have a threshold, see TID # 2954163 for instructions on how to find who has 25 meg, or bigger files, in their mailbox:

    After you have identified the big attachment files, you can contact the appropriate end-users and ask them to delete the messages associated with these attachments. The GWCHECK report tells you enough details about the message that you can instruct your GroupWise user as to which message to delete.

  6. There's another place for a big potential gain in disk space. There's a directory off of the PO\OFUSER directory called INDEX. These files in this directory hold the indexes that are used in the GroupWise Find feature. My experience has been that there's a whole bunch of stuff in that directory that is not needed by the GroupWise system. Here's how you clean it up:

    1. On the GroupWise 5.5 POA there's a hidden keystroke. It's "Ctrl-Q". When you invoke this keystroke the GroupWise POA re-indexes the entire post office message store from scratch. This process will take A LONG TIME! WARNING: The POA could tie up the server utilization for a long time, you will most likely want to do this overnight, or on the weekend.

    2. After the QuickFinder Re-Indexing process goes on, if there are files any older then the day in which you invoked the "Ctrl-Q", delete them. They are garbage files that will never be cleaned up in any other manner.

Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions.

© Copyright Micro Focus or one of its affiliates