Repository migration support with encryption - trillium_quality - trillium_discovery - Latest

Trillium DQ Release Notes

Product type
Software
Portfolio
Verify
Product family
Trillium™ software
Product
Trillium™ software > Trillium™ Quality
Trillium™ software > Trillium™ Discovery
Version
Latest
ft:locale
en-US
Product name
Trillium Quality and Discovery
ft:title
Trillium DQ Release Notes
Copyright
2024
First publish date
2008
ft:lastEdition
2026-01-30
ft:lastPublication
2026-01-30T16:16:09.403000
L1_Product_Gateway
Verify
L2_Product_Segment
Data Quality
L3_Product_Brand
Precisely Trillium
L4_Investment_Segment
Legacy DQ
Core Data Quality
L5_Product_Group
Legacy DQ - Application
Data Quality - Application
L6_Product_Name
Trillium Quality
Trillium Discovery

Repositories can now be migrated with encryption support on Windows and Linux platforms. The migration support with encryption details for Windows and Linux is provided in the tables below.

Windows migration compatibility matrix

Version Migration Support Migration Support with Encryption
Windows 2016 Migrate existing repositories from version 15.7.4 to 18.0

Migrating existing non-encrypted repositories to an encrypted repository is supported from version 15.7.4 to version 18.0.

Windows 2016 and Windows 2019 Migrate existing repositories from version 16.1 to 18.0 Migrating existing non-encrypted repositories to an encrypted repository is supported from version 16.1 to version 18.0.
Windows 11, Windows 2016, Windows 2019, and Windows 2022 Migrate existing repositories from version 17.1 to 18.0 Migrating existing non-encrypted repositories to an encrypted repository is supported from version 17.1 to version 18.0.

Windows 11, Windows 2016, Windows 2019, and Windows 2022

Migrate existing repositories from version 17.2 and 17.3 to 18.0

  • Migrating existing non-encrypted repositories to an encrypted repository is supported from versions 17.2 and 17.3 to version 18.0.
  • Migrating existing encrypted repositories to encrypted repository is supported from version 17.2 to 18.0.
  • Migrating existing encrypted repositories to non-encrypted repository is not supported.

Linux migration compatibility matrix

Version Migration Support Migration Support with Encryption
Linux RH 7

Version 18.0 is not supported on RH7. It can only be supported by using the cross-platform migration method to migrate from versions 15.7.4, 15.8.2, 16.1, 17.0.0, 17.0.1 and 17.1 to version 18.0.

Version 18.0 is not supported on RH7. It can only be supported by using the cross-platform migration method.
Linux RH 8

Migrate existing repositories from version 17.0.1 and 17.1 to 18.0

  • Migrating existing non-encrypted repositories to an encrypted repository is supported from versions 17.0.1 and 17.1 to version 18.0.
  • Migrating existing encrypted repositories to non-encrypted repository is not supported.
Linux RH 8

Migrate existing repositories from version 17.2 and 17.3 to 18.0

  • Migrating existing non-encrypted repositories to an encrypted repository is supported from versions 17.2 and 17.3 to version 18.0.
  • Migrating existing encrypted repositories to encrypted repository is supported from version 17.2 and 17.3 to version 18.0.
  • Migrating existing encrypted repositories to non-encrypted repository is not supported.
Linux RH 9 Migrate existing repositories from version 17.2 and 17.3 to 18.0
  • Migrating existing non-encrypted repositories to an encrypted repository is supported from versions 17.2 and 17.3 to version 18.0.
  • Migrating existing encrypted repositories to encrypted repository is supported from version 17.2 and 17.3 to version 18.0.
  • Migrating existing encrypted repositories to non-encrypted repository is not supported.
SuSE Linux 15.x+ Migrate existing repositories from version 17.2 and 17.3 to 18.0
  • Migrating existing non-encrypted repositories to an encrypted repository is supported from versions 17.2 and 17.3 to version 18.0.
  • Migrating existing encrypted repositories to encrypted repository is supported from version 17.2 and 17.3 to version 18.0.
  • Migrating existing encrypted repositories to non-encrypted repository is not supported.