New Direct Access gateway version (1.7.2)

Direct Access gateway 1.7.2 introduces the ability to set a chunk recovery resume threshold, and resolves several issues. To benefit from the enhancements and resolved issues, customers are encouraged to upgrade at the earliest opportunity. For upgrade instructions and a list of resolved issues, see Upgrading the Direct Access gateway installation

Setting a chunk recovery resume threshold

You can now set a threshold (in minutes) for the chunks recovery duration. If the reload has not resumed by the time the recovery duration threshold has been reached, it will fail with an appropriate message.

This option is useful for reloads that might otherwise exceed the three hour limit, following a long recovery. For example, let’s say it takes 90 minutes to retrieve the data from the database, but as soon as the reload starts, one of the chunks is corrupted. In this case, all of the chunks will be stored in the cache, and sent from the cache. In such a scenario, the entire reload process (storing in cache + actual reload) could take three hours to complete.

See also Setting a chunk recovery resume threshold.