This document is a manual for managing the Vusion Database and Vusion Extraction Agent in the event of server changes or TMWSuite upgrades.  There are three common scenarios that might affect your routine Vusion data extractions:

  1. The company has recently upgraded to new servers and the Vusion Agent and Vusion Database need to move from the old server to the new one, that also houses the TMWSuite database.
  2. The company recently upgraded their TMWSuite Database and the Vusion Agent/Database needs to be pointed to the new TMWSuite, and they reside on the same server.
  3. The company needs to move the Vusion Agent / Database to a new SQL server, which is not the same server that the TMWSuite Database is on.

The following three scenarios are laid out below.

 

Vusion Database / Agent Moving to New SQL Server Which Also Houses TMWSuite

Should the Vusion Database and Agent reside on the old server, and server changes necessitate that they are migrated to a new server where TMWSuite resides, the following steps will have to be followed to continue extracting data to Vusion’s FTP:

  1. A backup of the Vusion Database will need to be done so it can be restored after the migration.
  2. Uninstall the Vusion Agent on the server that it currently resides on
  3. Migrate the existing Vusion database to its new location
  4. Install the Vusion Agent on its new server
  5. Configure the newly installed Vusion Agent to point to the TMWSuite Database
    1. In the Vusion Database SETTINGS table, make sure the DBTMW_SERVER is still blank, and DBTMW_DATABASE is still set to the correct TMW database (name provided by client).
  6. Inside the Vusion Agent SETTINGS, type in
    1. SQL server
    2. Database (is the Vusion database so still should be VusionClient)
    3. Credentials provided by original Vusion email, FTP_USERNAME for FTP Username, FTP_PASSWORD for FTP Password.
  7. Click Send Status Update to force the Agent to catch up.


Vusion Database / Agent Pointing to New TMWSuite Database

Should the TMWSuite Database be upgraded but servers remain the same, the Vusion Database and Agent is already setup, but will need to be pointed to the correct TMWSuite Database to continue extracting data copies. The following is if the Vusion Database / Agent are on the same server as TMWSuite Database.

  1. In the Vusion Database SETTINGS table, make sure the DBTMW_SERVER is still blank, and DBTMW_DATABASE is set to the correct upgraded TMW database (name provided by client).
  2. Inside the Vusion Agent SETTINGS, type in
    1. SQL server
    2. Database (is the Vusion database so still should be VusionClient)
    3. Credentials provided by original Vusion email, FTP_USERNAME for FTP Username, FTP_PASSWORD for FTP Password.
  3. Click Send Status Update to force the Agent to catch up.

 

Vusion Database / Agent Moving to New SQL Server different From TMWSuite

Should the Vusion Database and Agent need to be migrated to a new SQL server different from the TMWSuite Database, the client will need to have linked servers set up on SQL for it to work cross server.

  1. Linked SQL Servers will need to be set up for TMWSuite and Vusion to work cross servers.
  2. A backup of the Vusion Database will need to be done so it can be restored after the migration.
  3. Uninstall the Vusion Agent on the server that it currently resides on
  4. Migrate the existing Vusion database to its new location
  5. Install the Vusion Agent on its new server
  6. Configure the newly installed Vusion Agent to point to the TMWSuite Database
    1. In the Vusion Database SETTINGS table, make sure the DBTMW_SERVER is set to the TMWSuite SQL Server name, and DBTMW_DATABASE is still set to the correct TMW database (name provided by client).
  7. Inside the Vusion Agent SETTINGS, type in
    1. SQL server
    2. Database (is the Vusion database so still should be VusionClient)
    3. Credentials provided by original Vusion email, FTP_USERNAME for FTP Username, FTP_PASSWORD for FTP Password.
  8. Click Send Status Update to force the Agent to catch up.