The failover Recording Server will kick in if the Recording Server is down. If uptime is critical, a failover server should be used. With less data in the live database, the reindex should be fairly quick. When the live database is rebuilt/reindexed, we can start recording to it and rebuild the archive index in the background. First, if you're running XProtect Corporate or XProtect Expert, and you're not archiving, you can speed up the rebuild process by having a live database for a few hours of data and an archive drive for the rest. However it happens, there are various ways to mitigate/minimize downtime. Power loss is the most common failure causing problems like this. This can happen if the power is lost, if the storage fails in some way, if the OS blue screens or the software crashes unexpectedly. It is definitely possible for corruption to occur and for that to result in some downtime while the data is reindex/repaired. BLK files, with some mix of index/metadata files to accompany them. The Recording Server stores the media in the database which is persisted to disk in. We do not use SQL or any other commercial/open source database software for storing or indexing media data. Our media database is implemented in such a way that our Recording Server is essentially a database server itself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |