Ask the Community
Groups
How to move a DGE extension to a new (upstream) DGE - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>QUESTION:</strong></p> <p>How do I move a DGE extension to a new (upstream) DGE?</p> <p><strong>SOLUTION:</strong></p> <p>The following instructions allow for one or more DGE extensions to be moved from their current upstream DGE to a newly installed DGE. Creating a new DGE for this purpose allows for the retention of existing historical data.</p> <p>To complete the move of one or more DGE extensions from one DGE to another:</p> <ul><li>install new Traverse DGE and reboot</li> <li>stop Traverse components on new DGE</li> <li>delete these folders from the new DGE<br><pre class="code codeBlock" spellcheck="false" tabindex="0">TRAVERSE_HOME\database\mysql\aggregateddatadb\<br>TRAVERSE_HOME\database\mysql\processdb\</pre> </li> <li>provision the new DGE by navigating to Superuser->DGE Mgmt in the Web Application</li> <li> <a rel="nofollow" href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/hc/en-gb/articles/229042248-Tip-Make-a-current-Traverse-database-backup">create a backup</a> of the databases on the existing upstream DGE </li> <li>copy the backup of the historical data from the current upstream DGE to the new DGE<br><br><strong>WINDOWS</strong> </li> </ul><pre class="code codeBlock" spellcheck="false" tabindex="0">TRAVERSE_HOME\database\backup\backup_aggregateddatadb\ ---> TRAVERSE_HOME\database\mysql\aggregateddatadb\<br>TRAVERSE_HOME\database\backup\backup_processdb\ ---> TRAVERSE_HOME\database\mysql\processdb\</pre> <p> <strong>LINUX</strong> - Contact Support</p> <ul><li>restore the historical data on the new DGE:</li> </ul><p><strong>WINDOWS</strong></p> <pre class="code codeBlock" spellcheck="false" tabindex="0">cd TRAVERSE_HOME net start nvdgedb apps\mysql\bin\mysql --defaults-file=etc\mysql.conf --execute="SHOW TABLES" --database="aggregateddatadb" --skip-column-names > tables.txt for /F %G IN (tables.txt) DO <a href="https://kaseya.vanillacommunities.com/profile/apps%5Cmysql%5Cbin%5Cmysql" rel="nofollow">@apps\mysql\bin\mysql</a> --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" --skip-column-names > tables.txt for /F %G IN (tables.txt) DO <a href="https://kaseya.vanillacommunities.com/profile/apps%5Cmysql%5Cbin%5Cmysql" rel="nofollow">@apps\mysql\bin\mysql</a> --defaults-file=etc\mysql.conf --execute="REPAIR TABLE %G USE_FRM" processdb >> logs\database_restore.log</pre> <p><strong>LINUX</strong></p> <pre class="code codeBlock" spellcheck="false" tabindex="0">cd TRAVERSE_HOME etc/dgedb.init start apps/mysql/bin/mysql --defaults-file=etc/mysql.conf --execute="SHOW TABLES" --database="aggregateddatadb" --skip-column-names > /tmp/tables.txt for i in `cat /tmp/tables.txt`; do apps/mysql/bin/mysql --defaults-file=etc/mysql.conf -u root --password= --execute "REPAIR TABLE $i USE_FRM" aggregateddatadb; done apps/mysql/bin/mysql --defaults-file=etc/mysql.conf --execute="SHOW TABLES" --database="processdb" --skip-column-names > /tmp/tables.txt for i in `cat /tmp/tables.txt`; do apps/mysql/bin/mysql --defaults-file=etc/mysql.conf -u root --password= --execute "REPAIR TABLE $i USE_FRM" processdb; done </pre> <ul><li>stop the Traverse components on all the existing DGE extensions to be moved</li> <li>stop the Traverse components on the current upstream DGE</li> <li>stop all the components on the BVE, except for the "Provisioning Database", and “Internal Communication Bus”</li> <li>stop the webapp (if you run it in a separate server)</li> <li>for each DGE extension, issue the command on the BVE to move it;</li> </ul><p><strong>WINDOWS</strong></p> <pre class="code codeBlock" spellcheck="false" tabindex="0">cd TRAVERSE_HOME apps\jre\bin\java -Xmx1024m -XX:-UseSplitVerifier -Dnetvigil.config="%CD%\etc\emerald.properties" -Dlog4j.configuration="file:///%CD%\etc\log4j.conf" -Djava.ext.dirs=webapp\WEB-INF\lib com.zyrion.traverse.utils.MoveDgeExtension "%CD%\etc\emerald.xml" "dge-extension-name" "new-upstream-dge"<br><br></pre> <p><strong>LINUX</strong></p> <pre class="code codeBlock" spellcheck="false" tabindex="0">cd TRAVERSE_HOME<br>database/schema/alter/moveDgeExtension.sh "dge-extension-name" "new-upstream-dge"</pre> <ul><li>start the Web Application</li> <li>navigate to Superuser->DGE Mgmt, select 'update' link for the DGE Extension, and specify the IP address/FQDN of the new upstream DGE</li> <li>stop all the remaining Traverse components on the BVE</li> <li>start all the Traverse components on the BVE</li> <li>start all the components on the original DGE</li> <li>start all the components on the new DGE</li> <li>start all components on the DGE extensions that were moved</li> </ul><h3 data-id="troubleshooting">TROUBLESHOOTING</h3> <p>In case you encounter any issues, please review the following:</p> <ul><li>Check the DGEx services remain 'running'.</li> <li>Check each DGEx is establishing tcp/9443 to the new DGE.</li> </ul><p>- run > netstat -tna | grep 9443</p> <p>- It should be connecting to the IP address of the new DGE.</p> <ul><li>If services do not remain running, check the logs, common errors are:</li> </ul><p> - DGE name in dge.xml does not match the DGE defined via the UI. <br> - IP address of upstream DGE defined in DGEx in UI is incorrect. <br> - Firewall blocking tcp/9443 to new DGE.</p> <ul><li>If all this is verified and correct, and the DGEx is still not connecting, then restart the services on the DGEx</li> </ul><p> </p> <p> </p> </article> </main>