Versions Compared

Version Old Version 1 New Version 2
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 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:

...

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 Before Velocity 3.8.5 6, 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 once you have restored your Velocity database on the new hardware. The grade grace 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.

...

  1. On Windows 10, 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. Visit Windows Support to check the computer name for other types of Windows versions.

  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.

  3. Log in to SQL Server using your credentials.

  4. Expand the Databases folder to display the Velocity database in the Object Explorer navigation pane.

  5. Expand the Velocity database to display the Tables branch.

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

  • If using local Windows accounts, the name of the local computer. For example, after restoring the database to a new system, the local computer name would be VEL1-LOCAL-SYSTEM.

  • If using domain accounts, the Windows Domain name.

VelocityServicesGroupPath

Name of the new Velocity Server (all UPPERCASE). For example, VEL1-LOCAL-SYSTEM.

UseDomainAuthentication

  • 0=Use Local accounts

  • 1=Use Domain accounts

Organizational Unit (OU)

(This column exists only if you selected an Organization Unit during the Velocity installation.)
LDAP://OU=Organizational Name,DC=Domain Name,DC=Top-Level Domain Name

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

  • If using local Windows accounts, update all rows to the local computer’s name. For example, the local computer name can be \\VEL1-LOCAL-SYSTEM after restoring the database to a new system.

  • If using domain accounts, update all rows to the Windows Domain name. For example, \\SQL_Instance_name.

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

  • Destination of the application path. For example: C:\Program Files(x86)\Identiv\Velocity.

  • If this is a 64-bit version of Windows, the path is: C:\Program Files (x86)\Identiv\Velocity.

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.

...