May 18, 2023

Office 365 Backup, Veeam

Veeam for Microsoft 365: Object reference not set to an instance of an object.

Recently, we have seen an increase in the number of jobs failing with the error message: Object reference not set to an instance of an object. Typically, when a large number of jobs start failing with the same error messages it indicates a backend change from Microsoft is the cause. We’ve opened a Veeam support case to identify a solution to these issues. Veeam support identified the issue as recently discovered and currently being reviewed by the R&D team. In the meantime, a workaround that has worked for us is to edit the backup job to increase the number of retries on jobs encountering this issue. The issue seems to be sporadic, so by increasing the retries the Veeam job will still fail with warnings but then automatically retry for the specified number of retries or until it is successful. For more information on increasing the retries see the Veeam documentation here: https://helpcenter.veeam.com/docs/vbo365/guide/specify_scheduling_options.html?ver=70

Office 365 Backup, Veeam

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

The code (429) in Veeam Backup for Microsoft 365 indicates that you have exceeded the rate limit imposed by Microsoft. It occurs when too many requests are made to Microsoft within a specific time frame. Here are some recommendations in handling the (429) throttling issue: • Upgrade Veeam. Veeam has released Veeam Backup for Microsoft 365 7.0.0.3007 which addresses the (429) warning. • Allow retries. (429) warnings normally clear up on a retry. Retries should be enabled by default. If retries are not enabled, you may turn these on in the last tab of the job settings. • Temporarily disable EWS Throttling Policy. Additional information can be found here at Veeam and Microsoft. If the (429) error persist, please reach out to Managecast. We’re happy to assist in troubleshooting and resolving your issue.

Office 365 Backup, Veeam

Veeam Backup for Microsoft 365 “Failed to find group owner account” error and how to resolve it

The “Failed to find group owner account” error occurs when a Microsoft 365 group does not have an assigned owner. To fix this error, you can follow these steps: Additional information can be found in the Veeam Article KB3105 If you continue to experience issues with your Veeam M365 backups, please reach out to Managecast and we can assist in resolving your issues.

Office 365 Backup, Veeam

What are the Veeam M365 OneDrive was not found/ Personal site was not found warnings and how to resolve or exclude?

Veeam will only backup user OneDrive and Personal site’s only when they have an assigned license. Veeam will present a warning if the Microsoft account does not have a OneDrive or Personal site enabled. You can exclude the Site/OneDrive in Veeam with the following steps depending on how you have set up your backups: 1. Log onto your Veeam M365 Console. 2. Select the job experiencing the warning and Select Edit. 3a. If you are backing up your entire organization, navigate to the Select objects to exclude tab. 4a. Click the Add button to open the users list, select the user(s) that is experiencing the warning, and select click Add. 5a. Select the user and Click the Edit button. Check the OneDrive and/or Site to exclude, hit OK, and save the job settings. 3b. If you have specific users selected to backup, navigate to the Select objects to back up tab 4b. Select the user from the list and click the Edit button. Uncheck the OneDrive and/or Site to exclude, hit OK, and save the job settings. If your warnings are not resolved after making these changes, please reach out to Managecast, and we will be happy to help troubleshoot the issue.

DRaaS, Veeam

Resolving Veeam Cloud Connect Replication Network Detection Warnings.

Veeam Cloud Connect Replication can sometimes complete with one of the following warnings: These warnings can occur with Linux virtual machines, when the virtual machine has multiple network adapters, or when the networking configuration is not set up correctly. No static IP addresses detected for VM, please specify default gateway settings manually. This warning means that Veeam was unable to assign an IP address to the target replica VM. This is typically due to the source being a Linux VM. The following information is from the Veeam documentation and explains this behavior, including a registry key for a workaround. One or more source networks possible were mapped to the same cloud network. Simultaneous partial failover of VMs on these networks may cause issues. This warning means that Veeam wasn’t able to detect the gateway address of the source VM causing it to be unable to automatically determine which failover network to map the production network to. The solutions for this include: Links: Please reach out to Managecast if the warnings persist and we can help troubleshoot and resolve the issue.

Hyper-V, Veeam

Veeam Hyper-V Failed to expand object ‘VM’. Error: Host ‘HOST’ either not a cluster or cluster services is unavailable.

The error message “Veeam Task failed. Failed to expand object VM NAME. Error: Host ‘HOST NAME’ either not a cluster or cluster services is unavailable” typically occurs when Veeam Backup & Replication is unable to communicate with the virtualization host or cluster. Here are some steps you can take to fix this issue: If the error persists, please reach out to Managecast and we can assist in troubleshooting and resolving the issue.

Veeam

Veeam Code: 1072 The specified service has been marked for deletion.

Veeam error code 1072 is related to Volume Shadow Copy Service (VSS) issues on your Windows VM or physical machine. The error message indicates that the VSS writer component has been marked for deletion and cannot be used. Here are some steps you can take to fix the Veeam code: 1072 VSS marked for deletion issue: 1. Restarting the VM. 2. Restart the VSS service 3. Check for other failed VSS writers Please reach out to Managecast if your errors persist and we can assist in troubleshooting and resolving the issue.

Scroll to Top