Backup retention policy
Answered
As I am moving my system, I find the storage and backup retention management lacking.
Something like Milestone offers, just the basics, write data to fast storage, copy to archive storage, read data from local or archive storage, independent retention on archive and local storage.
Note the difference in term between backup and archive, I don't need a backup of the data, I need fast write storage and long term read storage.
Use case:
Recording requires fast write storage, fast storage is expensive, long term retention is not feasible on expensive storage.
Archive storage is is used for playback, linear read access, can be slower, can use big and resilient and cheap.
Problem:
The local and backup storage shares the same retention policy.
My archive storage is petabytes, my local storage is terabytes.
I can only retain as much as the local storage allows.
I am overspending on local storage because I need to retain video for a long time period.
Backup is only useful as disaster recovery, and for aggregating from multiple servers, it is not useful as an archive for long term video storage.
Proposal:
Abandon the backup term, introduce an archive term.
Allow me to set retention policies independently for local and archive storage.
I am not personally a fan of having retention configured in the cameras, I prefer to set retention by storage, and cameras can be assigned to storage. Policy on camera groups could make it easier.
-
Hello, Pieter.
> Problem:
> The local and backup storage shares the same retention policy.If you set archive length settings to "Auto" on cameras, retention for main and backup storages will be different. Basically, each storage will try to accommodate as much archive as it can, deleting the oldest archive when there will be no room for new recordings.
Will it work for you? Or you need to have archive length setting to be configured to a some fixed value?
0 -
Not quite.
I want a time based policy for archives, else different servers that share the same archive storage will not collaborate on fair usage, and I am forced to artificially limit storage space on the archive destination else the servers will eat all storage.
0 -
Thanks for clarification.
We are working on feature which would allow to set a different retention time for bookmarks, events and motion, maybe it'll be possible to add also a general retention time to it.
0 -
Thank you, it would be great if I could set policy per storage target.
Like I said, the backup concept does not really make sense to me, maybe I misunderstand its use, but an archive storage used for playback retention, that I get. Arguably, this would ideally be a global setting, not a per server setting, which may imply it is a camera setting, and each server could have primary storage, and one archive storage location, that should be the same between servers.
0 -
Although the current implementation is very simple and less likely to have user error compared to the storage management in xprotect i agree that an option for more advanced users would be nice to have.
0 -
I would love to have the ability for local storage of both high and low rez video and then archive only High rez after a set time. For example, all cameras would store video locally (high and low rez), then after the configured time, have the high rez sent off to an archive storage and delete the low rez.
0
Please sign in to leave a comment.
Comments
6 comments