I have set my Blue Iris machine up according to these posts:
@SouthernYankee's Standard Allocation Post
@SouthernYankee's post in the thread Blue Iris settings issue
Like this - (where D: is dedicated to Blue Iris):
In my past life of setting up servers & client machines I typically set them up like the following (unless the application was written so that there was not a way to move application data (log files, internal db, application temp files, disk space utilization, etc.)).
This was done for various reasons (Backup, performance, separation of usage, disk space utilization, etc.)
So is there a reason not to install this drive as the D: drive and move the BI db to this drive along with the OS paging and OS temporary files directories?
Thanks,
Eric
@SouthernYankee's Standard Allocation Post
@SouthernYankee's post in the thread Blue Iris settings issue
Like this - (where D: is dedicated to Blue Iris):
c:\BlueIris\db
D:\BlueIris\New
D:\BlueIris\Stored
D:\BlueIris\Alerts
In my past life of setting up servers & client machines I typically set them up like the following (unless the application was written so that there was not a way to move application data (log files, internal db, application temp files, disk space utilization, etc.)).
This was done for various reasons (Backup, performance, separation of usage, disk space utilization, etc.)
- Boot Drive (SSD or NVME drive):
- OS/Application Executables
- 2nd Drive (SSD or Fast hard disk):
- Application Data (log files, internal db, application temp files, etc.):
- OS Paging file
- OS Temporary Files directory
- 3rd Drive (Large hard disk):
- User Data
I was going through my "old hardware box" and found an older 256gb SSD drive (Samsung SSD 840 Series).So is there a reason not to install this drive as the D: drive and move the BI db to this drive along with the OS paging and OS temporary files directories?
Thanks,
Eric