Can I set archkeep to more than 360 in my config?

Technical Support
1

I just realized that my Shake has only been retaining 7 days of data :face_with_head_bandage: all this time:

myshake@rubus-quasso:/opt $ du -sh /opt/data/archive/202?
20K	/opt/data/archive/2024
20K	/opt/data/archive/2025
333M	/opt/data/archive/2026

I have a 256GB drive mounted on /opt/data/archive and so despite the dire warning of https://manual.raspberryshake.org/download.html#general-comments which I suspect might be behind the UI’s maximum limit of 360 day retention, my estimates imply I should be able to store well over a decade of data on my drive (perhaps about 229 / (.333 * 52) = 13.225 years).

I’ll try restore or at least get a copy of my historical data following the instructions at https://manual.raspberryshake.org/fdsn.html#fdsnwebservices but I’m wondering if going forward I can bypass the 360 day limit by editing the other.archkeep value directly in the /opt/settings/config/config.json file rather than via the web UI?

2

Hello natevw,

Thanks for notifying us about this. We’ll be looking into it on our end.

In the meantime, you’re welcome to experiment. Editing other.archkeep directly in /opt/settings/config/config.json is a reasonable thing to try, and your storage math looks sound for a 256 GB drive. A few practical notes if you go down that path:

  • Back up config.json before editing, and make your changes while the Shake services are stopped (or restart them afterwards) so your value isn’t overwritten by the running process.
  • The 360-day cap in the UI exists due to a tested/supported range rather than a hard technical limit, so going beyond it is uncharted territory. Better keep an eye on overall system behavior and any log warnings over the days that follow your work.
  • FDSN queries over very long windows can get slow or time out, so you may want to chunk your historical pulls. You can find all details on our FDSNWS page.

If you do try it, let us know how it goes!

1 Like