10.2.

8 Clearing the Disk Space of the M2000 Server

This describes how to clean up the disk space of the M2000 server. Before cleaning up
the disk
space, ensure that the files to be deleted are not required for future operations. Deleting
a useful
file by mistake may lead to a system operation error.

Context
During the routine operation and maintenance, back up and delete the following files to
release
more disk space:
l
l
l
l
l

Files storing information about NEs and the M2000 server

Software upgrade package and decompressed files
Trace logs
Backup files
Temporary files created during system operations

NOTICE

You can delete files when the server is running. Before deleting files, run the ls -l
command to
check the date when the files are generated. Do not delete the files generated on the
current day.

Procedure
Step 1 Export the files that store information about NEs and the M2000 server, and
back up the files
to a tape.
l Files generated during automatic alarm dump
Alarm dump files are stored in the /opt/oss/server/var/ThresholdExport/FM
directory.
M2000
l User log files
User log dump files are stored in the /opt/oss/server/var/userlogs directory.
l Core files generated by the system
Core files are stored in the /opt/oss/server/var/logs/ directory.
l Historical trace files
Historical trace files are stored in the /opt/oss/server/var/logs/tracebak/ directory.
Step 2 Delete the software update package and the decompressed files.
After the software is successfully upgraded, you can delete the original upgrade
package and
the decompressed files. The upgrade package and decompressed files are stored in the
folder
named after the patch in the /export/home directory.

NOTICE
Generally, the decompressed upgrade files are stored in the /export/home directory.
The folder
for saving the decompressed upgrade files is named after the patch. Sometimes, the
folder is
created in the /export/home/bak directory.
Step 3 Delete trace logs.
Change the value of tracebackupnum in the IMP_tracemonitor_svc_ex.xml file to
reduce the
number of backup trace log files.
Edit the IMP_tracemonitor_svc_ex.xml file in the /opt/oss/server/etc/conf/
directory to set
the interval for checking trace log files, maximum trace log file size, and maximum
number of
backup trace log files.
The following are the contents of the IMP_tracemonitor_svc_ex.xml file:
<?xml version="1.0" encoding="utf-8"?>
<tracemonitor name="tracemonitor" mount="/imap/common/tracemonitor">
<strategy name="imap">
<!-- CCB-ITEM checktracetime indicates that how long trace file will be checked!
Min value is 300 seconds! -->
<param name="checktracetime">300</param>
<!-- CCB-ITEM tracebackupnum indicates the max number of reserved trace file! -->
<param name="tracebackupnum">50</param>
</strategy>
<strategy name="other">
<filename name="tao.trace">
<param name="filesize">200</param>
<param name="tracebackupnum">20</param>
</filename>
</strategy>
</tracemonitor>

In checktracetime, you can set the interval for checking trace log files. In the
preceding example,
the system checks the trace log files every 300 seconds. In tracebackupnum, you can
set the
number of backup trace log files for each process in the
/opt/oss/server/var/logs/tracebak
directory. For a process, if the number of backup trace log files in the tracebak
directory exceeds
the preset value, the system automatically deletes the earliest trace log files.
M2000
ATAE Cluster System Administrator Guide (SUSE10) 10 Monitoring the M2000 System
Issue 08 (2014-07-10) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
207

NOTICE

Backup trace files are used for locating and analyzing problems. Reducing the value in
tracebackupnum reduces the number of backup trace files, which may make problem
location
and analysis inconvenient.

Step 4 Clear the backup files.

l After the upgrade, delete the backup files for the upgrade or copy them to a tape.
l Periodically back up all the files in the /export/home/backup/omc directory to a tape.