The BVMS Logbook database can be moved to another SQL Server.
This article describes the steps that are necessary to migrate the database and describes how to confirm if the migration was successful.
BVMS is using Microsoft SQL Server Express to store its logbook. Based on the information provided by Microsoft (Compare SQL Server 2017 editions), SQL Server Express is limited to a 10GB database size.
This could be insufficient for larger installations or installations that require a very long logbook retention time. Additionally, some organizations have a dedicated SQL server environment which should be utilized by all applications. The BVMS Logbook database can be moved to another SQL Server. This guide describes the steps that are necessary to migrate the database and describes how to confirm if the migration was successful.
This article shows how to configure Input Alarm and later search for them in the Event search using Web Interface.
There are only 3 different search parameters for Event type search, which are "All", "Motion" and "Alarm". Once can search for any alarms during the set time period and channel and in this way indirectly to filter for Input Alarm (if only Input Alarm triggers Recording for a particular channel). It is not possible to directly narrow the search for particular Alarm type (ex. Input alarm).
Bosch Video Client
How do I backup the complete BVC configuration in Windows 7?
If BVC was installed whilst logged into Windows as the Administrator, go to the following folder:
C:\Users\Administrator\AppData\Roaming\Bosch\Vidos. Copy the conf folder. This folder contains the BVC configuration.
Note : Backup configuration only applicable to the specific BVC version during configuration restore.
Related Products VIPXD (Audio Version) Question Why there is NO sound from a loudspeaker connected to a VIPXD SPK port? Answer The RTC_AUDIO_LOUDSPEAKER_ON_OFF flag is not activated. This flag can be set manually by using this CGI command: http://160.10.x.x/rcp.xml?command=0x09be&type=F_FLAG&payload=1&direction=WRITE&num=1 Replace 160.10.x.x by your VIPXD IP address.
Related Products DVR 700 series BVIP device Question Why does Divar 700 change the settings of 2nd stream, even though only 1st stream is configured in the DVR? Answer Divar 700 uses the concept where it assumes to be the (master) device to have control over the cameras and their streams. Stream 1 is always set to profile 1 Stream 2 is always set to profile 2 Only one command is sent from DVR to set both stream 1&2 So please configure profile 2 in the wanted way to be used with stream 2.
Related Products DiBos version 8.0 to 8.7 BRS version 8.8 and later Question How to configure LDAP in DiBos / BRS? Answer See attached 8 screenshots which guide through the LDAP configuration. Known restrictions on the AD: - users and user groups must be located in the same directory in the AD - DiBos / BRS supports max. 1000 user groups in the AD - Comma separated user (ex. User, John) are not supported.
Related Products Bosch Recording Station (BRS) version 8.9 and later Question I cannot configure UDP tunneling on BRS. Network cards are grayed out. Answer Under certain circumstances BRS NetLimiter may become not registered. The network cards are not shown in Configuration > Security and Network > Network settings. In that case, register BRS NetLimiter manually: 1. Close BRS application 2. Control Panel > System and Security > Administrative Tools > Services > Bosch Networking Service a) Set "Startup Type" to "disabled" b) Stop service c) In a console window with administrative rights, enter "C:\Program Files\Bosch\Recording Station\NetLimiterServer" /service d) Set "Startup Type" to "Automatic" e) Start service 3. Start BRS application
This article guides you through the process of installing the BVMS Logbook Health Checker. The Bosch VMS Logbook Health Checker is a tool that is capable of fixing the overflow of the Bosch VMS Logbook database before it occurs.
How can I protect my security system, from an IT security perspective?
The attached document explains how the security system can be hardened. Additionally the BVMS - Network Design Guide includes best practices for desgning a secure network.
How to terminate a M12 connector for FLEXIDOME micro 5000 MP?
Both RJ45 and M12 plug connectors are available with IEC 11801:2002 Cat5 compliance. This further simplifies the concurrent use of both connector types within a single system. Assembly consists of three easy steps, none of which require specialist tools. The plug connectors, compliant with all standards and fully shielded against EMC interference, are available in four-pin and eight-pin configurations. They can be connected to flexible or rigid wires, with sizes ranging from AWG 26 to AWG 22. This makes the connectors suitable for all Industrial Ethernet transmission systems, Ethernet-based fieldbus systems such as Profinet, and EtherNet/IP up to gigabit speeds. The M12 Quickon connector provides a sturdy metal housing with a plug-and-turn mechanism. A 360 degree shielding connection with an iris spring means the connector is well suited to system environments with large amounts of EMC interference. The compact design of the RJ45 Quickon connector, on the other hand, makes it suitable for horizontal or vertical multi-port connection (as is frequently required by switches, for example). Connector ID rings are available in eight colors to visually aid patch-bay layout.
Microsoft Event Logging, when an error occurs, the system administrator or Integrator must determine what caused the error. The operator can then use the event log to help determine what conditions caused the error and identify the context in which it occurred.
Starting Event Viewer
The procedure for starting Event Viewer depends on your starting point, e.g. windows key + R type in ”eventvwr.msc” hit enter.
With the decent administrative access, you can select any computer in your network to view that Microsoft system event logs.
To select computers in Event Viewer:
In the top of the console tree, right-click Event Viewer (local), and then click Connect to another computer.
Enter FQDN/NetBIOS name or browser to the regarding machine
Adjusting Event Viewer Settings
In the console tree, right-click the appropriate log file, and then click Properties. Click the General tab.
Saving Event Logs
In the console tree, right-click the appropriate log file, and then click Save Log File As. Navigate to the subfolder in which you want to save the file, type a name for the file, click the file type, and then click Save.
Clearing Event Logs
In the console tree, right-click the appropriate log file, and then click clear all Events. You are prompted for whether you want to save the log to a file before clearing it. Click “Yes” to save a log and clear all events. If you click No, the log is not saved, but all events are cleared from the selected Event log. If you click Cancel, the request to clear the log is canceled.
Viewing Event Details
In the console tree, right-click the appropriate log file. A list of events in the log file is displayed in the details pane of Event Viewer. Click a specific event in the details pane to display the Event Properties dialog box and details about the event.
In the console tree, right-click the appropriate log file, and then click Properties. Click the Filter tab. Type the appropriate information that you would like to filter.
In the console tree, right-click the appropriate log file. On the View menu, click Find. Type the appropriate information that you would like to find in the dialog box, and then click Find Next.
An event that indicates a significant problem such as loss of data or loss of functionality. For example, if a service fails to load during startup, an Error event is logged.
An event that is not necessarily significant, but may indicate a possible future problem. For example, when disk space is low, a Warning event is logged. If an application can recover from an event without loss of functionality or data, it can generally classify the event as a Warning event.
An event that describes the successful operation of an application, driver, or service. For example, when a network driver loads successfully, it may be appropriate to log an Information event. Note that it is generally inappropriate for a desktop application to log an event each time it starts.
An event that records an audited security access attempt that is successful. For example, a user's successful attempt to log on to the system is logged as a Success Audit event.
An event that records an audited security access attempt that fails. For example, if a user tries to access a network drive and fails, the attempt is logged as a Failure Audit event.
The events themselves are what we’re trying to see, of course, and their usefulness can range from really specific and obvious things that you can fix easily to the totally undefined messages that don’t make any sense and you can’t find any information on your preferred search engine. example:
The regular fields on the display contain:
Log Name – while in older versions of Windows everything got dumped into the Application or System log, in the more modern editions there are dozens or hundreds of different logs to choose from. Each Windows component will most likely have its own log.
Source – this is the name of the software that generates the log event. The name usually doesn’t directly match with a filename, of course, but it is a representation of which component did it.
Event ID – the all-important Event ID can actually be a little confusing. If you were to Google for “event ID 122” that you see in the next screenshot, you wouldn’t end up with very useful information unless you also include the Source, or application name. This is because every application can define their own unique Event IDs.
Level – This tells you how severe the event is – Information just tells you that something has changed or a component has started, or something has completed. Warning tells you that something might be going wrong, but it isn’t all that important yet. Error tells you that something happened that shouldn’t have happened, but isn’t always the end of the world. Critical, on the other hand, means something is broken somewhere, and the component that triggered this event has probably crashed.
User – this field tells you whether it was a system component or your user account that was running the process that caused the error. This can be helpful when looking through things.
OpCode – this field theoretically tells you what activity the application or component was doing when the event was triggered. In practice, however, it will almost always say “Info” and is pretty useless.
Computer – on your home desktop, this will usually just be your PC’s name, but in the IT world, you can actually forward events from one computer or server to another computer. You can also connect Event Viewer to another PC or server.
Task Category – this field is not always used, but it ends up basically being an informational field that tells you a bit more information about the event.
Keywords – this field is not usually used, and generally contains useless information.
As a rule of thumb (common way of doing), you should try searching by the general description, or the Event ID and the source, or a combination of those values. Just remember that the Event ID is unique for each application. So there is a lot of overlap and you can’t just search for “Event ID 122” only. This is because users might find the list is too large and too general, your specific search aspect might not fit your issue.
What is the decoding performance of BVMS? How many cameras can I open on the screen before the systems is overloaded (and frames are being dropped)?
The BVMS client performance overview is attached to this article and shows, based on several workstation configurations and a specific BVMS version, how many cameras can be opened before the workstation is overloaded.