With the VRM eXport Wizard 2.0 encrypted and unencrypted VRM recordings can be exported (VRM block export) from any video surveillance system based on Bosch Video Recording Manager (VRM) and exported recordings can be converted to mp4-files. Therefore, the VRM eXport Wizard 2.0 offers the following two options, compare also Figure 1:
Export VRM recordings of cameras
Convert already exported data to mp4-file
Export VRM recordings
To export recordings, no matter if encrypted or un-encrypted recordings, from a video surveillance system based on VRM, the user first needs to select and connect to the Bosch VRM system that contains the source video data the user wants to export. To optimize the data traffic, the user can further select the number of maximum sources exported in parallel and set the maximum bit rate used per source, see Figure 2.
Note: To avoid any performance loss of the VRM system it is not recommended to run the VRM eXport Wizard on the same hardware as the VRM itself or any other system critical server (e. g. VRM server, BVMS MS, etc.).
In the next step (Figure 3) the user selects the cameras and the time period that shall be included in the export. Additionally, the user can change the name of the export file and add a comment.
Once the user is done with the camera selection, the export destination has to be selected in the "Select Type and Destination" window, see Figure 4. Here the user can choose between CIFS export, iSCSI export and export to a file system.
Note: The tape export some users might know from previous older versions is no longer supported.
Once the destination is selected, the export process can be started. The VRM export Wizard informs about the current status of the export process and tells the user when the export is completed, compare Figure 5. The exported blocks can now be found on the before choosen destination platform.
Please note for mass exports, if the overall export time is longer than the respective retention time for a camera not all video data might be exported before being overwritten / deleted.
As already mentioned above, this export procedure works for unencrypted as well as encrypted VRM recordings (encrypted and unencrypted VRM blocks).
Unfortunately, for playback of the exported material we have to differentiate between encrypted and unencrypted exported recordings. For playback of unencrypted video data exported by the VRM eXport Wizard BVMS is the best choice, as the user can then also take advantage of the meta data like IVA information. For now, this is not possible for encrypted recordings, because the re-import of encrypted VRM block exports is not yet supported. Instead, the user has to take advantage of the new mp4 conversion functionality of the VRM eXport Wizard. Of course, the conversion also works for unencrypted recordings. Both cases are explained in the following.
Convert already exported data to mp4
To convert VRM block exports to mp4 format the user has to choose the option "Convert already exported data to mp4-file", see Figure 6.
Max file size per MP4 file is 500 MiB
How to convert unencrypted recordings to mp4?
In the "Select exported data for conversion" screen the user can choose the source, in this case unencrypted recording blocks, and the output directory, where the mp4 files shall be saved to, Figure 7. To choose the exported VRM blocks, which shall be converted to mp4 format, the user has to navigate to the corresponding camera folder and has to select the related BIN.file. This is illustrated in Figure 8. For unencrypted VRM blocks no further information is needed and conversion can be started by pressing the next button in the "Select exported data for conversion" screen.
Similar to the export procedure the VRM eXport Wizard also shows the status of the conversion process. Once it is successfully finished, the screen will look like in Figure 9.
How to convert encrypted recordings to mp4?
The conversion of encrypted VRM blocks starts in the same way as the "unencrypted recordings" case above. However, in the "Select exported data for conversion" screen the user needs to add a valid redundancy key for encryption. Therefore, the checkbox "Source is encrypted" needs to be checked and the redundancy key (a .pfx file) needs to be selected and the password needs to be entered, as demonstrated in Figure 10 and Figure 11.
Possible Communication Issue between BVMS 8.0 Central Server and Video Recording Manager (VRM) 3.7x with BVMS 8.0 installed on different Servers.
Communication can get interrupted and configuraiton might fail if the below desribed actions are not performed. If your system is affected or not is described here as follows:
There can be authentication issues between the BVMS Central Server and the Video Recording Manager in case they are installed on different Servers.
It is possible to see reports at the BVMS 8.x system alarms that VRM reports wrong version
Please check in the VRM debug logging if the following logline indications can be found
CONFIG;DEBUG;SENDING XPATH /SYSTEM/DEVICES/DEVICE as well as HAS NO CONFIGURED NODE, SET TO CONFIGURED
CONFIG;INTERNAL;/SYSTEM/DEVICES CHANGED IN CONFIG. DEVICEID= [DEVICE IP]\0;SYSINFO;INTERNAL;LINE 1 HAS NO CONFIGURED NODE, SET TO CONFIGURED
In general please keep in mind, that it is strongly recommended to use VRM 3.71.00xx with BVMS 8.0. Do not use any older VRM version like 03.71.0022. The 03.71.0029 and Releaseletter is available at the BOSCH DownloadStore (status update 2018-10-26). https://downloadstore.boschsecurity.com/FILES/Setup_VRM_03.71.0029_win32.zip Release Letter: https://downloadstore.boschsecurity.com/FILES/Bosch_Releaseletter_VRM_3.71.0029.pdf
At the VRM system / server, please check and ensure that the following Microsoft software packages are pre-installed:
.NET framework 4.6.2 or higher
Redistributables for Visual Studio 2015
In case one component is missing, please perform the following steps:
Download the missing Microsoft components. Note: When using BVMS 8.0 the VRM is typically a 32-Bit VRM software. Therefore the 32-Bit Microsoft packages are needed. Component that was seen as missing is the >> “Visual C++ Redistributable for Visual Studio 2015” https://www.microsoft.com/en-US/download/details.aspx?id=4814 Please choose the 32-Bit version of that when using with 32-Bit VRM and the >> .NET framework 4.6.2 or higher (NDP462-KB3151800-x86-x64-AllOS-ENU.exe) https://www.microsoft.com/en-US/download/details.aspx?id=53344
Stop the VRM (rms.exe) service in Windows services
Install those components with Administrator rights at the VRM server Reboot the server after installation of the Microsoft components
Check if the VRM service is running and if needed Re-Start the VRM (rms.exe) service
Check that the combination of messages are not longer seen in the VRM debug logging
The VRM package is enhanced and useres should no longer run into this issue with VRM 3.81 and newer versions. Please be aware that BVMS releases are tested with certain VRM verions. This still can offer to install a newer VRM than originally rolled-out in the BVMS overall installer. For all VRM versions 3.7x and below 3.81 it is needed to add this packages.
When using Configuration Manager, each device has a status icon.
The method below shows you how to generate an updated certificate for Bosch IP Camera's and VRM Servers
Here we are talking about Certificates, the Icon is colored Yellow with an exclamation mark.
Using the mouse over Tooltip, the device is saying exactly what is wrong with the certificate connection.
VRM on a DIVAR IP 5000:
Right click on the device to Show Certificates, if you wish to view them.
We can see that there are multiple things wrong.
The Cert is not Trusted
Cert Name mismatch.
First is inconsistent date:
All IP devices and PC’s must be synchronized on Date time page (group General)
Second is invalid certificate
First quick look on certificate requirement level, navigate to Preferences -> Configuration Manager -> Access -> Security:
The certificate must just be valid - self signed certificate matching host name/IP address will be sufficient.
We need to generate a new certificate on Certificate page.
Clicking "Generate certificate" button:
should open a certificate creation dialog - most important options are matching common name and matching validity time.
After the certificate is created correct usage must be set as shown below:
IP Camera Certificate
To apply changes VRM must be restarted.
If certificate requirement is higher, then a validatable chain of certification must be used (This would be setup by a System Integrator or IT Administrator):
Trusted - the signing entity CA (e.g. VeriSign) must be trusted on target PC
Issued by this CA - There is a Micro CA setup on this PC.