Jetpack Backups don't run when an Atomic site's storage is full #81490
Labels
[Feature] Backups
The Jetpack Backup product
[Feature Group] Other Infrastructure
Miscellaneous infrastructure features and improvements on WordPress.com.
[Feature] Other Atomic Infrastructure
Anything else related to Atomic.
[Platform] Atomic
[Pri] Low
[Product] WordPress.com
All features accessible on and related to WordPress.com.
Triaged
To be used when issues have been triaged.
[Type] Bug
Quick summary
When an Atomic site has maxed out its storage, backups do not run. Apparently, when Jetpack tries to upload the helper script (the thing that fetches data from the site), it is unable to because there is no more space for it, thus the backup cannot run.
Could we perhaps adjust the storage to leave enough storage to upload the helper script?
Related Slack Conversation - p1693970297136969-slack-C03TY6J1A
Related Documentation Update Request - 84-gh-Automattic/reactor
Steps to reproduce
What you expected to happen
I would expect that our backups would still run even with storage maxed out.
What actually happened
Storage gets maxed out and there is no error message on the user's end indicating that backups are not happening because of a storage issue.
Impact
Some (< 50%)
Available workarounds?
Yes, easy to implement
Platform (Simple and/or Atomic)
Atomic
Logs or notes
No response
The text was updated successfully, but these errors were encountered: