archive storage
I want to be able to move old recordings to my NAS so that I can have recent recordings on my local fast SSD but still keep older footage available on my NAS having terabytes of spinning rust available. **Describe the solution you'd like** A way to configure an archive storage (either a different path that I mount using NFS or smb or even directly the connection parameters for frigate to use SMB client himself) + A way to configure the retention individually for main and archive storage (7 days in main storage and 90 days in archive for example) **Describe alternatives you've considered** No real idea, except running frigate twice and keeping duplicate of the "main" storage. **Additional context** Having 2 level of storage is the key here, moving data from main to archive storage can be complicated within frigate, so a first version could be to add a "cache" storage that fully duplicate the main storage but allows to setup shorter retention. This way I could set retention to 90 days on main storage and point it to a NFS mount and add a "cache" retention of 7 days in the local SSD under /tmp. This way it could be less complicated to implement: any recording in the db is available in main storage (NFS) if it was not found in the "cache" (SSD or /tmp)
Posted by toxic0berliner on Aug 18, 2022, 5:57 PM
Tags
Related issues
- I just invented a simple upgrade script for my father's ancient Fedora install.
- Weekly limit is draining like the old 5-hour limit
- Rather people unable to setup a static websites where needed.
- Besides the general awfulness of Windows that you describe, have you looked at C:\Windows recently?
- Does your work involves using teams or ms office or docker?
- Meta: Sorry, no response was returned
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
onboarding (Other)
I just invented a simple upgrade script for my father's ancient Fedora install.
Weekly limit is draining like the old 5-hour limit
Rather people unable to setup a static websites where needed.
Besides the general awfulness of Windows that you describe, have you looked at C:\Windows recently?
Does your work involves using teams or ms office or docker?
Meta: Sorry, no response was returned
Recent FrankerFaceZ Issues with Firefox
Allow creating a `python` shim on `python install`
archive storage
I want to be able to move old recordings to my NAS so that I can have recent recordings on my local fast SSD but still keep older footage available on my NAS having terabytes of spinning rust available. **Describe the solution you'd like** A way to configure an archive storage (either a different path that I mount using NFS or smb or even directly the connection parameters for frigate to use SMB client himself) + A way to configure the retention individually for main and archive storage (7 days in main storage and 90 days in archive for example) **Describe alternatives you've considered** No real idea, except running frigate twice and keeping duplicate of the "main" storage. **Additional context** Having 2 level of storage is the key here, moving data from main to archive storage can be complicated within frigate, so a first version could be to add a "cache" storage that fully duplicate the main storage but allows to setup shorter retention. This way I could set retention to 90 days on main storage and point it to a NFS mount and add a "cache" retention of 7 days in the local SSD under /tmp. This way it could be less complicated to implement: any recording in the db is available in main storage (NFS) if it was not found in the "cache" (SSD or /tmp)
Comments (0)
No comments yet. Start the discussion.