Follow

Migrate Traverse to New Server (Windows)

Note: these instructions are for migrating a combined Traverse BVE/DGE to a new server. Any references to TRAVERSE_HOME should be replaced with the actual Traverse installation directory (e.g. C:\Program Files (x86)\Traverse)

  1. Install the identical Traverse revision on the (new) destination server, as the original server
  2. Stop Traverse software components on the destination server
  3. Stop Traverse software on the (original) source server
  4. Apply any customization from 'TRAVERSE_HOME\etc\emerald.xml' on the source to the same file on the destination server. One way to achieve this is to compare the two files to highlight the differences (e.g. 'diff' or 'compare' commands)
  5. In the rare case that changes have been made to any device signatures in 'etc\typedef', copy the customized device signatures from the source server to overwrite the copies in the destination server.  Altering files in this folder is not recommended as the folder is overwritten during upgrades.
  6. Export the provisioning database from an elevated command prompt (launched with 'Run As Administrator):

    cd TRAVERSE_HOME

    Applicable to only BVE
    utils\databaseUtil.pl --action export --file database\provdb.xml

  7. Copy the following files and folders from source to destination:

    Applicable to a BVE

    TRAVERSE_HOME\database\provdb.xml
    TRAVERSE_HOME\database\mysql\summarydb\
    TRAVERSE_HOME\database\mysql\schedulerdb\
    TRAVERSE_HOME\database\mysql\sladb\
    TRAVERSE_HOME\database\mysql\liveeventsdb\
    TRAVERSE_HOME\database\derby\
    TRAVERSE_HOME\apps\silk\data\
    TRAVERSE_HOME\plugin\

    Applicable to a DGE
    TRAVERSE_HOME\database\mysql\aggregateddatadb\
    TRAVERSE_HOME\database\mysql\processdb\
    TRAVERSE_HOME\apps\silk\data\
    TRAVERSE_HOME\plugin\

    Applicable to a DGEX
    TRAVERSE_HOME\apps\silk\data\
    TRAVERSE_HOME\plugin\

  8. Import the provisioning data from a command prompt (launched with 'Run As Administrator):

    cd TRAVERSE_HOME

    Applicable to only BVE
    utils\databaseUtil.pl --action import --file database\provdb.xml --batch

  9. Restore the MySQL databases:

    cd TRAVERSE_HOME
    net start nvdgedb

    Applicable to only BVE
    apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="SHOW TABLES" --database="liveeventsdb" > tables.txt
    for /F "skip=1" %G IN (tables.txt) DO @apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="REPAIR TABLE %G USE_FRM" liveeventsdb >> logs\database_restore.log

    apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="SHOW TABLES" --database="schedulerdb" > tables.txt
    for /F "skip=1" %G IN (tables.txt) DO @apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="REPAIR TABLE %G USE_FRM" schedulerdb >> logs\database_restore.log

    apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="SHOW TABLES" --database="summarydb" > tables.txt
    for /F "skip=1" %G IN (tables.txt) DO @apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="REPAIR TABLE %G USE_FRM" summarydb >> logs\database_restore.log

    apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="SHOW TABLES" --database="sladb" > tables.txt
    for /F "skip=1" %G IN (tables.txt) DO @apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="REPAIR TABLE %G USE_FRM" sladb >> logs\database_restore.log

    Applicable to only DGE
    apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="SHOW TABLES" --database="aggregateddatadb" > tables.txt
    for /F "skip=1" %G IN (tables.txt) DO @apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="REPAIR TABLE %G USE_FRM" aggregateddatadb >> logs\database_restore.log

    apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="SHOW TABLES" --database="processdb" > tables.txt
    for /F "skip=1" %G IN (tables.txt) DO @apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="REPAIR TABLE %G USE_FRM" processdb >> logs\database_restore.log

  10. cd TRAVERSE_HOME
    utils\db_optimize.pl -r -o
  11. Start the Traverse components on the (new) destination server

 

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

1 Comments

Article is closed for comments.