Loading ...
Loading ...
Loading ...
l
Power outages (make sure you use an Uninterruptible Power Supply (UPS))
l
Static electricity (make sure you ground yourself if you are going to handle a hard disk drive)
l
Fire, water, etc. (avoid)
Windows Task Manager: be careful when you end processes
When you work in Windows Task Manager, be careful not to end any processes which affect the surveillance
system. If you end an application or system service by clicking End Process in the Windows Task Manager, the
process is not given the chance to save its state or data before it is terminated. This may lead to corrupt
camera databases.
Windows Task Manager typically displays a warning if you attempt to end a process. Unless you are absolutely
sure that ending the process is not going to affect the surveillance system, click No when the warning message
asks you if you really want to terminate the process.
Power outages: use a UPS
The single-most common reason for corrupt databases is the recording server being shut down abruptly,
without files being saved and without the operating system being closed down properly. This may happen due
to power outages, due to somebody accidentally pulling out the server's power cable, or similar.
The best way of protecting your recording servers from being shut down abruptly is to equip each of your
recording servers with a UPS (Uninterruptible Power Supply).
The UPS works as a battery-driven secondary power source, providing the necessary power for saving open
files and safely powering down your system in the event of power irregularities. UPSs vary in sophistication,
but many UPSs include software for automatically saving open files, for alerting system administrators, etc.
Selecting the correct type of UPS for your organization's environment is an individual process. When you
assess your needs, however, bear in mind the amount of runtime you require the UPS to be able to provide if
the power fails. Saving open files and shutting down an operating system properly may take several minutes.
SQL database transaction log (explained)
Each time a change is written to an SQL database, the SQL database logs this change in its transaction log.
With the transaction log, you can roll back and undo changes to the SQL database through Microsoft® SQL
Server Management Studio. By default, the SQL database stores its transaction log indefinitely which over time
means that the transaction log has more and more entries. The transaction log is by default located on the
system drive, and if the transaction log keeps growing, it may prevent Windows from running properly.
To avoid such a scenario, flushing the transaction log regularly is a good idea. Flushing it does not make the
transaction log file smaller, but cleans its content and thereby prevents it from growing out of control. Your
VMS system does not flush transaction logs. In SQL Server, there are ways of flushing the transaction log. Visit
the Microsoft support page https://docs.microsoft.com/en-us/sql/relational-databases/logs/the-transaction-
log-sql-server?view=sql-server-2017 and search for Transaction log truncation.
Administrator manual | XProtect® VMS 2023 R1
128 | Requirements and considerations
Loading ...
Loading ...
Loading ...