This section provides overview information on the key data and metadata that should be managed by your enterprise backup and recovery policies.
All backups should be performed in accordance with your enterprise's backup and recovery policies.
Backup Platform Files
The following directories on the Trifacta node should be backed up on a regular basis:
The following directory hosts key configuration files, including
You should backup your license key:
See License Key.
The Trifacta platform utilizes the following PostgreSQL databases as part of normal operations. These databases should be backed up on a regular basis:
|Trifacta DB||Stores users and metadata for flows, including datasets, and recipes.|
|Jobs DB||Stores and maintains job execution status and details.|
|Scheduling DB||Stores metadata for scheduled jobs.|
|Time-based Trigger DB||Additional database required for scheduled jobs.|
For more information on setting up these databases, see Set up the Databases.
The following commands can be used to back up the PostgreSQL databases to a compressed dump file. For more information on command options, see http://www.postgresql.org/docs/9.3/static/backup.html.
Time-Based Trigger DB:
You can schedule nightly execution of these backups using a third-party scheduler such as cron.
To recover the Trifacta platform based on backups:
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.
NOTE: If any of the hosts, pathnames, or credentials have changed since the backups were performed, these updates must be applied through
trifacta-conf.jsonor through the Admin Settings page after the restoration is complete.
- Perform a clean install of the Trifacta software provided in your distribution. See Install.
- Apply any patches or maintenance updates that may have been provided to you. See Maintenance Release Updater.
- Restore the
/opt/trifacta/confdirectory from backup.
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.
(Release 3.2 and later) Jobs database:
(Release 4.1 and later) Scheduling database:
(Release 4.1 and later) Time-based Trigger Service database:
- Restart the platform.
- Login and verify operations. See Verify Operations.
This page has no comments.