Secondary Disk Directory
A spinning drive is too slow for me to capture all the cameras that I have, and an NVME drive isn't big enough. I want to move the older files to a secondary drive, but I'd like to be able to review them via the SecuritySpy browser. If I move the directory and create a symlink from <main_directory>/<camera>/<date> -> <backup_directory>/<camera>/<date> will your implementation treat that as if it were local? Will that cause any issues with your old file removal algorithms?
Comments
-
This isn't explicitly supported and I can't guarantee that this will work. If the HDD is too slow for capture, then the best solution is to use one or more large SSD drives. These have come down in price a lot recently, to the extent that they are now a good solution for high-speed capture of large amounts of data.
-
Yes, this will work. I've done symlinks for a long time. Unless SS behavior has changed recently, I used to do this quite often (moving yesterday or last week's files to a remote-mounted HD, and then using symlinks to keep the files visible within SS's directory structure.)
JT
-
I can confirm that SecuritySpy uses standard file system calls, and nothing has changed recently in terms of its handling of these files.
