M365

Office 365 Backup, Veeam

Managing What You Backup Through the Portal with Veeam Backup for Microsoft 365

Most of the time, a full organization backup fits the needs of most users. However, there are times when you need to select specific mailboxes and groups to back up. Through the backup portal, selecting exactly what you need is made easy. First, it may help to check what you are currently backing up. If you are setting up a job for the first time, you can skip this step. You can find this information under the Reports section by selecting Licensed Users: Once you’ve identified the critical accounts that must be backed up, you can edit your job. In the portal, navigate to the Jobs tab. Ensure your company is selected in the drop-down menu (or if managing multiple tenants, select the company you wish to edit) and select the job you want to edit. To enable the ability to select specific objects, select the Backup the following objects option when editing the job. Note: These steps can be done when setting up your initial backup job as well. Once selected, there are two ways to add these users: Option 1: Per Group. This is the easiest way of managing what is backed up. Clicking the Add button and selecting Groups will bring up a full list of Groups in your environment. Creating a group specifically for backups is a simple way of ensuring the users that need to be backed up are backed up. Existing groups can be added, but we recommend managing a single group instead of multiple. Option 2: Per User. If you have a need to select specific users, perhaps to ensure you are not over X number of licenses, then this may be your best option. Clicking the Add button and selecting Users will bring up a full list of users in your environment. Here, you can select exactly which users you would like to backup.  Additionally, you can select specific Sites and Teams to backup. If you ever need to exclude a user, or a user object (OneDrive, Site, Teams), from a backup, this can be done on the very next screen. The most common reason to exclude a user is if a user in a selected group does not need to be backed up. Identical to adding a user, excluding a user, or any other object is done by selecting the Add button, choosing the type of object you want to exclude, and selecting it from the list. On special occasions, only a single user, group, site, or Teams needs to be excluded. For example, a user may need their mail backed up, but not their OneDrive. In this situation, just like above, you would select the user that needs to be excluded. Once selected, click on the users and press the Edit button. Here, you can select what objects you would like to exclude: Once all the changes have been made, finish the wizard and Save the job settings. That’s all there is to it! As always, if you ever need assistance, we are here to help answer any questions or assist with your backups. Please reach out to Support@Managecast.com for more information, questions, or assistance.

Office 365 Backup, Veeam

Veeam for Microsoft 365 Backing Up Public Mailboxes Limitations and Settings

Veeam has added the ability to backup public folders again, but with a few setting changes and limitations that you may run into. Here are a list of some of these that you may run into or need to adjust: Additionally Veeam information on public folders can be found HERE. Microsoft is constantly pushing changes that may affect the backups. These are just some things to check when trying to backup a public folder. If you continue to run into issue, reach out to Support@Managecast.com for assistance.

Office 365 Backup, Veeam

Veeam for Microsoft 365 Not allowed to access Non IPM folder Error

Microsoft constantly pushes out changes, and sometimes these changes break things for 3rd party vendors. After a recent change, we had started seeing the error message “Failed to get folder properties. Not allowed to access Non IPM folder” across several backups. The Microsoft change to the properties of the TeamsMessagesData folder caused Veeam to be unable to retrieve the data over the EWS APIs. Luckily, the fix for this a quick and easy! Note: This requires you to be on Veeam for Microsoft 365 6.1.0.1015 or Newer. Implementing the change on prior versions will NOT resolve the issue. We recommend upgrading to a supported version before applying the following fix. Recent Veeam for Microsoft 365 releases cover this issue. Please follow these steps: If you continue to experience issues or would like assistance with any other issues you may be experience, please reach out to Support@Managecast.com.

Office 365 Backup, Veeam

Veeam for Microsoft 365 Invalid Serialized Stream, Unknown Opcode Found:4 error

A recent Microsoft change to the Serialized Property of Exchanges items have caused “Invalid ‘serialized stream, unknown opcode found: 4’” errors across Veeam for Microsoft 365 users. This issue has been resolved with new hotfixes for users on versions 7.0.0.4551 and 7.1.0.1401. Below are the KB links to download the hotfix that pertains to your environment: Hotfix for 7.0.0.4551 P20231218 Hotfix for 7.1.0.1401 P20231218 To install the hotfix, follow these quick steps: If you continue to experience the error, would like assistance with the hotfix, or have any other backup replated questions, please reach out to Support@Managecast.com.

