365

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 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 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 for Microsoft 365 “Item may have a virus reported by the virus scanner plug-in” warning

Veeam will report when an “Item may have a virus reported by the virus scanner plug-in.” This warning is caused when Veeam for M365 attempts to backup an item that the built-in Microsoft 365 virus protection has flagged as possibly being infected. If you were to attempt to download the file that is reporting the malware/virus you should be met with a “This file is compromised” message: It is recommended that you get your security team involved to investigate if the item has been compromised. Additionally, removing the infected item will clear up the warning in Veeam for M365. Additionally information on Microsoft built-in virus protection can be found HERE. If the item that is reporting as potentially having a virus is downloadable and found to be a healthy file, please reach out to Support@Managecast.com and we can assist in investigating the issue.

Office 365 Backup, Veeam

Veeam Backup for Microsoft 365 “Failed to find Team mailbox owner account”

The “Failed to find Team mailbox owner account” error can be caused by the owner of the mailbox being moved, or if the owner no longer has a licensed assigned. Resolving either of these will also resolve your M365 issues. Here are the steps to resolving the cause to either issue: If the owner was removed from the mailbox: Assigned owner does not have a license: As these are two of the most common causes of the “Failed to find Team mailbox owner account” error, there may be other issues causing the error. If your issues persist, please reach out to Support@Managecast.com for assistance. Additional Microsoft information on assigning a Team mailbox owner can be found HERE, and assigning a license can be found HERE.

Office 365 Backup, Veeam

Veeam for Microsoft 365 Mailbox does not have a valid Microsoft 365 license warnings

Veeam Backup for Microsoft 365 can only backup mailboxes that are licensed*. If a mailbox is selected to backup and does not have a licensed assigned, Veeam will report a warning stating the “Mailbox does not have a valid Microsoft 365 license.” There are two options for resolving the “Mailbox does not have a valid Microsoft 365 license” warning. Option 1: Assign a valid license to the mailbox that you would like to backup. Option 2: If the mailbox does not need to be backed up, then you can exclude the mailbox. Below are the steps to exclude a mailbox: If you are backing up your entire organization: If you have specific objects selected to backup: * Shared and resource mailboxes are the exception, and do not require a license to backup. If the warning persist, or would like any other Veeam assistance, please reach out to Support@Managecast.com

Veeam

Veeam Explorer for Microsoft Exchange Timeouts

A possible issue when restoring a large number of items with the Veeam Explorer for Microsoft Exchange can be operations timing out. Especially when using the advanced search feature in large mailboxes. Error messages related to these timeouts can pop-up during the restore with the following message: Connection to server was unexepectedly close. See log file for details. Error: This request operation sent to net.tcp://127.0.0.1:59148/ArchiverExchangeServiceOrg did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client. In the Veeam Explorer for Exchange log files (C:\ProgramData\Veeam\Backup\ExchangeExplorer\Logs) these errors may also be present: Error: The message could not be transferred within the allotted timeout of 00:01:00. There was no space available in the reliable channel’s transfer window. The time allotted to this operation may have been a portion of a longer timeout. Error: Unable to read data from the transport connection: A blocking operation was interrupted by a call to WSACancelBlockingCall. Error: A blocking operation was interrupted by a call to WSACancelBlockingCall To resolve this issue, the timeout can be increased by editing the Exchange Explorer config.xml file. To do this, follow these steps: Make sure that the Exchange explorer is closed and no restore sessions are running. If you are performing the restore from a Veeam for Microsoft 365 server, make sure no jobs are running and stop the Veeam Services: Next, open a text editor and edit the file: C:\ProgramData\Veeam\Backup\ExchangeExplorer\Config.xml Add the following text between the tags in the file: <WCF OperationTimeout=”3600″ />. Don’t modify any other lines in this file. Example: Finally, save the file and start the Veeam for Microsoft 365 services again. After following these steps try the restore again. The time-out issues should now be resolved.

Scroll to Top