# Discourse-health-check: one-shot CLI overview of your Discourse server

**URL:** https://meta.discourse.org/t/discourse-health-check-one-shot-cli-overview-of-your-discourse-server/404458
**Category:** Extras
**Tags:** performance, server-resources, hosting
**Created:** [3 juni 2026 om 18:57 UTC](https://meta.discourse.org/t/discourse-health-check-one-shot-cli-overview-of-your-discourse-server/404458 "2026-06-03T18:57:33Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [4 juni 2026 om 05:36 UTC](https://meta.discourse.org/t/discourse-health-check-one-shot-cli-overview-of-your-discourse-server/404458/5 "2026-06-04T05:36:30Z")

</div>

Nice offering, thanks!

For backups, I’d suggest checking the latest backup to see if it has been read since it was written. That’s a proxy, for checking if it has been copied offsite. (Or, if not checking the latest, perhaps check all.)

If no backup has been copied offsite for a week, that’s worth warning about.

(I think you can subtract `stat -c %Y` from `stat -c %X` or perhaps just compare them. They will be different if the backup file has been read since it was written.)

---

_[View the full topic](https://meta.discourse.org/t/discourse-health-check-one-shot-cli-overview-of-your-discourse-server/404458)._
