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