User’s Guide – version 3.5
NetFlow Tracker
75
Archiving
NetFlow Tracker can be configured to archive real-time data older than the age
configured in
Database Settings
to a nominated location rather than delete it. Archiving
is enabled for a device in
Device Settings
; the archiving settings page allows you to set
the archive location and mount archived data back into the system for reporting using
the
Filter Editor
.
You can choose to have all archives stored in the archive folder, or you can choose to
store in sub folders for each device and/or day, Please note that NetFlow Tracker
does not delete archive files so you must ensure that they are moved from the archive
directory to permanent storage.
To mount an archive, enter the directory containing it in the box under “Mount
Archives” and press “List”; you can then select archives and press “Mount”. When
there are archives mounted they appear under “Currently Mounted Archives” and can
be unmounted by selecting and pressing “Unmount”. Note that mounting and
unmounting archives does not affect the archive file itself.
Mounting an archive from a device that was deleted or was never present on the
server is not supported.
Memory Settings
NetFlow Tracker uses a small amount of memory during its normal operation. You can
control this amount by changing the values here, but it is not likely to be necessary.
Note that it is possible to prevent the software from working by setting inappropriate
values. Note also that this page is not available on Unix installations; to change the
memory settings on Unix the “start” script must be edited.
Performance Counters
The performance counters can help diagnose problems setting up NetFlow Tracker.
Counters are stored for each device the software has received data from. The
counters are kept from when the system is started; you can reset them at any time.
Average sample storage duration
This keeps track of how long it takes the system to store a one-minute sample of real-
time data. If this takes more than about fifteen seconds it is a sign that the system is
overloaded.
Last long-term database maintenance duration
This is how long it took to perform the last update of the long-term database; if this
takes more than two to three hours you may have to reduce the number of long-term
reports you have, reduce the number of devices they cover or set some of the long-
term sample sizes to zero.
Last real-time database maintenance duration
This is how long it took to perform the last reorganisation of the real-time database;
this should not take longer than thirty minutes.
