Page tree

Versions Compared

Key

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

...

Excerpt

In the event that an upgrade or hotfix to your instance of the 

D s platform
rtrue
 has run into issues that cannot be repaired in the upgraded instance, you can follow the steps in this section to rollback to your previous version.

Info

NOTE: Before you perform a rollback, you should review the set of issues with

D s company
first. For more information, please contact
D s support
.

Pre-requisites

In order to complete the rollback in a timely manner, please verify that you have access to the following:

Access

You must:

  • Acquire root user access to the 
    D s node
    .
  • Acquire database access to uninstall and reinstall the 
    D s item
    itemdatabases
    .
Tip

Tip: You should communicate to any affected users the required maintenance and expected outage window.

Backups

Warning

If you do not have the following, you cannot perform a rollback. These items cannot be acquired from

D s company
.

  • Backups of your pre-upgrade 
    D s item
    itemconfiguration files
  • Backups of your pre-upgrade 
    D s item
    itemdatabases

The following can be acquired from 

D s company
 if you do not have them:

  • RPM installers for the previous version. If any Hotfixes have been applied to the previous version, you should acquire and use the latest Hotfix RPM for your re-install.
  • PDF documentation for the previous version.


Rollback Steps

To recover the 

D s platform
 based on backups:

Info

NOTE: When the databases are restored, internal identifiers such as job IDs, are reset in an order that may not correspond to the expected order. Consequently, references to specific identifiers may be corrupted. After restoring the databases, you should clear the job logs.

Info

NOTE: If any of the hosts, pathnames, or credentials have changed since the backups were performed, these updates must be applied through

D s triconf
or through the Admin Settings page after the restoration is complete.

