This page contains information about the VMS server failover material copying test. The test was performed to measure the time it takes to copy the stored data after a failback from the failover server to the VMS server. The test results provide a framework for estimating how much time the material copying takes after a failback.
Test setup
The following VMS servers were used when performing the tests:
-
Main VMS server - Real Windows 11 machine with 64 GB RAM
-
Failed VMS server - Virtual machine with Windows 11 and 24 GB RAM
-
Failover VMS server - Virtual machine with Windows 11 and 24 GB RAM
The failed VMS server used camera emulators to keep the stored data similar in each test scenario. Servers used the dedicated disk (the drive D:\) for the storage, and the disk was cleared before running each test scenario. Used servers were connected to a 1GB network.
Test results
The material copying duration was captured from the VMS server logs (C://Program Files/DVMS/DVR/Logs/DVRl.og.txt).
The following table contains information about the material copying test results containing the following information:
-
Duration of failover
-
Number of cameras used
-
Material size that was copied back to the failed server
-
Time in minutes taken for a material copy from failover server to VMS server
|
Failover Duration |
Material Copy |
|||||||||
|
1 Hour |
1 Camera |
5 Cameras |
10 Cameras |
15 Cameras |
20 Cameras |
|||||
|
GB |
Minutes |
GB |
Minutes |
GB |
Minutes |
GB |
Minutes |
GB |
Minutes |
|
|
1,4 |
6 |
7 |
13 |
14 |
20 |
22 |
33 |
29 |
40 |
|
|
5 Hours |
7 |
13 |
35 |
65 |
70 |
130 |
105 |
185 |
140 |
250 |
|
10 Hours |
14 |
26 |
70 |
130 |
140 |
260 |
210 |
390 |
280 |
500 |
|
15 Hours |
22 |
39 |
105 |
195 |
210 |
390 |
315 |
575 |
420 |
750 |