Cleaning Up Logs Parent topic

  1. Set the log backup destination by executing one of the following commands.
    • admin log config backup ftp [host] [user] [password] [path]
    • admin log config backup local
    • admin log config backup smb [host] [user] [password] [path]
    Command Parameters
    • Host: If FTP or SMB, type the server FTP IP address or SMB IP address.
    • User: Type the user name. For a domain account, type '/' instead of '\' (such as trend/test).
    • Password: If there is no password, type "none" (case sensitive).
    • Path: If FTP or SMB, type the relative path on the FTP or SMB/SAMBA server. DLP does not support the following special characters: ~`!* and white space.
    Note
    Note
    When the backup destination is the FTP server, and the FTP backup destination does not exist, DLP backs up the logs to the root folder on the FTP server.
    If DLP cannot access the FTP and SMB servers, DLP backs up files to the local directory at /backup/violationlogs.
  2. Purge logs or set the schedule for purging logs by executing one of the following commands:
    CLI commands for cleaning up incident logs and forensic data
    • admin log config schedule [none/ day mon week]
      Sets the schedule for automatically running the log purge.
    • admin log config purge [days]
      Sets the maximum number of days to save the backup incident logs after a purge. Valid values are 0 to 180. After exceeding the time limit, the logs are cleaned up. This parameter must be an integer. If set to 0, all incident logs in the database are deleted.
    • admin log purge
      Immediately purges incident logs in the database. The time it takes to purge log files depends on the number of log files to purge. The purge is not finished until the command prompt returns. You must wait until the purge is complete.