Steps:

  1. Login to the 

    D s node
     as root user.

  2. Stop the 

    D s item
    service
    service
    :

    Code Block
    service trifacta stop
  3. Clear each current database and restore the backup of the version from the preceding release. In some cases, the database may not exist in the previous version.
    1. PostgreSQL:

      1. Login as a user that can run admin commands for PostgreSQL. This user may vary between deployments.

      2. D s item
        itemdatabase
        :

        Code Block
        psql -c "DROP DATABASE trifacta;"
        psql -c "CREATE DATABASE trifacta WITH OWNER trifacta;"
        psql --dbname=trifacta < trif_triDB_bkp_<date>.sql
      3. (Release 3.2 and later) Jobs database:

        Info

        NOTE: Please note the escaped quotes in the CREATE DATABASE command for this database.

        Code Block
        psql -c "DROP DATABASE \"trifacta-activiti\";"
        psql -c "CREATE DATABASE \"trifacta-activiti\" WITH OWNER trifactaactivit;"
        psql --dbname="trifacta-activiti" < trif_actDB_bkp_<date>.sql
      4. (Release 4.1 and later) Scheduling database:

        Code Block
        psql -c "DROP DATABASE trifactaschedulingservice;"
        psql -c "CREATE DATABASE trifactaschedulingservice WITH OWNER trifactascheduling;"
        psql --dbname=trifactaschedulingservice < trif_schDB_bkup_<date>.sql
        
      5. (Release 4.1 and later) Time-based Trigger Service database:

        Code Block
        psql -c "DROP DATABASE trifactatimebasedtriggerservice;"
        psql -c "CREATE DATABASE trifactatimebasedtriggerservice WITH OWNER trifactatimebasedtriggerservice;"
        psql --dbname=trifactatimebasedtriggerservice < trif_tbtsDB_bkup_<date>.sql
      6. (Release 6.0 and later) Configuration Service database:

        Code Block
        psql -c "DROP DATABASE trifactaconfigurationservice;"
        psql -c "CREATE DATABASE trifactaconfigurationservice WITH OWNER trifactaconfigurationservice;"
        psql --dbname=trifactaconfigurationservice < trif_confservDB_bkup_<date>.sql
      7. (Release 6.0 and later) Artifact Storage Service database:

        Code Block
        psql -c "DROP DATABASE trifactaartifactstorageservice;"
        psql -c "CREATE DATABASE trifactaartifactstorageservice WITH OWNER trifactaartifactstorageservice;"
        psql --dbname=trifactaartifactstorageservice < trif_artifactstorageservDB_bkup_<date>.sql
      8. (Release 6.4 and later) Job Metadata Service database:

        Code Block
        psql -c "DROP DATABASE trifactajobmetadataservice;"
        psql -c "CREATE DATABASE trifactajobmetadataservice WITH OWNER trifactajobmetadataservice;"
        psql --dbname=trifactajobmetadataservice < trif_jobmetadataservDB_bkup_<date>.sql
      9. (Release 7.1 and later) Authorization Service database:

        Code Block
        psql -c "DROP DATABASE trifactaauthorizationservice;"
        psql -c "CREATE DATABASE trifactaauthorizationservice WITH OWNER trifactaauthorizationservice;"
        psql --dbname=trifactaauthorizationservice < trif_authorizationservDB_bkup_<date>.sql
      10. (Release 7.1 and later) Orchestration Service database:

        Code Block
        psql -c "DROP DATABASE trifactaorchestrationservice;"
        psql -c "CREATE DATABASE trifactaorchestrationservice WITH OWNER trifactaorchestrationservice;"
        psql --dbname=trifactaorchestrationservice < trif_orchestrationservDB_bkup_<date>.sql
    2. MySQL: For details, see https://dev.mysql.com/doc/refman/5.7/en/reloading-sql-format-dumps.html. 
      1. Login:

        Code Block
        su - mysql
      2. D s item
        itemdatabase
        :

        Code Block
        mysql trifacta < trif_triDB_bkp_<date>.sql
      3. Jobs database:

        Code Block
        mysql trifacta-activiti < trif_actDB_bkp_<date>.sql
      4. (Release 4.1 and later) Scheduling database:

        Code Block
        mysql trifactaschedulingservice < trif_schDB_bkup_<date>.sql
      5. (Release 4.1 and later) Time-based Trigger Service database:

        Code Block
        mysql trifactatimebasedtriggerservice < trif_tbtsDB_bkup_<date>.sql
      6. (Release 6.0 and later) Configuration Service database:

        Code Block
        mysql trifactaconfigurationservice < trif_confservDB_bkup_<date>.sql
      7. (Release 6.0 and later) Artifact Storage Service database:

        Code Block
        mysql trifactaartifactstorageservice < trif_artifactstorageservDB_bkup_<date>.sql
      8. (Release 6.4 and later) Job Metadata Service database:

        Code Block
        mysql trifactajobmetadataservice < trif_jobmetadataservDB_bkup_<date>.sql
      9. (Release 7.1 and later) Authorization Service database:

        Code Block
        mysql trifactaauthorizationservice < trif_authorizationservDB_bkup_<date>.sql
      10. (Release 7.1 and later) Orchestration Service database:

        Code Block
        mysql trifactaorchestrationservice < trif_orchestrationservDB_bkup_<date>.sql
  4. Uninstall the current version of the 
    D s item
    itemsoftware
    :
    D excerpt include
    pageUninstall
    nopaneltrue
  5. Perform a clean install of the 
    D s item
    itemsoftware
     provided in your distribution. See Install.
  6. Restore your configuration files. The following commands assume that they were backed up to the /tmp directory on the node:

    Code Block
    cp /tmp/trifacta-conf.json  /opt/trifacta/conf/trifacta-conf.json
    cp /tmp/env.sh /opt/trifacta/conf/env.sh
    cp /tmp/trifacta.service /etc/init.d/trifacta
    
  7. Apply any patches or maintenance updates that may have been provided to you.See Maintenance Release Updater.

  8. Restart the platform.See Start and Stop the Platform.

  9. Login and verify operations.See Verify Operations.