Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 71 Next »



Version 5.5 Release Notes

 

Version: 5.5.0.3887
Release Date: August 3, 2023

 

DryvIQ Migrate version 5.5 was available on August 16, 2023. This release focuses on connector updates, license tracking improvements, and bug fixes. Learn more about the release below. For detailed information about individual items, refer to the DryvIQ Migrate Documentation Center.

Updates

  • DryvIQ now supports connection to Hitachi Object Storage for custom S3 implementations. Learn more here.

  • We have optimized how we calculate the volume used, which may cause your volume used to go up slower than it did previously. There will be no retroactive changes to your calculations, but this will affect all jobs run after you upgrade to the 5.5 release. Please see Licensing for additional information on how usage will be calculated going forward.

    You may also notice that there is a new section on the Licensing page for "Govern/Discovery bytes under management.” This section only affects customers using the Govern or Discover products. If you are interested in learning more about what the Govern or Discover products offer, please submit an inquiry here or contact us at 1-888-550-3721.

Fixes

  • For jobs using Google Drive as the source connection, a permission reset will now properly reapply permissions to converted Google Docs.

  • Updates were made to ensure newly uploaded items on the source are transferred on delta runs.

  • If a job that is part of a connection pool contains an invalid URL, the job will not run and will be flagged as “Failed to start.” This message will be listed in the log, and the failed job will not impact the other jobs associated with the connector.

  • Upgrade scripts no longer fail due to a NULL extension.

  • Updates were made to the Box connector to correct an issue where only 100 permissions (collaborations in Box) were being returned.

 

Updating the DryvIQ Platform does not update the Command-line Interface (CLI). If you use the CLI, you should update it when you update to a new version of DryvIQ to ensure the CLI is current. Run the CLI install command to update the CLI.  

  • No labels