If you are restoring a backup of the Velocity database to the same computer (a Velocity server, data server, or standalone workstation) where the backup was made, follow the instructions in Moving a Velocity 3.8 Database.
Suppose you are restoring a backed-up Velocity database to a different computer other than the one where it initially backed up; you must perform the additional procedures mentioned after restoring the Velocity database to the new computer. The other tasks are:
Licensing Velocity during the restoration of the Velocity Database
Editing the data in the tables in the restored Velocity database
Importing the Velocity TLS certificate from one server to another
Licensing Velocity during the restoration of the Velocity Database
The Velocity v3.8.4 and below versions use the Velocity licensing mechanism with the unique machine ID of your computer as part of obtaining the Velocity license for the new system. Contact the Identiv Sales department for licensing your Velocity system.
The Velocity v3.8.5 licensing mechanism provides a grace period of 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 displays.
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 installed.
An expired Velocity license notification message displays when the original Velocity license installed is more than 30 days.
If the installation is less than 30 days, a pop-up message asks the user to purchase the Velocity Licensed version.
The Velocity license found in the database that does NOT match the Server ID of that machine will be removed.
All other license types, including plugins or any created and used by IGS, are not applied or extended.
Editing the Data in the Tables in the restored Velocity Database
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 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 this table: | Select this column: | Enter this data: |
|---|---|---|
MiscProperties | AuthenticationPath |
|
VelocityServicesGroupPath | Name of the new Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM. | |
UseDomainAuthentication |
| |
Organizational Unit (OU) (This column exists only if you selected an Organization Unit during the Velocity installation.) | For example: LDAP://OU=ENGINEERING,DC=SECURITY,DC=com | |
Operators | Name | If you are not logging in as Administrator for OperatorID=2, use your Windows user name. (If you are using the Administrator account, skip this step.) |
DirectorySource |
| |
Servers | Server_Name | Name of the new Velocity Server (all UPPERCASE). For example, after restoring the database to a new server, the server name can be VEL1-LOCAL-SYSTEM. |
ServerExtensions | RemoteComputerName | Name of the new Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM. |
Registry | AppPath |
|
ComputerName | Name of the new Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM. | |
RemoteIP | Name of the new Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM | |
RemoteServerIP | Name of the new Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM. | |
SDServer | Name of the new Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM. | |
ServerName | New SQL Server Instance name. For example, VEL1-LOCAL-SYSTEM\SQL_Instance_name. | |
Workstations | WorkstationName | Name of the new Velocity Server for WorkstationID=1 (all UPPERCASE). For example, the workstation name is VEL1-LOCAL-SYSTEM. |
ScheduledServiceTasks | ComputerName | Name of the new Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM (only if scheduled service has been created). |
After each change, click outside the edited row for the changes to take effect.
In a Windows Split Server setup, the Velocity SQL Server Database can be moved to a new location or optionally can be renamed using the SQL Server Management Studio(SSMS) in SQL Server. The database can be moved to a new directory path or a copy of a database on either the same server instance or a different server instance can be created.
7. Restart all Velocity Services and launch the Velocity Application.
8. Click Velocity's menu button, then select Extensions → Server Extensions.
9. The Velocity Server Extensions Manager appears.
The Server Extensions Manager lists the service extensions that need to update the computer’s name before they work on the new computer. Make a note of which server extensions you are using.
10. Click to highlight an existing service extension. The Uninstall button is activated.
11. Click Uninstall. The selected extension service is removed from the system.
12. Reinstall the Server Extensions that are used.
To install a server extension:
Click Velocity's menu button, then select Extensions > Server Extensions.
The Velocity Server Extensions Manager appears.
Click Install.
The Find Server Extension dialog appears.Search for C:\Program Files (x86)\Identiv\Velocity root directory. Several HEX files are located here, as shown.
Select the extension you want to install and click Open.
The newly installed extension appears in the Server Extension list in the Velocity Server Extensions Manager. By default, the extension is enabled (checked,) and the word 'True' appears in the first column.
Repeat steps 3 to 5 to install more extensions.
When you are finished.
A message appears, prompting you to restart the Extension Service before the extension takes effect.Click OK.
For the service extension to take effect, right-click on the Velocity Service Control Manager (SCM) in Windows to try stopping and restarting the extension service.
Start the Velocity DIGI*TRAC Network Service.
The extension services are displayed in Velocity’s Interfaces Configuration folder after installing and restarting them.
Moving Velocity Archive Files
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.
The Velocity archive file contains a snapshot of the alarms and events recorded for a specified Velocity system. This file is created every time the Scheduling Agent runs the Archive Alarm/Event Logs schedule.
To maintain the history of your Velocity system, you should copy the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf files (where xxx is the time and date when the file was created) in the C:\Program Files\Microsoft SQL Server\MSSQL15.IDENTIV\MSSQL\DATA folder from your old source system to the new target system.
If you cannot copy the archive files due to user permission or restriction, grant access to the current user who has logged in.
Restoring SNIB2 and SNIB3 Encryption Files
You can ignore this section if your Velocity system does not have SNIB2 or SNIB3 boards installed in any attached controllers.
On the old system, locate the ...\ProgramData\Identiv\Velocity directory and find the velocitytmpxxxxx.dat files, where XXXX is the number of each encryption file.
There should be one data file for each SNIB2/SNIB3 installed in the system.Copy all relevant .dat files to a USB drive, removable media, or network-accessible location.
Paste the relevant .dat files into the ...\ProgramData\Identiv\Velocity directory on your new computer.
These files will overwrite the existing files, and provide Velocity with the encryption information it needs to communicate with the connected SNIB2s/SNIB3s.
Open Velocity and resume communication between this Velocity server and the SNIB2/SNIB3 installed controller using the specified encryption.
Right-click the .dat files to check if the permissions on each file are set to Full Control.
Importing the VelocityTLS certificate from one server to another
Replacing a Velocity server machine will require the customer to delete the VelocityTLS certificate added by the Velocity installer and manually import the certificate from the Velocity database to the new computers Windows Certificate store (using -import switch option of provided tool, GenerateVelocityTLSCertificate.exe).
Deleting the VelocityTLS certificate added by the Velocity installer
To delete the VelocityTLS certificate:
Open certmgr.msc, goto certificates →Current User→ Personal → Certificates.
In the Certificate Properties dialog box, go to the Details tab and look for the field called "Issuer" or "Issued by". This will tell you where the certificate came from. Note down this information.
If you want to remove the certificate permanently, select the certificate (VelocityTLS) and press the Delete key, or right-click on the certificate and select Delete.
Importing the VelocityTLS certificate from the Velocity database to the Windows Certificate Store
To import the VelocityTLS certificate from the Velocity database:
Open a command prompt with Administrator privileges (i.e., Run as administrator).
Change the Directory to Velocity installation directory (i.e., cd C:\Program Files (x86)\Identiv\Velocity).
Run the GenerateVelocityTLSCertificate.exe with -import switch (i.e., C:\Program Files (x86)\Identiv\Velocity ->GenerateVelocityTLSCertificate -import).
Verify Velocity TLS certificate was imported to Current User → Personal → Certificates.
Sometimes after importing the Velocity TLS certificate, permission for VelocityServices is not set correctly even though VelocityServices displays as having permission. When this occurs, you can fix this problem by deleting and re-granting permission to VelocityServices.
Open certmgr with Administrator permissions and go to Current User → Personal → Certificates.
Right-click VelocityTLS certificate → All Tasks → Manage Private Keys...
Select the user VelocityServices and click the Remove button.
Click OK.
In order to perform the above actions, you need to have administrative rights on the computer.