Welcome to the forum...you may have designated too much space for the storage...From the help fileI keep getting this error or some version of it: C:: 2419, 1.06G/29.63T (-27.63T). I have plenty of storage on my hard drive, over 1TB remaining. I have also verified the folder structure in the Blue Iris Folder. Can anyone help? Thank you
Great..make sure 50gb is enough to hold the data for the duration you want to save videoThank you. Reduced the amount of space "Limit Folder Size:" to 50 GB. I no longer get the "Clips Warning"
Great..make sure 50gb is enough to hold the data for the duration you want to save video
You should never be using days as a measure of storage. I don't know what the error means because you still have free space on the nas however it appears to be almost completely full. Try leaving a bit more free space on your nas and your PC drive@fenderman - Old thread but what's the recommended solution if I don't want to reduce the storage space?
My error is "\\remoteNas: 206033, 14.69T/14.89T (+4.90T)"
I have one local folder [f:] and one remote folder (NAS) for alerts and clips. I keep 30 days on local disk and then move alerts and clips to the remote NAS. I keep roughly 90 days of alerts and clips on the NAS. Should I break up the NAS folder into 60 - 90 day folders for alerts and clips? Is my issue the amount of storage or the number of files?
You should never be using days as a measure of storage. I don't know what the error means because you still have free space on the nas however it appears to be almost completely full. Try leaving a bit more free space on your nas and your PC drive
If you have an age limit it will be either or, but why delete footage that you have room to store?I'm using both a size limit and age limit. Will BI keep files past the size limit if the age limit is not met?
Is there a way to force BI to leave more of a buffer? I actually have plenty of space on the NAS and expanded the space by 1TB, still seeing the error.
In your ealrier post you mention a number of files limit, is that still an issue on 5.6.2.3?