Free up disk space on Messaging Gateway appliances

book

Article ID: 177979

calendar_today

Updated On:

Products

Messaging Gateway

Issue/Introduction

Symantec Messaging Gateway (SMG) sends alerts indicating that available disk space is below configured thresholds or that operations like backups or diagnostic collection are failing with an error indicating that there is not enough free disk space to complete the operation.



 

Cause

Depending on configuration of reporting, logging and quarantine options, SMG may exhaust available disk space.

Resolution

Messaging Gateway is unlikely to exhaust available disk space under the default configuration but selecting some policy actions such as quarantining messages or maintaining audit logs for extended periods may require periodic administrator action to ensure that disk space is not exhausted.

Control Center role

  • Quarantined messages
    • Regularly delete old messages from the quarantine in Spam > Email Spam.
    • This can be automated by going to Spam > Quarantine settings. Under the “Spam Quarantine Expunger” heading, set some thresholds and ensure that messages are expunged regularly.
  • Compliance incidents
    • Regularly delete old incidents from the incident folders in Content > Incident Management.
    • You can keep a record of your incidents by exporting them with the “Export Incident History” button
  • Reporting data
    • You can manually delete reporting data in Administration > Reports, and click on “Delete Data Now”.
    • The Brightmail Gateway is set to expunge reporting data older than 7 days. You can adjust this to your needs.
  • Logging
    • You can manually clear all scanner logs from the log database by going to Status > Logs and clicking on “Clear All Scanner Logs”
    • The Brightmail Gateway is configured to expunge the log database once logs are 7 days or older and have a default maximum log size of 50MB. You can adjust this in Administration > Logs
     
    NOTE: Message Audit Logs are stored separately on each scanner, make sure you backup and clear the logs on each scanner on your deployment.
  • Database backups
    • You can download or delete old backups in Administration > Version > Restore/Download
    • Message Audit Logs:
    • You can backup the Message Audit Logs from each scanner to a remote server using the admin CLI command "mallog". The command supports scp/ftp to backup and scp/ftp and http to restore.
    • You can manually clear all Message Audit Logs from the scanners by using the 'delete mallogs' admin CLI command
       
  • Reporting data:
    • You can manually delete reporting data in Administration > Reports, and click on “Delete Data Now”.
    • The Brightmail Gateway is set to expunge reporting data older than 7 days. You can adjust this to your needs.


Scanner role

  • Core files are useful when troubleshooting a crash, but take up a lot of space and should be deleted when not in use.
    • Log in to the command-line interface with the admin account
    • Run “delete cores"
  • Log files are separate from the log database on the control center.
    • Log in to the command-line interface with the admin account
    • Run “delete scannerlogs” to remove all such logs
    • See “help delete” for more information on clearing specific log files


All appliance types

  • Old software update cache
    • Log in to the command line interface
    • Run "delete sudata"
  • List the largest files on the system available to be deleted (Warning: This can result in loss of data. Be aware of the function related to files that are deleted)
    • Run "list -t" to display files available to delete sorted by size.
    • Run "delete file <path and filename displayed in the list -t command>"