2.6 update provides resolution or major part of recurring "HDD/SSD slow errors".
But there are still possible options that such notifications will be received after the upgrade:
- Hardware performance doesn't face the load
- Storage database is corrupted which might slow down the system workflow
Note! Point 2 should be resolved according to guide from separate "Storage database corruption" article
In common Server-Storage drive workflow might be split into two processes:
- Writing/Removing media data received from cameras
- Storage database update
There's nothing could be done with writing/removing media data since it's just necessary to keep the archive at the drive but Nx Server now allows to redirect storage database to the system drive which usually is quite fast and mostly stays unused.
In order to redirect storage database you need to:
- Update system to the patch with build number 184.108.40.20623 or higher
- Stop the Media Server
- Navigate to the storage drive facing the issues, to the directory that contains "hi_quality", "low_quality" folders and <server_id>_media.sqlite database and affilated files(Windows -- local drives and NAS drives, Linux -- local only).
Note! At the end-user PC id part of the database file will be different from the one shown at the screenshots.
- At this folder create file with the name <server_id>_db_ref and extension .guid(tech article shows how to show and change extensions in Windows).
Note! <server_id> part should be the same as at your sqlite database file name.
- With web-browser go to the guid generator web-site, generate new unique guid and copy it to the clipboard.
- Open your new <server_id>_db_ref.guid file with any text editor(for example, notepad) and paste there single line containing guid generated at the web-site. Save it.
- Do steps 3 -- 6 for every drive that suffers from "Slow" errors and start the Media Server.
- If every step is performed correctly, the new directory storage_db will appear at the main Media Server system folder:
-- Windows -- C:\Windows\System32\config\systemprofile\AppData\Local\Network Optix\Network Optix Media Server\storage_db
-- Ubuntu -- /opt/networkoptix/mediaserver/var/storage_db
- It will contain subdirectories for each <server_id>_db_ref.guid file from problem drives. Names will be the same as generated guids.
- After that Server will start a "Fast Archive scan" -- initial database build. After it's over it's necessary to manually force "Archive Index Rebuild" in Server Settings / Storage Management to restore all recordings to the timeline.
Note! If using this method doesn't eliminate the issues -- database redirect is just not enough. The only option is to improve hardware overall performance(adding independent drives, replacing old drives with faster one, etc.).