It looks like your MARS box is storing about 6 months worth of data on the box itself. If you need to store data longer you can configure an archive location, which will also give you configuration backups. The process of pulling logs from an archive is a bit tricky and can involve using a second box, there is information on it in the setup guide.
You cannot know this information from the MARS commands (as in when the box will reach full capaciity). The output you have posted mentions when the 'current' partition will fill up. The 'diskusage' command can give you the overall usage (for all partitions). The 'u02' is the partition stroring the events 'data' AFAIK.
There is no way to extend the capacity of MARS, you can just archive the data to a NFS server or use a stronger appliance (or multiple appliances).
The following is more detail about the partitions as mentioned in the user guide:
"Displays amount of disk space available on all partitions in the MARS Appliance
For all MARS Appliance models, the Oracle database has three partitions:
â¢/u01: Stores the Oracle binary files.
â¢/u02: Stores the data files.
â¢/u03: Stores the replay log files, which are cached, in-memory working files not yet committed to the data store.
If any of these partitions reaches 99% capacity, the Oracle database will experience operational issues.
The size of the data partition (/u02) varies based on the model: "
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...