After rebuilding my system due to the SSD failing (the SSD controller possibly failed from getting too warm causing it to not be seen by the system), I attempted to use the rebuilt system with the bi db on the d drive (a 3 TB WD purple drive where the bi recordings are stored and is also in the same local computer), I discovered that my recordings were no longer being archived and deleted once the set size limits were reached (no deleted or file moving logs either). This caused the drive to run out of space before I realized that there was an issue. Once I moved the db back to the c drive (the SSD drive where only the OS, apps, & now BI db are located) everything started to work as it should again. It's possible that my attempts to refresh / rebuild the db just didn't work for some reason before moving the db back to the primary drive, but the system undoubtedly performs better if the db is kept on the SSD as opposed to the spinning (local) hd.
Has anyone else had similar issues when moving the db to a secondary but still local drive?
I did some forum browsing / reading and found others with similar issues after moving the storage locations and not rebuilding the db afterwards. I did attempt to do this but for some reason all it did at the time was purge the db and did not complete a scan and rebuild. Once I moved the db back to the c: drive and then selected repair db it worked like it should and resumed normal archiving / deleting space management behaviors...
When reading the documentation, I noticed that it mentions keeping the db on a local fast drive so I didn't initially foresee a potential issue. My mindset of moving the db to the (still local) d drive was that I could set it to also synchronize with my Onedrive folders so it could also be backed up in the case of a lost drive, but since the db can be easily rebuilt and with files in use being locked, they would also be limited to successful syncs if constantly being in use. I limited my clips files to 1 hr to help reduce the potential issue of files only syncing or archiving once they are closed and unlocked.
Has anyone else had similar issues when moving the db to a secondary but still local drive?
I did some forum browsing / reading and found others with similar issues after moving the storage locations and not rebuilding the db afterwards. I did attempt to do this but for some reason all it did at the time was purge the db and did not complete a scan and rebuild. Once I moved the db back to the c: drive and then selected repair db it worked like it should and resumed normal archiving / deleting space management behaviors...
When reading the documentation, I noticed that it mentions keeping the db on a local fast drive so I didn't initially foresee a potential issue. My mindset of moving the db to the (still local) d drive was that I could set it to also synchronize with my Onedrive folders so it could also be backed up in the case of a lost drive, but since the db can be easily rebuilt and with files in use being locked, they would also be limited to successful syncs if constantly being in use. I limited my clips files to 1 hr to help reduce the potential issue of files only syncing or archiving once they are closed and unlocked.
Last edited: