Veritas Alta™ SaaS Protection Release Notes

1.

Fixed the issue where AWS CLI commands were not functioning properly for EDB compliance copy retrieval.

2.

Fixed the issues where the Audit log connector would persist for days without updating any backup details, giving the appearance of the connector being stuck in a hang state.

3.

Fixed the issue where Custodian search fails when the resulting (ACL) exceeds 65,000 entries.

4.

Fixed the issue of deletion propagation not functioning correctly for EDB Compliance Storage.

5.

Fixed the slow-running EDB to Amazon S3 backup issue.

6.

Fixed the issue where Exchange EWS connectors were backing up incorrect mailboxes when the 'Specific Mailboxes' option was enabled.

7.

Fixed the issue where incremental backup was not functioning for the compliance Stor, while it was operational for the EDB storage in the AWS S3 bucket.

8.

Fixed the issue where, in the event of un-stubbing failure, the items are successfully reverted back to the stub state.

9.

Fixed the issue preventing the addition of an excluded group from the Administration portal.

10.

Fixed the issue preventing the generation of backup task reports for SharePoint connectors.

11.

Fixed the issue preventing the use of Microsoft's personal account for authentication.

12.

Fixed the issue where errors occurring during the restore process are not displayed when the job status is Completed.

13.

Fixed the issue with OneDrive crawls for users who have folders under the 'Forms' folder in the 'Document' library.

14.

Fixed the issue where SharePoint was unable to open files from stubs when custodian groups were configured.

15.

Fixed the issue of displaying incorrect data in the 'stor-compliancestor' folder on the AWS S3 bucket when only the 'Enable EDB Compliance Transformation' option is selected.

16.

Fixed the issue where .PDF, .JPG, .JPGE, PNG, .XLXS, and .PPTX files were inaccessible after retrieval from the EDB ComplianceStor folder.

17.

Fixed the issue of the Content page not loading data and timing out due to API issue.