# Backup less frequently used data

**URL:** <https://forum.mautic.org/t/backup-less-frequently-used-data/21728>\
**Category:** General Discussion\
**Created:** [November 23, 2021, 4:38am UTC](https://forum.mautic.org/t/backup-less-frequently-used-data/21728 "2021-11-23T04:38:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mzagmajster](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/mzagmajster/32/687_2.png) [@mzagmajster](https://forum.mautic.org/u/mzagmajster)\
**Post date:** [November 23, 2021, 4:38am UTC](https://forum.mautic.org/t/backup-less-frequently-used-data/21728/1 "2021-11-23T04:38:21Z")

</div>

Hi,

Some tables in Mautic over time get quite large as a result sooner or later you have to deal with fine-tunning your Mautic instance. Some tables that will only get bigger and bigger over time: page\_hits, email\_stats, audit\_log, etc.

Since I do not want to lose old data I wonder if there is a way to cleanup mautic instance so that data is only moved to old table which would not be used during regular requests unless explicitly requested by user.

So for example I would like to be able to move page\_hits older then 12 months to old\_page\_hits table. Data in old table would only be used/accessed if user specifically requested he wanted to include data from old table.

Each table in Mautic would have exactly the same table with prefix old\_. That way we can move data to old table when we do not want to use it as much anymore. It would keep instance nice and tidy and marketers should have better experience using the platform.

For rare occasions… lets say we want to email something to a lead that has been inactive for the past two years we would access old\_ tables but otherwise stick with “current” size regulated tables.

Questions:

1. Would the above proposal be possible to incorporate in Mautic?

2. Do you have any other suggestions/approach on how to deal with the big database tables over time (besides hardware/server scale)?