Hello,
I an running 25 cameras on Blue Iris 5 in a system with a dedicated 20TB storage for Blue Iris. Is there a way to have database only for last 30 days despite having older files ?
I want Blue Iris to store the files older than 30 days and manage that folder to delete the files when there is no more storage but not to include this folder of older files in the database.
Is there a way to have database only for last 30 days despite having older files ?
Re: Is there a way to have database only for last 30 days despite having older files ?
My first thought would be to export them as Mp4. I think that would do it. Does anybody have a better idea ?
Forum Moderator.
Problem ? Ask and we will try to assist, but please check the Help file.
Problem ? Ask and we will try to assist, but please check the Help file.
Re: Is there a way to have database only for last 30 days despite having older files ?
TimG,
I agree exporting them sounds like a good solution, even if they are left in BVR format, BI would no longer see them and would not have them in the DB, but they could still be viewed from the BI PC by opening the file from windows explorer.
I agree exporting them sounds like a good solution, even if they are left in BVR format, BI would no longer see them and would not have them in the DB, but they could still be viewed from the BI PC by opening the file from windows explorer.
Re: Is there a way to have database only for last 30 days despite having older files ?
I think that one can set up an automatic Move from New to Stored or AUX1, and leave that AUX1 as an "unmanaged" option (or have them expire after a year or something). That would not remove them from the database though. However, if one was to use another utility to move them (a chron job or a sync software) elsewhere, then BI should probably lose track of them when it rebuilds the DB.
That said, the OP didn't say why he wants to do that. Is the DB getting too big and slow? My DB is over a month long and is only 1Gb in size, and is lightning fast. A senior software engineer at work told me "don't try to over-optimize". So I listen to him and only try to change things if something isn't working.
That said, the OP didn't say why he wants to do that. Is the DB getting too big and slow? My DB is over a month long and is only 1Gb in size, and is lightning fast. A senior software engineer at work told me "don't try to over-optimize". So I listen to him and only try to change things if something isn't working.