Overview
The computer from which you are transferring database files is called the source computer, and the computer to which you are transferring the database files is called the target computer.
The process of migrating your Velocity database to a different computer can be separated into three phases:
Preparing the computers for migration
Backing up current database files on your source computer
Restoring your existing Velocity database to the target computer and customizing the resulting database
If you are planning to upgrade Velocity, perform your upgrade, and then move your database.
Preparing the Computers for Migration
Before you begin this process, make sure you have fulfilled the following prerequisites:
The person performing these procedures should be versed in several SQL Server tasks, including backing up and restoring the Velocity database, as well as modifying SQL tables.
Make sure the person who will be doing the actual migration has administrator privileges on both the source and target computers
Make sure that the versions of the SQL Server you have on both your source and target computers are the same
Make sure that the version of Velocity on the source and target computers are the same – this includes service packs and KB updates.
After you have fulfilled these prerequisites, you can perform the required procedures on the source computer.
Backing up the Current Database
The Velocity database file you will be moving is the backup file (.BAK). The database backup procedure differs depending on whether you are using:
Backing Up Using SQL 2012
If you are backing up the Velocity database using SQL 2012, use this procedure:
Right-click on the Velocity Service Control Manager (SCM) icon on the source computer, stop all Velocity services, then select the Exit option to exit SCM.
Open Microsoft SQL Server Management Studio; from the Windows desktop, select Start-> Microsoft SQL Server 2012 -> SQL Server Management Studio.
The Connect to Server dialog appears:
Click Connect.
The Microsoft SQL Server Management Studio screen appears:
In the left tree pane, expand the Databases folder to reveal the Velocity database.
Right-click on the Velocity database.
A pop-up menu appears.
Select Tasks -> Back Up...
The Back-Up Database – Velocity dialog appears:
If one or more backups are already displayed in the Destination pane, remove them by highlighting the device and clicking the Remove button.
Click the Add... button to the right of the Destination pane.
The Select Backup Destination dialog appears:
Click to select the File name radio button.
In the ‘File name’ field, place your cursor at the end of the path and type a name for the database file you are about to create. For example, Velocity_backup.bak.
Make note of the path where this backup file is created, because you will need to access the file during a later step.Click OK to close this dialog and return to the Back Up Database – Velocity dialog.
The new file name now appears in the Destination pane.Click OK again.
The current Velocity database is backed up to the selected destination. A message appears indicating that the database was backed up successfully.
Click OK.
Exit the SQL Server Management Studio.
Backing Up Using SQL 2014
If you are backing up the Velocity database using SQL 2014, use this procedure:
Right-click on the Velocity Service Control Manager (SCM) icon on the source computer, stop all Velocity services, then select the Exit option to exit SCM.
Open Microsoft SQL Server Management Studio; from the Windows desktop, select Start-> Microsoft SQL Server 2014-> SQL Server 2014 Management Studio.
The Connect to Server dialog appears:
Click Connect.
The Microsoft SQL Server Management Studio screen appears:
In the left tree pane, expand the Databases folder to reveal the Velocity database.
Right-click on the Velocity database.
A pop-up menu appears.
Select Tasks > Back Up...
The Back-Up Database – Velocity dialog appears:
If one or more backups are already displayed in the Destination pane, remove them by highlighting the device and clicking the Remove button.
Click the Add... button to the right of the Destination pane.
The Select Backup Destination dialog appears:
Click to select the File name radio button.
In the ‘File name’ field, place your cursor at the end of the path and type a name for the database file you are about to create. For example, Velocity_backup.bak.
Make note of the path where this backup file is created, because you will need to access the file during a later step.Click OK to close this dialog and return to the Back Up Database – Velocity dialog.
The new file name now appears in the Destination pane.Click OK again.
The current Velocity database is backed up to the selected destination. A message appears indicating that the database was backed up successfully.Click OK.
Exit the SQL Server Management Studio.
Backing Up Using SQL 2017
If you are backing up the Velocity database using SQL 2017, use this procedure:
Right-click on the Velocity Service Control Manager (SCM) icon on the source computer, stop all Velocity services, then select the Exit option to exit SCM.
Open Microsoft SQL Server Management Studio; from the Windows desktop, select Start->Microsoft Server Tools 18->Microsoft Server Management Studio 18.
The Connect to Server dialog appears:
Click Connect.
The Microsoft SQL Server Management Studio screen appears
In the left tree pane, expand the Databases folder to reveal the Velocity database.
Right-click on the Velocity database.
A pop-up menu appears.Select Tasks -> Back Up...
The Back-Up Database – Velocity dialog appears:
If one or more backups are already displayed in the Destination pane, remove them by highlighting the device and clicking the Remove button.
Click the Add... button to the right of the Destination pane.
The Select Backup Destination dialog appears:
Click to select the File name radio button.
In the ‘File name’ field, place your cursor at the end of the path and type a name for the database file you are about to create. For example, Velocity_backup.bak.
Make note of the path where this backup file is created, because you will need to access the file during a later step.
Click OK to close this dialog and return to the Back Up Database – Velocity dialog.
The new file name now appears in the Destination pane.
Click OK again.
The current Velocity database is backed up to the selected destination. A message appears indicating that the database was backed up successfully.
Click OK.
Exit the SQL Server Management Studio.
Backing Up Using SQL 2019
If you are backing up the Velocity database using SQL 2019, use this procedure:
Right-click on the Velocity Service Control Manager (SCM) icon on the source computer, stop all Velocity services, then select the Exit option to exit SCM.
Open Microsoft SQL Server Management Studio; from the Windows desktop, select Start->Microsoft Server Tools 18->Microsoft Server Management Studio 18.
The Connect to Server dialog appears:
Click Connect.
The Microsoft SQL Server Management Studio screen appears
In the left tree pane, expand the Databases folder to reveal the Velocity database.
Right-click on the Velocity database.
A pop-up menu appears.Select Tasks -> Back Up...
The Back-Up Database – Velocity dialog appears:
If one or more backups are already displayed in the Destination pane, remove them by highlighting the device and clicking the Remove button.
Click the Add... button to the right of the Destination pane.
The Select Backup Destination dialog appears:
Click to select the File name radio button.
In the ‘File name’ field, place your cursor at the end of the path and type a name for the database file you are about to create. For example, Velocity_backup.bak.
Make note of the path where this backup file is created, because you will need to access the file during a later step.
Click OK to close this dialog and return to the Back Up Database – Velocity dialog.
The new file name now appears in the Destination pane.
Click OK again.
The current Velocity database is backed up to the selected destination. A message appears indicating that the database was backed up successfully.
Click OK.
Exit the SQL Server Management Studio.
Moving a Velocity 3.6 Database
Before proceeding, make sure you have installed Velocity 3.6 on the target computer using the instructions in the Velocity 3.6 Installation Guide.
To make sure no data or history is lost, the following files must be copied to the target computer:
Velocity database backup
SNIB2/SNIB3 Encryption files (.DAT)
Velocity archives (detached databases)
To move a Velocity 3.6 database from one computer to another:
If your installation does not use SNIB2/SNIB3 ports, skip Steps 1 – 3 and go to Step 4.
On the source PC, open Windows Explorer and navigate to C:\Program Files (x86)\Identiv\Velocity.
Scroll down until you see files with the general format velocitytmpxxx.dat, where xxx is the address of the Velocity SNIB2/SNIB3 port.
These .dat files are encryption key files for the individual SNIB2s/SNIB3s this Velocity system controls.
There should be one .dat file for each SNIB2/SNIB3 port.Copy all encryption .dat files to a thumb drive, media, or other network-accessible location.
Copy the Velocity backup file created previously using this procedure:
On the source computer, go to
C:\Program Files\Microsoft SQLServer\MSSQL11.IDENTIV\MSSQL\BackupLocate the Velocity backup created previously.
Copy this backup file to a USB drive, media, or other network-accessible location.
Right-click on the Velocity Service Control Manager icon on the target PC, stop all Velocity services and then select the Exit option to exit SCM.
If your installation does not use SNIB2/SNIB3 ports, skip Steps 6–7and go to Step 8Copy the source PC’s .dat files from the thumb drive, media, or other network-accessible location to the C:\Program Files\Hirsch Electronics\Velocity subdirectory on the target PC.
Check the permissions of the .dat file(s). To do this:
Right-click on the .dat file.
Select Properties then click the Security tab.
Highlight the Velocity Service account as shown below.
Check the ‘Allow’ box on the Full Control line.
If you are not running on a domain or are not using SNIB2/SNIB3 ports, ignore this step and proceed to Step 8.
If you have any Velocity archive files, you need to copy these files as well so that you don't lose any of the history stored on these archives.
To move the Velocity archive files:
On the source PC, locate the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf file (where xxx is the time and date when the file was created) in the C:\Program Files\Microsoft SQL Server\ MSSQL11.IDENTIV\ MSSQL\Data subdirectory.
Copy these files to a USB drive, media, or other network-accessible location.
On the target PC, copy the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf files to the same SQL Server subdirectory specified in Step 8a.
On the target PC, make a backup of the current database and store it under a name, such as Velocity_default_db.bak.
This database can be used later as a comparison to indicate whether you need to modify (or add rows) tables in the migrated database or kept in case you need to restore the original.
Copy the database backup created previously from the thumb drive, media, or other network-accessible location to the appropriate SQL Server backup Subdirectory. This is the same for both SQL 2012 and SQL 2014 as below:
For SQL 2012 Express, select C:\Program Files\Microsoft SQL Server\MSSQL11.IDENTIV\ MSSQL\Backup
For SQL 2014 Express, select C:\Program Files\Microsoft SQL Server\ MSSQL12.IDENTIV\ MSSQL\Backup
On the target PC, open the SQL Server Management Studio by selecting Start > All Programs or Start > Programs, then
For SQL 2012 Express, select Microsoft SQL Server 2012> SQL Server Management Studio Express
For SQL 2014 Express, select Microsoft SQL Server 2014> SQL Server Management Studio Express
The Connect to Server dialog box appears like in this example:
Click Connect.
The SQL Server Management Studio screen appears like in this example:
From the left tree pane, expand the Databases folder to reveal the Velocity database.
Right-click on the Velocity database.
A pop-up option list appears.
Select Tasks -> Restore -> Database...
The Restore Database – Velocity dialog box appears.
Select the device radio button from Source, then click the browse button.
The Select backup devices dialog appears:
Click Add, then locate and select the backup file you copied from the source computer.
Click OK until the Restore Database dialog reappears.
The appropriate .bak file to be restored should now appear in the pane:
Click the Options tab.
Make sure the ‘Overwrite the existing database’ box is checked.
Click OK.
The current Velocity database is overwritten. When it has been completed successfully, a confirmation message appears.
Click OK once again. The main page appears.
Right-click on the Velocity database, and select the Refresh option.
Expand the Velocity database and select Tables in the left pane.
A list of database table options appears:
Right-click on the following tables and select Edit Top 200 Rows, then make the specified changes.
In this table... | Select this column... | And enter this data: |
MiscProperties | AuthenticationPath | If using local Windows accounts, the name of the local computer. If using domain accounts, the Windows Domain name. |
UseDomainAuthentication | 0=Use Local accounts 1=Use Domain accounts, | |
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=SEC URITY,DC=com | |
Operators | Name | If you are not logging in as Administrator for OperatorID=2, 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 name of the local computer. (for example: \\Hirsch) If using domain accounts, update all rows to the Windows Domain name. | |
Servers | Server_Name | Name of the Velocity Server (all UPPERCASE) |
ServerExtensions | RemoteComputerName | Name of the Velocity Server (all UPPERCASE) |
Registry | AppPath | Destination of the application path. For example: C:\Program Files\Hirsch Electronics\Velocity If this is a 64-bit version of Windows, the path is: C:\Program Files (x86)\Hirsch Electronics\Velocity |
ComputerName | Name of the Velocity Server (all UPPERCASE). | |
RemoteIP | ||
RemoteServerIP | ||
SDServer | ||
ServerName | ||
Workstations | WorkstationName | Name of the Velocity Server for WorkstationID=1 (all UPPERCASE) |
After each change, click outside the edited row for the changes to take effect.
26. Minimize, but do not close, the SQL Server Database Manager. You must verify that everything is working properly before closing SQL Server.
27. Open Velocity’s Service Control Manager and start all Velocity Services starting with the Security Domain Service, then the DIGI*TRAC Network Service, then the Extension Service, then finally the CCTV Service.
28. Launch Velocity.
The source database should now be running on the Velocity target computer.
Moving a Velocity 3.7 Database
Before proceeding, make sure you have installed Velocity 3.7 on the target computer using the instructions in the Velocity 3.7 Installation Guide.
To make sure no data or history is lost, the following files must be copied to the target computer:
Velocity database backup
SNIB2/SNIB3 Encryption files (.DAT)
Velocity archives (detached databases)
To move a Velocity 3.7 database from one computer to another:
If your installation does not use SNIB2/SNIB3 ports, skip Steps 1 – 3 and go to Step 4.
On the source PC, open Windows Explorer and navigate to C:\Program Files (x86)\Identiv\Velocity.
Scroll down until you see files with the general format velocitytmpxxx.dat, where xxx is the address of the Velocity SNIB2/SNIB3 port.
These .dat files are encryption key files for the individual SNIB2s/SNIB3s this Velocity system controls.
There should be one .dat file for each SNIB2/SNIB3 port.Copy all encryption .dat files to a thumb drive, media, or other network-accessible location.
Copy the Velocity backup file created previously using this procedure:
On the source computer, go to
C:\Program Files\Microsoft SQL Server\MSSQL15.IDENTIV\MSSQL\BackupLocate the Velocity backup created previously.
Copy this backup file to a USB drive, media, or other network-accessible location.
Right-click on the Velocity Service Control Manager icon on the target PC, stop all Velocity services and then select the Exit option to exit SCM.
If your installation does not use SNIB2/SNIB3 ports, skip Steps 6–7and go to Step 8Copy the source PC’s .dat files from the thumb drive, media, or other network-accessible location to the C:\Program Files (x86)\Identiv\Velocity subdirectory on the target PC.
Check the permissions of the .dat file(s). To do this:
Right-click on the .dat file.
Select Properties then click the Security tab.
Highlight the Velocity Services property, as shown below.
Check the ‘Allow’ box on the Full Control line permissions.
If you are not running on a domain or are not using SNIB2/SNIB3 ports, ignore this step and proceed to Step 8.
If you have any Velocity archive files, you need to copy these files as well so that you don't lose any of the history stored on these archives.
To move the Velocity archive files:
On the source PC, locate the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf file (where xxx is the time and date when the file was created) in the C:\Program Files\Microsoft SQL Server\MSSQL15.IDENTIV\MSSQL\Data subdirectory.
Copy these files to a USB drive, media, or other network-accessible location.
On the target PC, copy the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf files to the same SQL Server subdirectory specified in Step 8a.
On the target PC, make a backup of the current database and store it under a name, such as Velocity_default_db.bak.
This database can be used later as a comparison to indicate whether you need to modify (or add rows) tables in the migrated database or kept in case you need to restore the original.
Copy the database backup created previously from the thumb drive, media, or other network-accessible location ) to the C:\Program Files\Microsoft SQL Server\MSSQL15.IDENTIV\MSSQL\Backup subdirectory.
On the target computer, open the SQL Server Management Studio by selecting Start > All Programs or Start > Programs, then select Microsoft SQL Server Management Studio 18 or enter Microsoft SQL Server Management Studio 18.
The Microsoft SQL Server Management Studio window and later a Connect to Server dialog appears:
Click Connect.
The SQL Server Management Studio screen appears:
From the left tree pane, expand the Databases folder to reveal the Velocity database.
Right-click on the Velocity database.
A pop-up menu appears.
Select Tasks -> Restore -> Database...
The Restore Database – Velocity dialog box appears.
Select the device radio button from Source, then click the browse button.
The Select backup devices dialog appears:
Click Add, then locate and select the backup file you copied from the source computer.
Click OK until the Restore Database dialog reappears.
The appropriate .bak file to be restored should now appear in the bottom pane:
Click the Options tab.
Make sure the ‘Overwrite the existing database’ box is checked.
Click OK.
The current Velocity database is overwritten. When it has been completed successfully, a confirmation message appears.Click OK once again. The main page appears.
Right-click on the Velocity database, and select the Refresh option.
Expand the Velocity database and select Tables in the left pane.
A list of database table options appears:
Right-click on the following tables and select Edit Top 200 Rows, then make the specified changes.
In this table... | Select this column... | And enter this data: |
MiscProperties | AuthenticationPath | If using local Windows accounts, the name of the local computer. If using domain accounts, the Windows Domain name. |
UseDomainAuthentication | 0=Use Local accounts 1=Use Domain accounts, | |
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=SEC URITY,DC=com | |
Operators | Name | If you are not logging in as Administrator for OperatorID=2, 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 name of the local computer. (for example: \\Hirsch) If using domain accounts, update all rows to the Windows Domain name. | |
Servers | Server_Name | Name of the Velocity Server (all UPPERCASE) |
ServerExtensions | RemoteComputerName | Name of the Velocity Server (all UPPERCASE) |
Registry | AppPath | Destination of the application path. For example: C:\Program Files\Hirsch Electronics\Velocity If this is a 64-bit version of Windows, the path is: C:\Program Files (x86)\Hirsch Electronics\Velocity |
ComputerName | Name of the Velocity Server (all UPPERCASE). | |
RemoteIP | ||
RemoteServerIP | ||
SDServer | ||
ServerName | ||
Workstations | WorkstationName | Name of the Velocity Server for WorkstationID=1 (all UPPERCASE) |
After each change, click outside the edited row for the changes to take effect.
26. Minimize, but do not close, the SQL Server Database Manager. You must verify that everything is working properly before closing SQL Server.
27. Open Velocity’s Service Control Manager and start all Velocity Services starting with the Security Domain Service, then the DIGI*TRAC Network Service, then the Extension Service, then finally the CCTV Service.
28. Launch Velocity.
The source database should now be running on the Velocity target computer.
Moving a Velocity 3.8 Database
Before proceeding, make sure you have installed Velocity 3.8 on the target computer using the instructions in the Velocity 3.8 Installation Guide.
To make sure no data or history is lost, the following files must be copied to the target computer:
Velocity database backup
SNIB2/SNIB3 Encryption files (.DAT)
Velocity archives (detached databases)
To move a Velocity 3.8 database from one computer to another:
If your installation does not use SNIB2/SNIB3 ports, skip Steps 1 – 3 and go to Step 4.
On the source PC, open Windows Explorer and navigate to C:\ProgramData\Identiv\Velocity.
Scroll down until you see files with the general format velocitytmpxxx.dat, where xxx is the address of the Velocity SNIB2/SNIB3 port.
These .dat files are encryption key files for the individual SNIB2s/SNIB3s this Velocity system controls.
There should be one .dat file for each SNIB2/SNIB3 port.Copy all encryption .dat files to a thumb drive, media, or other network-accessible location.
Copy the Velocity backup file created previously using this procedure:
On the source computer, go to
C:\Program Files\Microsoft SQL Server\MSSQL15.IDENTIV\MSSQL\BackupLocate the Velocity backup created previously.
Copy this backup file to a USB drive, media, or other network-accessible location.
Right-click on the Velocity Service Control Manager icon on the target PC, stop all Velocity services and then select the Exit option to exit SCM.
If your installation does not use SNIB2/SNIB3 ports, skip Steps 6–7and go to Step 8Copy the source PC’s .dat files from the thumb drive, media, or other network-accessible location to the C:\ProgramData\Identiv\Velocity subdirectory on the target PC.
Check the permissions of the .dat file(s). To do this:
Right-click on the .dat file.
Select Properties then click the Security tab.
Highlight the Velocity Service account as shown below.
Check the ‘Allow’ box on the Full Control line.
If you are not running on a domain or are not using SNIB2/SNIB3 ports, ignore this step and proceed to Step 8.
If you have any Velocity archive files, you need to copy these files as well so that you don't lose any of the history stored on these archives.
To move the Velocity archive files:
On the source PC, locate the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf file (where xxx is the time and date when the file was created) in the C:\Program Files\Microsoft SQL Server\MSSQL15.IDENTIV\MSSQL\Data subdirectory.
Copy these files to a USB drive, media, or other network-accessible location.
On the target PC, copy the VelocityArchivexxx.mdf and VelocityArchivexxx_log.ldf files to the same SQL Server subdirectory specified in Step 8a.
On the target PC, make a backup of the current database and store it under a name, such as Velocity_default_db.bak.
This database can be used later as a comparison to indicate whether you need to modify (or add rows) tables in the migrated database or kept in case you need to restore the original.
Copy the database backup created previously from the thumb drive, media, or other network-accessible location ) to the C:\Program Files\Microsoft SQL Server\MSSQL15.IDENTIV\MSSQL\Backup subdirectory.
On the target computer, open the SQL Server Management Studio by selecting Start > All Programs or Start > Programs, then select Microsoft SQL Server Management Studio 18 or enter Microsoft SQL Server Management Studio 18.
The Microsoft SQL Server Management Studio window and later a Connect to Server dialog appears:
Click Connect.
The SQL Server Management Studio screen appears:
From the left tree pane, expand the Databases folder to reveal the Velocity database.
Right-click on the Velocity database.
A pop-up menu appears.
Select Tasks -> Restore -> Database...
The Restore Database – Velocity dialog box appears.
Select the device radio button from Source, then click the browse button.
The Select backup devices dialog appears:
Click Add, then locate and select the backup file you copied from the source computer.
Click OK until the Restore Database dialog reappears.
The appropriate .bak file to be restored should now appear in the bottom pane:
Click the Options tab.
Make sure the ‘Overwrite the existing database’ box is checked.
Click OK.
The current Velocity database is overwritten. When it has been completed successfully, a confirmation message appears.
Click OK once again. The main page appears.
Right-click on the Velocity database, and select the Refresh option.
Expand the Velocity database and select Tables in the left pane.
A list of database table options appear:
Right-click on the following tables and select Edit Top 200 Rows, then make the specified changes.
The table describes the modification of the SQL table properties and their value. 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.
There are three entities that control access to Velocity:
AuthenticationPath\VelocityUsersGroup
VelocityServicesGroupPath\VelocityServicesAccount
VelocityServicesGroupPath\VelocityServicesGroup
These entities are specified in the MiscProperties table as shown below:
In this table: | Select this column: | Enter this data: |
|---|---|---|
MiscProperties | AuthenticationPath | The authentication path for the Velocity users group (see VelocityUsersGroup below)
|
VelocityUsersGroup | Name of the Windows (or Active Directory) group that all Windows (or Active Directory) users that are Velocity operators must belong to. The default value is Velocity Users. User can also define custom users group name. | |
VelocityServicesGroupPath | The authentication path for both the Velocity services group and Velocity services account (see VelocityServicesGroup and VelocityServicesAccount below)
| |
VelocityServicesAccount | Name of a dedicated Windows (or Active Directory) user account to run the Velocity services. The default value is “VelocityServices” . User can also define custom services account group name. | |
VelocityServicesGroup | Name of the Windows (or Active Directory) group that the account running the Velocity services must belong to. The default value is “Velocity Services” (note the space). User can also define a custom services group name. | |
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). |
The column names, VelocityServicesAccount, VelocityServicesGroup, and VelocityUsersGroup in the MiscProperties table are specific to Velocity v3.8.5 and above.
After each change, click outside the edited row for the changes to take effect.
26. Minimize, but do not close, the SQL Server Database Manager. You must verify that everything is working properly before closing SQL Server.
27. Open Velocity’s Service Control Manager and start all Velocity Services starting with the Security Domain Service, then the DIGI*TRAC Network Service, then the Extension Service, then finally the CCTV Service.
28. Launch Velocity.
The source database should now be running on the Velocity target computer.