...
Licensing Velocity during the restoration of the Velocity Database
Contact the Identiv Sales department for licensing your Velocity system.
The
...
The Velocity license mechanism uses attributes of your computer to form a unique System ID that is used to license your system which is used to validate your Velocity license.
Prior to Velocity 3.8.5 restoring your database on a new machine would invalidate your existing Velocity licenses because the new machine's System ID would no longer match your license stored in the restored Velocity database.
Starting with Velocity v3.8.5, the licensing mechanism provides a grace period of up to 30 days while moving Velocity instances or updating them based on licensing schemas, depending on the Velocity update on the expiration of the demo license and an expiration alert window like the one below displaysonce you have restored your Velocity database on the new hardware. The grade period follows the Demo License of the newly installed Velocity software on the new machine. Therefore you may continue to use your new instance of Velocity (with the restored database) while you obtain your new licenses (for the new hardware) from Identiv.
During Demo License period you will see the Velocity Demo License expiration reminder (as shown below) each time an operator logs in until you have obtained new Velocity Licenses for the new hardware.
...
The following rules of the temporary license apply while migrating Velocity Application from one system to another,
If the migrated system does not have the Velocity license, a 30 days temporary license will be installeda valid Velocity license (i.e., license for the new hardware), the 30 day demo license is used.
An expired Velocity license notification message displays is displayed when the original Velocity license installed is more than 30 days.has bot been replaced with a new license within the 30 day demo period
If the installation is less than 30 days, a pop-up message reminder asks the user to purchase the Velocity Licensed version.
The Velocity license licenses found in the database that does do NOT match the Server ID of that machine will be removed.
All other license types , including plugins or any created and used by IGS, (i.e. Velocity integrations) are not applied or extended.
...
After restoring the Velocity database to the new system, perform the following procedure to edit the data in the SQL tables of the Velocity database.
For On Windows 10 type of machines, to locate the computer name of your system:
Open Control Panel. Click System and Security → System.
On the View basic information, see the Full computer name under the Computer name, domain, and workgroup settings section. Visit Windows Support to check the computer name for other types of Windows versions.
From the Windows desktop, select Start→ Microsoft SQL Server Tools 18→ Microsoft SQL Server Management Studio 18.
The Microsoft SQL Server Management Studio opens.
Log in to SQL Server using your credentials.
Expand the Databases folder to display the Velocity database in the Object Explorer navigation pane.
Expand the Velocity database to display the Tables branch.
Make the changes specified in the following table by right-clicking each database table and selecting Edit Top 200 Rows from the pop-up menu. (After each change, click outside the edited row for the changes to take effect.)
Note: Be extra careful while editing the tables because accidentally editing the tables can corrupt the database.
The table describes the modification of the SQL table properties and their value after a Database restoration. A set of table properties such as Server_Name, Remote Computer Name, Application path, Remote Server IP, and its value are replaced by the destination system name or target system name, for example, VEL1-LOCAL-SYSTEM.
...
In a larger facility with many activities, the events and alarms table in the Velocity database can become quite large. It becomes critical for the older alarms and events to be archived.
...