Ipswitch WhatsUp Gold User Guide - Ipswitch Documentation Server

Ipswitch WhatsUp Gold User Guide
Regularly purging database tables can improve performance of Flow Monitor.
Important: Purged data cannot be recovered. Make sure that you export and save any Flow
data you need for your records.
Stopping the Ipswitch Flow Collector service
To perform any of the purge actions listed in this dialog, you must first stop the Flow
Collector service.
Click Stop service to stop the collector while you perform database maintenance.
Selecting items to purge
When the Ipswitch Flow Collector service has been stopped, you can select the Flow Monitor
database tables you want to purge.
Purge the log table. Select this option to purge the log table. The log table holds
messages generated by Flow Monitor about the status of Flow Monitor, as well as
errors and warnings that have occurred during operations.
Purge temporary tables. Select this option to purge host update and flush tables.
These tables temporarily hold data during the configuration and flushing of
configuration data.
Purge the Data table. Select this option to purge flow data. This table holds flow
data gathered from the NetFlow exporter on the Flow Monitor source, this
information includes source and destination IP addresses, with traffic values in
number of flows, packets and bytes.
Purge the Host table. Select this option to purge host data. This table holds
information on hosts discovered during the processing of flow information, and
successfully resolved using DNS.
Purge the Interface table. Select this option to purge interface traffic data. This
table holds information about interface traffic, including traffic values in number of
flows, packets and bytes.
Purge NBAR tables. Select this option to purge NBAR information gathered by Flow
Monitor. These tables hold information gathered using NBAR, including application
identification as well as traffic values in number of packets and bytes.
Purge CBoS tables. Select this option to purge CBoS information. These tables hold
information defining class maps as well as information about the effectiveness of
policies based on the defined classes. The effectiveness of the policy is measured by
comparing the traffic values in packets, bytes and bit-rate prior to the application of
the policy with the traffic values after the application of the policy.
Purge flows with unclassified ports. Select this option to purge flows with
unclassified ports from the Data table. Ports are classified by mapping the port to an
application.
1033