/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Traverse Traverse

Troubleshooting: exporting the configuration/provisioning database

QUESTION:

How do I export the configuration/provisioning database?

Occasionally, to troubleshoot an issue, the provisioning or configuration database may be required to be reviewed.

SOLUTION:

Please post attachments to an existing support ticket or open a new support ticket.

Please note - <TRAVERSE_HOME> refers to the Traverse installation directory
- replace YYYYMMDD as appropriate with the year, month and date

Additionally, the audit.log from the BVE (<TRAVERSE_HOME>\logs\webapp) will be required to be reviewed.

This process does not require any components to be shut down.

On Windows:

cd <TRAVERSE_HOME>\apps\poet\bin<br>ptxml -export -file provdb-YYYYMMDD.xml -server localhost -base provisioning > provdb-YYYYMMDD.txt 2>&1

The above command creates the provdb backup in <TRAVERSE_HOME>\apps\poet\bin.

To redact the password, please follow the additional instructions below.

Then please zip together and attach

* provdb-YYYYMMDD.xml
* provdb-YYYYMMDD.txt
* <TRAVERSE_HOME>\logs\webapp\audit.log
* <TRAVERSE_HOME>\database\backup\backup_provisioning.xml

to the appropriate support ticket for analysis.

On linux (please note the backtick ` are to be typed in as is for the export LD_LIBRARY_PATH command below):

cd TRAVERSE_HOME/apps/poet/lib # Replace TRAVERSE_HOME with your actual Traverse install folder
export LD_LIBRARY_PATH=`pwd` 
cd ../bin 
./ptxml -export -file /tmp/provdb-YYYYMMDD.xml -server localhost -base provisioning > /tmp/provdb-YYYYMMDD.log 2>&1
cd /tmp 
zip provdb-YYYYMMDD.zip provdb-YYYYMMDD.xml provdb-YYYYMMDD.logsu <br>

To redact the password, please follow the additional instructions below.

Then please tar/compress together and attach

* the provdb-YYYYMMDD.xml
* the provdb-YYYYMMDD.log
* <TRAVERSE_HOME>/logs/webapp/audit.log
* <TRAVERSE_HOME>/database/backup/backup_provisioning.xml

to the appropriate support ticket for analysis.

For version 9.5.187, credentials removal is no longer required as the passwords are now masked in the provisioning database.

Credentials removal:

For security reasons, we recommend after the steps outlined above, to download the attachment and run the following instructions:

Unzip the attachment under <traverse_home>\utils\ (same folder in Linux)
Run in a command line window (shell in Linux):

<traverse_home>\utils\remove_passwords.pl provdb-YYYYMMDD.xml

Note for Linux make this script executable with 'chmod +x remove_passwords.pl'
The output that would be provdb-YYYYMMDD.xml.tmp file with all the passwords altered with the word "redacted"
Repeat this process with TRAVERSE_HOME>/database/backup/backup_provisioning.xml
Kindly zip this file with the rest of the files outlined above (<TRAVERSE_HOME>/logs/webapp/audit.log and the redacted <TRAVERSE_HOME>/database/backup/backup_provisioning.xml)

ATTACHMENT: