# Alarms.data file is too fat

**URL:** <https://forum.inductiveautomation.com/t/alarms-data-file-is-too-fat/12711>\
**Category:** Ignition\
**Created:** [February 24, 2017, 8:17am UTC](https://forum.inductiveautomation.com/t/alarms-data-file-is-too-fat/12711 "2017-02-24T08:17:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![uborzz](https://avatars.discourse-cdn.com/v4/letter/u/58956e/32.png) [@uborzz](https://forum.inductiveautomation.com/u/uborzz)\
**Post date:** [February 24, 2017, 8:17am UTC](https://forum.inductiveautomation.com/t/alarms-data-file-is-too-fat/12711/1 "2017-02-24T08:17:38Z")

</div>

Hi all!

I have an issue with the Alarms.data file in the installation directory in Ignition/data/datacache/Alarms.

It doesn’t stop growing (about 42GB at this moment).

What can I do to stop it getting bigger?

Thanks!

---

<div class="post-metadata">

**Author:** ![adam.morales](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/adam.morales/32/3405_2.png) [@adam.morales](https://forum.inductiveautomation.com/u/adam.morales)\
**Post date:** [March 2, 2017, 6:12pm UTC](https://forum.inductiveautomation.com/t/alarms-data-file-is-too-fat/12711/2 "2017-03-02T18:12:30Z")

</div>

I believe that this file would contain the Store and Forward cache for a datasource called Alarms. Do you have a database connection configured in Ignition called Alarms with store and forward information viewable on the gateway web page under Status \> Store and Forward? If so, how many items are in the cache, and is the database connection faulted?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 3, 2017, 6:58pm UTC](https://forum.inductiveautomation.com/t/alarms-data-file-is-too-fat/12711/3 "2017-03-03T18:58:32Z")

</div>

Also, it’s occasionally possible for this store and forward cache to get corrupted. If you disable the cache on the datasource (Configure -\> Databases -\> Store and Forward -\> Alarms -\> Disk Cache Enabled), then remove/rename the /Alarms folder in the datacache directory, then set disk cache back to enabled, it will generate a new cache file that shouldn’t be subject to these issues. Note that if you have any quarantined/cached records they will be deleted or inaccessible after you do this.