Contact Us

Veeam

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

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 Backup & Replication v10 and Newer Windows backup proxy is missing C++ runtime components error

/

Veeam will display the error message “Backup proxy is missing C++ runtime components” for a different reason depending if you are on a current supported version, or an older unsupported version. If you are still running an unsupported version of Veeam (9.5 and older) please see THIS blog post for steps to resolve the C++ issue. For newer versions of Veeam, this issue is caused when the VDDK libraries on the VMware Backup Proxy fail to load. This occurs when the Veeam Transport Service is missing components on the backup proxy. Repairing the Veeam Backup Transport should resolve the error. Before taking the following steps, please ensure no jobs are running. Once the install has finished, you may re-enable your jobs, and retry any job that was reporting the error. This is the most common reason we see the C++ runtime component occurring but may not resolve every C++ error. If you are continuing to experience issues, please contact Support@Managecast.com for further assistance.

Veeam

Veeam Error “There is not enough space on the disk.”

/

The generic “There is not enough space on the disk” error message is a fairly common and easy issue to investigate and resolve. The error is caused by the backup repository destination storage running out of space for the backup to run. The storage where the backups run differs from standalone agents and backups through your Veeam Backup & Replication console. If you are seeing the error message for a Standalone Veeam Agent backup: If you are seeing the error message for a VM or Machine on Veeam Backup & Replication Console: There may be additional reasons that may be preventing your backups from running. Please reach out to Support@Managecast.com to help troubleshoot and get your backups running successfully.

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

Veeam

Veeam Backup “given key was not present in the dictionary” error

/

We have run into an issue when a job starts reporting the “The given key was not present in the dictionary” error. This seems to occur when a backup is interrupted multiple times. When this isn’t caused by the metadata being corrupted, we’ve been able to be resolve the error by removing the chain, re-importing, and re-mapping the job: 1. Connect to the tenant Veeam backup console.2. Open Home – > Backup Copy Jobs.3. Find your cloud job that processes the backup you want to modify, right-click the job and select Disable. The option can be greyed-out if the job is not scheduled to run at some particular time.4. Open the Home –> Backups –> Cloud view.5. Press and hold the [CTRL] key (please do not release it) and right-click the backup you want to modify.6. Select the Remove from configuration option.7. Open the Backup Infrastructure -> Backup Repositories view.8. In the inventory pane, find the cloud repository where the affected backup is stored, right-click it and select Rescan.During the rescan operation, in the statistics window, you will see that the backup was imported.The modified backup should appear in the Home –> Backups –> Cloud node in the tenant Veeam backup console.9. Open Home –> Backup Copy and find the cloud job associated with this backup.10. Right-click the job, select Edit, proceed to the Storage step of the wizard and select Map backup.11. Select the cloud backup from the cloud repository. Then, click OK to finish mapping.12. Save the settings and enable the job. Then run it or wait for the job to run upon schedule. If this does not resolve the issue, it may point to metadata corruption as the culprit. For further troubleshooting, please reach out to Support@Managecast.com to help get your backups running again.

  • (513) 735 - 6868
  • sales@managecast.com
  • 8354 Princeton Glendale Rd #108
    West Chester, OH 45069
Facebook X-twitter Youtube Linkedin

Powered by Veeam

Veeam Solutions

DRaaS

Resellers & Partners

Support

Blog

About

Scroll to Top