Common Maintenance Tasks


Backing Up

Maintaining a daily backup schedule is crucial to the security of your data.

For information about the backup software included with NetWare, see Backup and Restore.


Checking Server Error Logs

Check server error logs at least once a week, even if you don't believe there have been errors. Problems caught early are easier to solve. View the error logs with EDIT at the server console or with a text editor from a workstation. See EDIT in Utilities Reference.

When needed, NetWare creates the following error logs, the first four in sys:system:

To keep error log files from using too much disk space, modify the values of the relevant Error Handling server parameters. See SET Error Handling Parameters in Utilities Reference.


Checking Disk Drives

Once a week check the Storage Devices statistics in MONITOR to make sure that the operating status of each disk is active.

If you rarely use the diskette drive on your server, you might want to test the drive about twice a year to make sure it's running properly.


Reviewing Server Cache Statistics

For more information about monitoring and optimizing server memory, see Optimizing in Server Memory.

  1. Review file server cache statistics weekly.

    These statistics are found on the General Information screen of MONITOR.

  2. Divide the value of Total Cache Buffers by the value of Original Cache Buffers to determine the percentage of available cache.

    Ideally, file server cache should be 70% or more of the total cache.

  3. If the percentage falls below 50%, add more memory to the server.


Checking Free Space on Server Disks and Volumes

  1. Check server disks and volumes weekly to make sure they have enough free space.

    To determine the amount of free space, load MONITOR and select Volumes. The Mounted Volumes screen lists all mounted volumes, their capacity, and the percentage of the volume that is full.

    Keep at least 15% to 20% free space on any disk.

    Keep at least 20% free space on the Sys volume and at least 10% free space within other volumes. If the Sys volume fills up, your server hangs.

  2. If the free space is less than the recommended values, increase the size of the volume or remove unneeded files and directories.

You can use the VREPAIR utility to repair volumes. See VREPAIR in Utilities Reference.


Reviewing User Accounts

  1. Review all users and objects on the network once a month to make sure that there are no intruders, obsolete accounts, or unauthorized accounts.

    The network administrator should know all objects and accounts on the network.

  2. Make sure accounts are closed for all users who have left the system.


Testing the Uninterruptible Power Supply

If your network has an Uninterruptible Power Supply (UPS), check it twice a year to make sure it's running properly. Choose a time when no users are logged into the network.

  1. Down the server and exit to DOS, but do not turn off the computer,

  2. While the computer is still running, unplug it.

    If your UPS system is working properly, the computer should continue to run.

    If the server powers off, your UPS batteries are probably low or dead. Check and replace them.


Documenting the Network

It is important to document your network. Keeping records of network layout, hardware and software inventory, configuration, repairs, and backup schedules will save you time and work if you need to rebuild or replace parts of the network, justify new equipment, or restore the network after a disaster. You will need much of this information if you ever need to call Novell Technical Support. You might want to keep documentation in a three-ring binder or online in a database.

WARNING:  Whether you store your network documentation in a binder or in a database, keep multiple copies and update them regularly. Always store one or more copies offsite---along with your taped backups. Documentation does no good if it's destroyed with the network itself in a major disaster.

Information you should keep in your network documentation includes the following: