Follow

Migrate Traverse to New Windows Server

Note: 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 (source) server
  2. Stop Traverse software components on the destination server.
  3. 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 and note the differences (e.g. 'diff' or 'compare' commands).
  4. 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.
  5. Copy the license key (TRAVERSE_HOME\etc\licenseKey.xml) from source to destination server.
  6. Create a backup of the databases on the source server.
  7. Delete the database folders from the destination server:

    cd TRAVERSE_HOME
    del /q TRAVERSE_HOME\database\mysql\*

  8. Copy the archived historical data from the source server backup location to the destination server, overwriting the live folders on the destination:

    Applicable to BVE only
    TRAVERSE_HOME\database\backup\backup_liveeventsdb\    ---> TRAVERSE_HOME\database\mysql\liveeventsdb\
    TRAVERSE_HOME\database\backup\backup_schedulerdb\ ---> TRAVERSE_HOME\database\mysql\schedulerdb\ TRAVERSE_HOME\database\backup\backup_sladb\ ---> TRAVERSE_HOME\database\mysql\sladb\ TRAVERSE_HOME\database\backup\backup_summarydb\ ---> TRAVERSE_HOME\database\mysql\summarydb\ TRAVERSE_HOME\database\backup\backup_provisioning.xml ---> TRAVERSE_HOME\database\backup\
    Applicable to DGE only
    TRAVERSE_HOME\database\backup\backup_aggregateddatadb\ ---> TRAVERSE_HOME\database\mysql\aggregateddatadb\
    TRAVERSE_HOME\database\backup\backup_processdb\        ---> TRAVERSE_HOME\database\mysql\processdb\ 
  9. If server is a BVE, copy these folders from source to destination:

    TRAVERSE_HOME\database\derby\
    TRAVERSE_HOME\plugin\ 
  10. If the server is a DGE or DGE extension, copy these folders from source to destination:

    TRAVERSE_HOME\apps\silk\data\
  11. If server is a BVE, import the provisioning data from a command prompt on the destination server (launched with 'Run As Administrator):
    cd TRAVERSE_HOME
    utils\databaseUtil.pl --action import --file database\backup\backup_provisioning.xml --batch
  12. Restore the MySQL databases on the destination server:
    cd TRAVERSE_HOME
    net start nvdgedb

    Applicable to BVE only

    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 DGE only

    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
  13. If server is a BVE, restore the Derby Database on the destination:
    cd TRAVERSE_HOME
    del database\derby\netconf\log\* database\derby\netconf\db.lck
  14. Optimize the MySQL databases, unless server is a DGE extension:
    cd TRAVERSE_HOME
    utils\db_optimize.pl -r
  15. Stop Traverse on the source server, and ensure that all components are down before proceeding.
  16. Start the Traverse components on the (new) destination server.
  17. After verifying that the new server is performing as expected, uninstall Traverse from the source server.

 

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

1 Comments

Please sign in to leave a comment.