Warning

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 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.

Replication, Veeam

Veeam Replication Latest Available Restore Point is Already Replicated

The replication warning “Latest available restore point is already replicated” appears when the replication job that’s sourced from a backup/backup copy attempts to run, but there is no new restore point to grab new data from. Here are a few reasons that may cause new data not to be available to replicate: These are some of the most common reasons we find that cause the “already replicated’ warning to occur. Veeam, replication, and virtualization are complex, so there are many reasons this may occur. If you are still seeing the warning pop up, please reach out to Support@Managecast.com for further assistance.

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.

Veeam

Veeam Agent for Windows “Sending e-mail report Details: The remote certificate is invalid according to the validation procedure”

When a certificate change to the SMTP server that your Veeam agent uses to send out notifications occurs, the notifications may start failing to send. Your jobs will begin displaying the warning message, “Sending e-mail report Details: The remote certificate is invalid according to the validation procedure.” This can be easily resolved by running through the email notification settings and testing that it can connect. 2. In the Configure and test email notifications window, verify and test your SMTP email settings. Selecting Test Now will test the current settings. 3. If the Test Now fails, you may need to make a change to warrant Veeam to rescan the certificate. Veeam will only rescan the certificate if a change has been made here. Clicking the Mail server drop down, switch it to one of the other options, then switch back is a significant enough to warrant a rescan. Click Apply to initiate the rescan. 4. You should be met with an alert stating that the certificates are mismatched. Continue through the certificate window. Run the Test Now option to verify Veeam can now connect. There may be other reasons that could be interrupting the communication between your Veeam Backup Agent for Windows and the SMTP server. If you would like further assistance please contact 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.

Veeam

Veeam “Unable to connect to SMTP server because of invalid credentials or connection settings”

From time to time, there are changes and updates to your SMTP server that may adversely affect you nightly reports. Your jobs will start throwing Sending e-mail report warnings that Veeam is “Unable to connect to SMTP server because of invalid credentials or connection settings” and/or “the remote certificate is invalid according to the validation procedure.” Resolving the SMTP warning is quick and easy as long as you know where to look. Here are the quick steps to checking and re-accepting the SMTP certificate: There may be other reasons that could be interrupting the communication between your Veeam backup server and the SMTP server. If you would like further assistance please contact Support@Managecast.com.

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