- You should record weekly the disk space available on the server plotting on a
graph the free disk space against the maximum capacity of the disks. Record
any reasons for major changes noted (for example, new disks added or loading
of extra applications) and input the graph to the Service Level Management
process for reporting. You could use or adapt the disk usage report provided or
look at an example disk usage report to get an idea of the information you can
collect.
- The log can be used to identify trends and action taken before lack of disk
space starts to affect network performance. The first action is to try and reduce the
amount of disk space used by:
- running disk-cleaning utilities to clear out temporary files (temporary web
browser files can be a particularly large consumer of disk space)
- removing unnecessary or infrequently used software applications
- deleting or moving personal data that has been inappropriately stored on the
server.
- The above actions need to be carried out each time disk space is running low
but eventually you will probably need to consider:
- installing extra disks
- replacing smaller disks with larger units
- installing a separate disk array to store large volumes of data.
- The person responsible for technical support in the school along with the school
leadership team should conduct an annual review of the suitability and cost
effectiveness of the network monitoring software. The weekly reports of network
performance and the output from the Problem Management process should be
inputs to this review.
If the right network monitoring software has been chosen and appropriately
configured, and the management tasks have been rigorously followed, then it
should be possible to detect a measurable improvement in network performance. If
this is not the case, the review should determine whether the correct solution has
been chosen or whether the set- up or day-to-day management of the software
could be improved.
