Per camera storage rotation on low disk space #20906
-
|
Hello, When the storage is running low, older recodings are deleted to make room for the new one, and if I understand correctly, the current behavior is this :
This behavior is a bit problematic for my usecase as some cameras aren't going to have the same amount of '' events '' as other ones, yet their older recordings might get deleted. Is it possible to avoid having B cameras recording deleted and only delete older A camera recordings ? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
You are correct about the current behavior: when storage runs low, Frigate deletes the oldest recordings system-wide, regardless of which camera they belong to. There is no built-in option to restrict deletion to only the oldest recordings from a specific camera. This means if camera A tries to record when storage is full, the oldest files—potentially from camera B—will be deleted to make space(1), (2). There is also no configuration available to set a maximum storage limit per camera or to have per-camera storage rotation. You can manually tune the retention days for each camera to balance usage, but automatic per-camera disk management is not supported(2). 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
The AI is correct here. Frigate's emergency cleanup is not configurable. The recommendation is to configure your retention settings to avoid emergency cleanup altogether, or just increase the amount of storage available to Frigate.