My LEM produces a DB backup file of approximately 1GB daily.
Do I need to retain all of these to insure I have data in the event that I get a request for information from any date in the past?
Lem retains all data until the disk is nearly full then starts deleting the oldest records, so unless you need to maintain an archive that goes back farther than what you can fit on the disk (maxes at 2 TB) these backups aren't necessary for the purposes of looking at past data.
Now for good practices you should be regularly backing up and archiving the appliance (and by extension it's db) using the same methods that you use for all your other VM's.
I feel like those automatic daily backups of the LEM db are pretty much just a holdover from the days back before LEM became a virtualized appliance.
If you are already maxing out the 2 TB and still want to retain old records for longer then having these incremental backups is probably handy but I feel like that might be an edge case.
To clarify mesverrum's answer, what they are talking about is the archiveconfig settings which have to do with backing up the data in the database.
The files that appear in your screenshot are the backupconfig files which back up only the settings such as users, rules, groups, etc and NOT the data.
Similarly to his answer, it depends on how far back you want this data. If you want to have a daily backup of your configuration for a month you can delete older files without issue, but you won't have those backups any longer.
You may decide that keeping the configs to a weekly backup makes more sense for you, but you run the risk of not having a backup for settings you may wish to revert to in the future.
Each of these one GB files represents the LEM configuration as it was on that particular day.
Good to know, I hadn't seen them in so long I couldn't remember which naming convention applied to which backup file.