Office 365 Backup, Veeam

Veeam for Microsoft 365 What’s unsupported after the deprecation of basic authentication?

After Microsoft’s decision to deprecate basic authentication in favor of modern authentication, there are a few things that will change when switching from basic to modern. Below are items that are not supported through modern app-only authentication, and support that has been added in newer releases: Further information on what is/is not supported when switching to modern authentication can be found here KB3146. If you would like assistance, or have any further questions on what is supported, please email Support@Managecast.com.

Office 365 Backup, Veeam

Veeam Backup for Microsoft 365 “objects types are unsupported in the modern app-only authentication mode”

After Microsoft’s deprecation of basic authentication, item’s that were excluded that aren’t supported in modern app-only authentication mode will raise a warning. The warning will specify, “Found # excluded objects. Some of the objects specified for exclusion will be ignored during processing because such objects types are unsupported in the modern app-only authentication mode.” If you are unsure what is no logner supported, you can check HERE. To resolve this warning: If you continue to experience issues with your M365 job, or any Veeam issue, please reach out to Support@Managecast.com.

Office 365 Backup, Veeam

Veeam for Microsoft 365 “Download request retry timeout exceeded” error

Recently we have begun seeing the “Failed to backup item: FILEPATH, Download request retry timeout exceeded” error appear in jobs backing up OneDrive. Recent changes on the Microsoft side have begun preventing OneNote notebooks from being able to be downloaded. This prevents Veeam from being able to request and download the file to backup. We have an active case open with Veeam while they work with Microsoft to resolve this issue. We will update this post once Veeam and Microsoft have provided a public workaround or hotfix. Information on the issue can also be found here in KB4529. For additional assistance, please reach out to Support@Managecast.com.

Office 365 Backup, Veeam

Veeam Microsoft 365 XML document and Specific SharingMessage type not recognised errors

During early December we began noticing two errors pop up. The messages “There is an error in XML document” and “The specific type was not recognized: name: ‘SharingMessage’” were caused by a minor Microsoft change. The changes were to the structure of the XML message received from M365 referencing the SharingMessageType property received from EWS. This change to the structure was unable to be processed by Veeam when the change occurred. However, Veeam has already pushed out patches to resolve the issue. Here are the two patches provided by Veeam: Veeam Backup for Microsoft 365 7.0 Cumulative Patch 7.0.0.4551 (P20231218) Veeam Backup for Microsoft 365 7a Cumulative Patch 7.1.0.1401 P20231218. Any newer version downloaded and installed will have the patch included. If you continue to run into any issues, have any questions, or need any other assistance, please reach out to Support@Managecast.com

Office 365 Backup, Veeam

Veeam for Microsoft 365 Item has been changed during the backup warning

The warning “Item has been changed during the backup” occurs when a file is in use during a Veeam Backup for Microsoft 365 backup, Veeam will skip the file and try to backup it up during the next run. Here are a few tips to help get your file backing up. These are common steps we follow to help get items backing up after the warning has occurred. If your issues continue to occur, or would like assistance for any other issues, please reach out for assistance at Support@Managecast.com.

Office 365 Backup, Veeam

Veeam Backup for Microsoft 365 SharePoint “The remote server returned an error: (429)”

The nuisance error, “The remote server returned an error: (429)” in Veeam Backup for Microsoft 365 indicates that you have exceeded the request rate limit imposed by Microsoft. This occurs when too many requests are made to Microsoft within a specific time frame. We commonly see this during the initial Veeam for M365 backup and the error resolves itself during the automatic retry, which is enabled by default. If you would like to make changes on the backend in Microsoft, such as editing Retry-After headers or decorating traffic, you may refer to this Microsoft Article on how to avoid getting throttled in SharePoint. If the (429) error persist, please reach out to us at Support@Managecast.com. We’re happy to assist in troubleshooting and resolving your issue.

Scroll to Top