Release 5.1
Page tree


Support | Blog | Contact Us 

Versions Compared

Old Version 3

changes.mady.by.user docuser1

Saved on

compared with

New Version Current

changes.mady.by.user docuser1

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DEV and version next

 

D toc

D s install marketplace

...

https://raw.githubusercontent.com/trifacta/trifacta-utils/release/5.0/azure/trifacta-backup-config-and-db.sh

  • Example command to download the script:

    • Excerpt

    Please complete the instructions in this section if you are upgrading from version 5.0 of 

    D s product
    rtrue
    . 

    Info

    NOTE: These instructions apply only to

    D s product
    rtrue
     available through the Azure Marketplace.

     

    Before You Begin

    Before you upgrade, please do the following:

    Steps:

    1. Login as an admin to the application.
    2. From the left nav bar, select Settings > Admin Settings.

    3. Locate the following parameter:

      Code Block
      azure.wasb.defaultStore.sasTokenId
    4. Store the current value for safekeeping. It must be applied again to a new parameter after upgrade.

    Overview

    Upgrading your instance of 

    D s product
     for Azure follows these basic steps:

    1. Back up the databases and configuration for your existing platform instance.
    2. Download the latest version of 
      D s product
    3. Uninstall the existing version of 
      D s product
      . Install the version you downloaded in the previous step.
    4. Upgrade the databases.
    5. Start up 
      D s product
      . This step automatically upgrades the configurations. 
    6. Within the application, perform required configuration updates in the upgraded instance.

    Instructions for these steps are provided below. 

    Backup

    Before you begin, you should backup your current instance.

    1. SSH to your current Marketplace instance.

    2. Stop the 

      D s platform
       on your current Marketplace instance:

      Code Block
      sudo service trifacta stop
    3. Update the backup script with a more current version.

      1. If you have not done so already, download 5.0.0 backup script from the following location:

    Code Block
    D s property overflow

    Code Block
    curl --output trifacta-backup-config-and-db.sh \
https://raw.githubusercontent.com/trifacta/trifacta-utils/release/5.0/azure/trifacta-backup-config-and-db.sh

  • Overwrite the downloaded script to the following location:

    Code Block
    /opt/trifacta/bin/setup-utils/trifacta-backup-config-and-db.sh

  • Verify that this script is executable: 

    Code Block
    sudo chmod 775 /opt/trifacta/bin/setup-utils/trifacta-backup-config-and-db.sh

  • Run the backup script:

    Code Block
    sudo /opt/trifacta/bin/setup-utils/trifacta-backup-config-and-db.sh

     

    1. /

      When the script is complete, the output identifies the location of the backup. Example:

      Code Block

      opt/trifacta-backups/trifacta-backup-5.0.0+110.20180615100731.e4ded4d-20181211213601.tgz

  • Store the backup in a safe location. 

    • Download software

    Download the latest version by using the command below

    code

    :

    wget

    'https://trifactamarketplace.blob.core.windows.net/artifacts/trifacta-server-5.1.0m5-120~xenial_amd64.deb?sr=c&si=trifacta-deploy-public-read&sig=ksMPhDkLpJYPEXnRNp4vAdo6QQ9ulpP%2BM4Gsi/nea%2Bg%3D&sv=2016-05-31'

    -O

    trifacta-server-5.1.0m5-120~xenial_amd64.deb

    Uninstall and install software

    Uninstall old version

    To uninstall older version of 

    D s product
    rtrue
    , execute as root user the following command on the 
    D s item
    itemnode
    :

    Code Block
    apt-get remove trifacta

    Upgrade components

    Upgrade supervisor package:

    Code Block
    apt-get install supervisor=3.2.4

    Excerpt Include
    Upgrade the Databases
    Upgrade the Databases
    nopaneltrue

    Install new version

    Install the latest version that was downloaded. Execute the following command as root:

    Code Block
    dpkg -i <location of the 5.1 deb file>

     

    Start up platform

    To migrate the DBs and upgrade configs from the older version of 

    D s product
    rtrue
     to the latest version, the platform needs to be started. To start the 
    D s platform
     on the instance:

    Code Block
    service trifacta start

    Platform Configuration

    Change database ports

    The database version is PostgreSQL 9.6, which uses a different port number than the previous version. You must verify that the platform is using the appropriate port number to access the databases.

     

    Steps:

    1. Login to the
      D s item
      itemnode
      .

    2. Edit the following file:

      Code Block
      /etc/postgresql/9.6/main/postgresql.conf
    3. Locate the listed database port number. Typically, this value is 5433.
    4. Close the file.
    5. D s config
      methodt

    6. Locate the following parameters, which define the port numbers used by each

      D s item
      itemdatabase
      . The values below are the defaults but may be different:

      Info

      NOTE: All databases should use the same port number.

      Code Block
      "webapp.db.port" = 5433;
...
"batch-job-runner.db.port" = 5433;
...
"scheduling-service.database.port" = 5433;
...
"time-based-trigger-service.database.port" = 5433;

    7. The above values should be updated with the value from the postgresql.conf file, if they differ.

    8. Save and close the file.

    Reconfigure use of Key Vault for WASB access

    Info

    NOTE: This section applies only if you are upgrading Release 5.1 or later.

    Beginning in Release 5.1, you can configure the platform to access WASB using configuration stored in the

    D s item
    itemconfiguration
    , including the SAS token.

    In your pre-upgrade environment, if you enabled WASB access through a Key Vault, you must set the following property to true. This property is new in Release 5.1 and defaults to false.

    Steps:

    1. D s config

    2. Locate and set the following property to true:

      Code Block
      "azure.wasb.fetchSasTokensFromKeyVault": true

    3. Locate your saved value for azure.wasb.defaultStore.sasTokenId. Set the following property to the saved value:

      Code Block
      "azure.wasb.defaultStore.keyVaultSasTokenSecretName"
    4. Save your changes.

    No other configuration is required to enable your previous WASB access.

     

    Storage protocol wasb replaced by wasbs

    Info

    NOTE: This section applies to upgrades to Release 5.1 and later.

    Beginning in Release 5.1, the wasb: storage protocol is no longer supported. All interactions with WASB are managed through wasbs: at this point, using the SAS token that must be created for all environments using WASB as the base storage layer.

    Info

    NOTE: If you created any External Datasources for a SQL DW connection using the wasb: protocol before you upgraded, then you must recreate them using the wasbs: protocol in your upgraded instance. See Create SQL DW Connections.

    Verify 

    The upgrade is complete. To verify:

    Steps:

    1. Restart the platform:

      Code Block
      sudo service trifacta start
    2. Run a simple job with profiling. 
    3. Verify that the job has successfully completed. 
      1. In the Jobs page, locate the job results. See Jobs Page.
      2. Click View Details next to the job to review the profile.

    ...

    © 2013-2023 Alteryx® Inc Privacy Policy  |  Terms of Use