Versions Compared

Version Old Version 3 New Version 4
Changes made by

Anand Rajaraman

Anand Rajaraman

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If you are restoring a backed-up Velocity database to a different computer other than the one where it was originally backed up, you must perform the additional procedures mentioned after you have restored the Velocity database to the new computer. The additional tasks are:

...

  1. For Windows 10 type of machines, to locate the computer name of your system:

    1. Open Control Panel. Click System and Security -> System.

    2. On the View basic information, see the Full computer name under the Computer name, domain, and workgroup settings section. To check the computer name for other types of Windows version, visit Windows support.

  2. From the Windows desktop, select Start-> Microsoft SQL Server Tools 18-> Microsoft SQL Server Management Studio 18.
    The Microsoft SQL Server Management Studio opens.

    Image RemovedImage Added

  3. Login to SQL Server using your credentials.

  4. In the Object Explorer navigation pane, expand the Databases folder to display the Velocity database.

  5. Expand the Velocity database to display the Tables branch.
    Note: Be extra careful while editing the tables, because accidentally editing the tables can corrupt the database.

    Image RemovedImage Added

  6. Make the changes specified in the following table, by right-clicking on 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.)

    Refer the table for data modifications.

...

  1. Click Velocity's menu button, then select Extensions > Server Extensions.

  2. The Velocity Server Extensions Manager appears.

  3. Click Install.
    The Find Server Extension dialog appears.

  4. Search for Identiv\Velocity root directory. Several HEX files are located here as shown.

    Image RemovedImage Added

  5. 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.

    Image RemovedImage Added

  6. Repeat steps 3 till 5 to install more extensions.

  7. When you are finished. click OK.
    A message appears, prompting you to restart the Extension Service before the extension takes effect.

  8. Click OK.

  9. For the service extension to take effect, right click on the Velocity Service Control Manager (SCM) in the Windows try to stop the extension service and restart again.

  10. Start the Velocity DIGI*TRAC Network Service.

Tip

After installing and restarting the extensions services, they are displayed in the Velocity’s Interfaces Configuration folder.

Moving Velocity Archive Files

In a larger facility with lot of activities taking place, the events and alarms table in Velocity database can become quiet 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 past 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.

Restoring SNIB2 and SNIB3 Encryption Files

If your Velocity system does not have SNIB2 or SNIB3 boards installed in any attached controllers, you can ignore this section.

  1. On the old system, locate the ...\Program Files\Identiv\Velocity directory and find the velocitytmpxxxxx.dat files, where xxxxx is the number of each encryption file.
    There should be one data file for each SNIB2/SNIB3 installed in the system.

  2. Copy all relevant .dat files to a USB drive, removable media, or network-accessible location.

  3. On your new computer, paste the relevant .dat files into the ...\Program Files\Identiv\Velocity directory.

    These files will overwrite the existing files, and provide Velocity with the encryption information it needs to communicate with the connected SNIB2s/SNIB3s.

  4. 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 is set to Full control.