Scansource received approval and instructions from the Exacq Engineering team to modify hardware by adding hard drives to existing systems. Since our Tech Support team may need to be aware of the changes, a Sharepoint page with all of the instructions and a spreadsheet with each system that has been modified can be accessed HERE.
Month: January 2022
SSA-SYNC is a way to bring all licenses in a Batch to a common SSA end date without having to buy full-year increments of SSA.
- License 1 has 47 Enterprise IP channels and an SSA end date of 2018-09-01
- License 2 has 6 Professional IP channels and an SSA end date of 2021-10-15
- License 3 has 4 Professional IP channels and an SSA end date of 2021-11-10
The desired outcome is for all licenses to have an SSA end date of 2022-12-31
In order to bring these 3 licenses to 2022-12-31, we need to use custom (partial-year) SSA as opposed to whole-year increments.
License 1 needs 1,582 days of SSA to bring the SSA end date to 2022-12-31
1,582 days of Enterprise SSA for 47 channels would cost $9,166.93, but we can reduce that using “Current Version”.
“Current Version” brings the license to the next exacqVision version date for a fixed price – in this case, $466.00
The next Current Version date is 2021-12-14, so we compare the SSA price to that date to the Current Version price:
The number of days from 2018-09-01 to 2021-12-14 is 1200
1200 days of Enterprise SSA for 47 channels is $6,953.43
Calculated as such: Enterprise SSA = $45.00 per year x 47 channels = $2,115.00 per year, divided by 365 = $5.794521 per day.
1200 days x $5.794521 = $6,953.43
The Current Version price of $466 is less than that, so we’ll use that to get the license to 2021-12-14, and then regular SSA to get it the rest of the way to 2022-12-31
The SSA price from 2021-12-14 to 2022-12-31 (382 days) is $5.794521 per day x 382 days = $2213.51
The total SSA price for License 1 is: $466.00 + $2,213.51 = $2,679.51
License 2 needs 442 days to get its 6 channels to 2022-12-31
It’s a Professional license, so that’s $30.00 per year x 6 channels = $180.00 per year divided by 365 = $0.4931507 per day.
442 days x $0.4931507 per day = $217.97
The total SSA price for License 2 is: $217.97
License 3 needs 416 days to get its 4 channels to 2022-12-31
It’s also a Professional license, so that’s $30.00 per year x 4 channels = $120.00 per year divided by 365 = $0.3287671 per day.
416 days x $0. 3287671 per day = $136.77
The total SSA price for License 3 is: $136.77
The total SSA price to bring all 3 licenses to 2022-12-31 is: $2,679.51 + $217.97 + $136.77 = $3,034.25
SSA-SYNC uses the aggregate price of the custom SSA for all licenses to determine the SSA-SYNC quantity.
For this example, the aggregate price of custom SSA for all licenses is $3,034.25
We round it down to the nearest hundred: 30.34
We remove any digits to the right of the decimal to arrive at the SSA-SYNC quantity: 30
We then multiply the SSA-SYNC quantity by the SSA-SYNC MSRP of $100.00 to get the price $3,000.00
This saves the customer some money when syncing licenses to the same date. The most you can save per order is $99.99
Sometimes you can only save $1.00 – it depends on what the total aggregate custom SSA price is:
- $3,034.25 saves $34.25
- $3,001.00 saves $1.00
- $3,099.99 saves $99.99
- $3,000.00 saves $0.00
All of the above will produce an SSA-SYNC quantity of 30, which will be $3,000.00 when multiplied by the SSA-SYNC MSRP of $100.00.
To make the most efficient use of drive capacity, it is advisable to use drives of the same capacity. This is because the capacity of each drive is limited to the capacity of the smallest drive in the unit. Fault Tolerance:
| RAID Type | Description |
| RAID 5 | This type of unit provides performance, fault tolerance, and high storage efficiency. RAID 5 units can tolerate one drive failing before losing data. |
| RAID 6 | Provides very high fault tolerance with the ability to protect against two consecutive drive failures. Performance and efficiency increase with higher numbers of drives. |
Possible Configurations Based on Number of Drives.
| # Drives | Possible RAID Configurations |
| 3 | RAID 5 |
| 4 | RAID 5 |
| 5 or more | RAID 5RAID 6 |
The total array capacity is defined as follows: Drive Capacity
| RAID Level | Capacity |
| RAID 5 | (number of Drives – 1) x (capacity of smallest drive)Storage Efficiency Increases with the number of disks:Storage efficiency = (number of drives -1) / (number of drives) |
| RAID 6 | (number of drives -2) x (capacity of smallest drive) |
Example 1 3 2TB HDDs RAID 5 Capacity = (3-1) x 2 = 4TB RAID 6 Capacity = N/A requires 4 or higher total HDDs Example 2 4 2TB and 1 4TB HDDs RAID 5 Capacity = (5-1) x 2 = 8TB RAID 6 Capacity = (5-2) x 2 =6TB Auto-Carving Note: If the capacity of the unit you create will exceed 2TB and you are using Windows 2000, Windows XP, Linux 2.4, or FreeBSD 4.x, you will need to enable auto-carving.
Auto-carving divides the available arrays capacity into multiple chunks of 2 TB volumes that can be addressed by the operating systems as separate volumes. Then, when you boot to the operating system, each volume appears as a different disk drive.
I have seen this on two different devices, 2N Force IP and 2N Solo IP
You will need perform the following steps
Go in to the cameras Web GUI under Services
Then click on Automation
-Click on Events at the top of the list and pick an input from the next group.
-Pick the one called SetOnvifVirtualInput and drag it over to the drawing board.
-Set the State of the MotionDetected box to Start
-Draw a connector line from Event to Event
-Set the port to 1
-Set Level to Hi
Repeat the process
-Under Events, drag the Event titled MotionDetected over to the drawing board on the right
-Click on Events at the top of the list and pick an input from the next group.
-Pick the one called SetOnvifVirtualInput and drag it over to the drawing board.
-Set the State of the MotionDetected box to End
-Draw a connector line from Event to Event
-Set the port to 1
-Set Level to Lo
Click on SAVE in the top right corner
Under Add IP Cameras, disable the device and Re-enable the device
Test to see if it is detecting motion correctly now
To mitigate currently known vulnerabilities, the following updates are recommended. Apache to 2.4.51, Apache Solr to 7.5.0 and exacqVision Enterprise Manager (EM) to 21.12.1 or higher.
Note: Updates for both Apache and Apache Solr are available as part of the EM install package for version 21.09 and higher. However, updating to EM versions 21.12 or higher is recommended as this will also address the Log4j vulnerability.
WARNING: You must update EM manually i.e. download from our site and then launch the installer directly. The optional updates will not be prompted for if any other update method is used. Once the updates are in place future updates can be launched from the dashboard.
ALERT: If previous modifications have been made to the default configuration settings such as adding a certificate and key for SSL they will need to be reapplied. See Recover custom settings section below.
Determine the current version of Apache
- Open and administrative Command Prompt
- Navigate to
C:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache2\bin - Run the command
httpd.exe -v - Make note of the Server Version
Determine the current version of Apache Solr
- Open a browser and go to http://127.0.0.1:8983/solr/#
- Make note of the Version
Determine the current version of exacqVision Enterprise Manager
- From the EM dashboard
- Click the Information icon in the upper right-hand corner
- Select About
- Make note of the Version
Install exacqVision Enterprise Manager
- Download the 64-bit Enterprise Manager installer for Windows from our site at https://exacq.com/support/downloads.php. Note: 32-bit updates are not supported.
- Launch the installer
- During the install you will be prompted to update Apache Solr 7.5.0 and/or Apache 2.4.51 it is recommended that you check both.
- A backup folder is created for folders being replaced by each update.
- By default, the newly created backup folders will be located at:
C:\Program Files\exacqVision\EnterpriseManager\apache_solr.oldC:\Program Files\exacqVision\EnterpriseManager\apache2.old - Using the instructions provided earlier verify the versions of Apache, Apache-Solr and Enterprise Manager have changed to confirm the updates.
Note: Resource utilization may be high for a period of time after the update as reindexing is performed.
Recover custom settings (Optional)
As previously mentioned, the updates will overwrite any previous configuration changes. However, those settings were backed up as part of the update. By default, they are located at C:\Program Files\exacqVision\EnterpriseManager\apache_solr.old
- Copy the file httpd-ssl.conf
fromC:\Program Files\exacqVision\EnterpriseManager\apache_solr.old\apache2\conf\extra\
toC:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache2\conf\extra - Copy httpd.conf
fromC:\Program Files\exacqVision\EnterpriseManager\apache_solr.old\apache2\conf\
toC:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache2\conf\ - Copy server.crt
fromC:\Program Files\exacqVision\EnterpriseManager\apache_solr.old\apache2\conf\
toC:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache2\conf\ - Copy server.key
fromC:\Program Files\exacqVision\EnterpriseManager\apache_solr.old\apache2\conf\
toC:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache2\conf\ - Restart the solrApache Service
RESTORE (SPECIAL CASE)
When restoring EM to a previous version that used Apache Solr 6.6.0 or earlier it is necessary to manually restore an Apache Solr backup containing the targeted version of Apache Solr for that install. Note: If a backup does not exist a restore cannot be performed.
- To perform a restore first determine the version of the apache_solr backup which is appropriate.
- Stop all exacqVision Enterprise Manager service including solrApache and solrJetty.
- Copy the existing
C:\Program Files\exacqVision\EnterpriseManager\apache_solrfolder to a safe location renaming it as appropriate - Replace with the apache_solr backup folder
- Start all exacqVision Enterprise Manager service including solrApache and solrJetty.
Notes
The presence of Log4j files in C:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache-solr\server\resources does not mean there is a vulnerability ensure the version of apache is either 2.4.51 or 7.5.0.
Related Trac Tickets
- https://trac.exacq.com/DVR/ticket/23311 “Fix Log4j vulnerability in Apache Solr – CVE-2021-44228”
- https://trac.exacq.com/DVR/ticket/23188 “Update Apache to 2.4.51”
- https://trac.exacq.com/DVR/ticket/23062 “Apache Solr incremental update to 7.5.0”