It’s recommended to back up the existing database, especially if you turned off the automatic daily backup. For additional information, see the Backing Up the Databases section.

If your operating system language is set to a locale other than English, change the locale to English. After the upgrade you can switch back to the original locale.

Launch the BriefCam Administrator Console and stop the BriefCam services.

If you have custom classes and want to upgrade them, make sure the custom classes are enabled. After the upgrade you will see the classes on the Custom Class screen and will need to retrain the classes. Note that you will not be able to change the class name.

Close all BriefCam applications.

Uninstall your VMS plugin/s (including any embedded client plugins).

If you are upgrading from 2024 M1, the upgrade process will upgrade PostgreSQL to version 15.5 and will first export the existing data. (2024 R2 already deploys PostgreSQL 15.5.) Make sure there is enough available space for the backup (the database size + 10 GB of free space). Note that if the database is larger than 150 GB, the upgrade will stop. In this case, contact the BriefCam Support team. In addition, if the database was installed in the previous version to a non-default directory, BriefCam will need double the free space for the backup.

Run the latest version of the BriefCam PostgreSQL installer.

When the installer prompts for a location to store the backup, provide a local directory and not a network path (for example: C:\backup and not \\server\backup). You can provide a network path, but the installer will not be able to validate that there is sufficient space on the network.

The PostgreSQL upgrade may take some time, because data is exported from the old to the new database. For example, a 50 GB database takes about 30 minutes to migrate the data.

If you see the following message, click OK.

Upgrade the following BriefCam 2025 R1 relevant components: BriefCam Server and Web Services. Note that the RabbitMQ component does not need to be upgraded.

If you use NGINX:

1. If you made changes to the nginx.conf file (located by default at: C:/nginx/conf), back up the file.

2. The RESEARCH installer always tries to communicate with Qlik using the default port (443). If this port was changed in QMC, temporarily change it back to 443 for the upgrade process. After the upgrade is complete, you can restore the custom port.

3. Merge the changes from your previous ngingx.conf file to the new file.

4. If you selected to use a secure connection (https), open the BriefCam Administrator Console and set the DefaultSiteProtocol environment setting to https:.

5. Check that the CommonPlatformAPI.ServiceURL environment setting is set to the NGINX IP address or hostname.

6. Add the upstream and routing directives to the NGINX configuration files.

   • In the upstream section, after the upstream definition of the outboundAPIGateway ( replace [SERVERNAME] with the server defined in the upstream definition of the Notification server):

     #BriefCam Common Platform Api
     upstream common-platform-api-backend {
     server [SERVERNAME]:5014;
     }

   • In the routing section (under the Server configuration section, after the routing definition for the Storage Gateway or Notification Service (/signalr)), the following section needs to be added (replace [PROTOCOL] with either http or https based on whether or not you are using TLS):

     location /commonplatformapi/ { 
     proxy_pass [PROTOCOL]://common-platform-api-backend; 
     proxy_http_version 1.1; 
     proxy_set_header Upgrade $http_upgrade; 
     proxy_set_header Connection $connection_upgrade; 
     proxy_set_header Host $host; 
     proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
     proxy_read_timeout 1440m; }

If you use the RESEARCH module:

1. Make a list of any changes you made to QMC, such as whitelist entries.

2. If you use NGINX, stop the NGINX service.

3. Run the RESEARCH installer.

4. If you are using an extended Research license, contact BriefCam’s Support team by logging into the BriefCam Portal at https://www.briefcam.com/support/ and opening a ticket.

5. If you use NGINX, restart the NGINX service.

6. Manually re-enter any custom QMC configurations that were in place before the upgrade.

7. Upgrade to Qlik November 2025, by following the steps in: Upgrading to Qlik November 2025 (for 2025 R1 SP3).Upgrading to Qlik November 2025 (for 2025 R1 SP3)

If you are installing BriefCam 2025 R1 SP1 and the Milestone Embedded plugin, delete the <BCServer>\MilestoneSSOProvider folder.

Reinstall the latest versions of all the VMS plugins you used in the previous installation. Note that the plugin version may have changed from version to version.

If you are using the Genetec Embedded plugin, open the BriefCam.GenetecEmbeddedViewer.dll.config file (located by default in C:\Program Files (x86)\Genetec Security Center x\Plugins\BriefCam) and change the suffix of the serverAddress from /synopsis to /app.

Upgrade the license as follows:

1. Open the Chrome/Edge browser and go to http://localhost:1947.

2. Click on the Sentinel Keys option.

3. From the Actions column, click C2V.

   

4. Log into the BriefCam Portal at https://www.briefcam.com/support/ and open a ticket. You’ll attach the C2V file and request a V2C file with the new features.

5. The BriefCam Customer Success team will email you the requested V2C (vendor to client) file.

6. Open the Chrome/Edge browser and go to to http://localhost:1947.

7. Click the Update/Attach option.

8. Click the Select File button and select the V2C file that you received from BriefCam.

9. Click the Apply File button.

   

Clear the browser's cache.

Launch the BriefCam Administrator Console and start the BriefCam services needed for each host.

Restart the IIS services on the machine where the BriefCam Web Services are installed (by opening the Windows Services, right-clicking on the World Wide Web Publishing Service and clicking Restart).

To ensure that all the new features work as expected, reprocess previously processed videos.