Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Veeam Backup for Microsoft 365 4b cumulative patch KB3119. Please note that Veeam Backup for Microsoft 365 4с is now available and contains all the resolved issues from Veeam Backup for Microsoft 365 4b.
Please confirm you are running Veeam Backup for Microsoft 365 4b (build 4.0.0.2516) prior to installing this cumulative patch KB3119. You can check this under Help > About in Veeam Backup for Microsoft 365 console. After upgrading, your build version will change to 4.0.0.2549. As a result of on-going R&D effort and in response to customer feedback, cumulative patch KB3119 provides a set of enhancements and bug fixes, the most significant of which are listed below: Enhancements The amount of RAM reserved for object storage metadata cache is extended to 512 MB to reduce egress costs associated with retrieving data from an object storage repository. The limitation on the minimum Access Key length required for adding S3 compatible object storage removed. The default setting for applying retention policy to object storage repositories is changed to monthly in order to reduce egress costs. Resolved Issues General Adding Office 365 organizations using U.S. Government plans fails with the “Confidential Client is not supported in Cross Cloud request” error. Working with Office 365 organizations using U.S. Government GCC High plans fails with the “ProtocolError - The remote server returned an error: (403) Forbidden” error. Incremental backup jobs processing OneNote data fails with the “File not found in the database” error. Email notifications on backup job completion results do not include information about users that exceeded the license count. The Veeam.Archiver.Proxy service fails with the “System.TimeoutException: This request operation sent to net.tcp://%IP%port% did not receive a reply within the configured timeout.” error if the Veeam Backup Proxy server is being backed up using a VSS writer. Object storage repositories Moving existing backup data from a local to an object storage repository fails with the “JetError -1011, JET_errOutOfMemory, Out of Memory” error. Moving existing backup data from a local to an object storage repository fails with the “JetError -1101, JET_errOutOfSessions, Out of sessions” error. Under certain conditions, moving existing backup data from a local to an Amazon S3 or an S3 compatible object storage repository fails with the “JetError -1605, JET_errKeyDuplicate, Illegal duplicate key” error. Configuring object storage consumption limit to more than 1TB in the product UI doesn’t apply these changes to the configuration database. Adding an S3 compatible object storage repository fails with the “Failed to request region for bucket %Bucket Name%, bucket skipped” error. Adding an Amazon S3 object storage repository with a bucket in the AWS GovCloud (US) region fails with the “The AWS Access Key Id you provided does not exist in our records” error. The amount of RAM reserved for metadata cache locally when retrieving data from an object storage repository exceeds the expected default size. Backup OneDrive data backup to a repository extended with object storage fails with the “Unspecified Error”. Exchange data backup to a repository extended with object storage fails with the “Specified argument was out of the range of valid values. Parameter name: count” error. Backup to object storage repository fails with the “JetError -1069, JET_errVersionStoreOutOfMemory, Version store out of memory” error. Backup to a repository extended with object storage fails with the “JetError -1311, JET_errTooManyOpenTables” error. Backup of OneNote files retained in the Preservation Hold Library fails with the “Block request failed. (403) Forbidden” error. Restore When exploring backup jobs configured with exclusions, Veeam Explorer for Microsoft SharePoint fails with the “Some backup data is not available” error. Restore of OneDrive accounts which URLs have been changed after the backup job run fails with the “A file or folder with the name %path% already exists” error. Export to PST fails with "Unable to read beyond the end of the stream". REST API The “GET v4/Organizations/{organizationId}/Groups/{groupId}” resource doesn’t return the “managedBy” parameter. PowerShell Under certain conditions, execution of the Get-VBOUsageData PowerShell cmdlet fails with the “Specified cast is not valid” error.
To install the cumulative patch KB3119: Download VBO4b-KB3119.msp. Execute VBO4b-KB3119 as administrator on the Veeam Backup for Microsoft 365 server. If there are any remote proxies in your environment, please update those as described here. NOTE: Veeam Backup for Microsoft 365 RESTful API Service will not be started automatically after the update. Please start it manually to continue using REST API.
DOWNLOAD MD5: 543c44ed9c163034c8215a30ef4ce9a3 SHA-1: 9ad1dbe456f59cdcd8bbbd15e1408cf7face37e3