November 8, 2024

Office 365 Backup, Veeam

“Processed by Another Job” Warning in Veeam M365 Backups

The “Processed by Another Job” warning in Veeam M365 backups appears when multiple backup jobs attempt to back up the same Microsoft 365 object (such as mailboxes, SharePoint sites, or OneDrive accounts). When Veeam detects that an object is already being processed or backed up by another job, it flags this warning to avoid redundant operations and potential data consistency issues. This warning typically occurs due to overlapping backup job configurations. You may have multiple backup jobs configured to protect the same set of mailboxes, SharePoint sites, or OneDrive accounts. For example, if one job is set to back up all mailboxes in your organization and another job targets a specific department that includes those same mailboxes, a conflict arises. Best Practices to Address the Warning Review Your Backup Job Configurations Schedule Jobs to Avoid Overlap Fortunately, the “Processed by Another Job” warning does not typically indicate a critical issue. Veeam intelligently manages the backup process to ensure that each object is protected only once, even if it’s referenced in multiple jobs. This warning serves as an alert that your configuration may need to be optimized to avoid inefficiencies or unnecessary resource consumption. If you have any questions or need assistance with your Veeam M365 backups, feel free to reach out to us at support@managecast.com. We’re happy to assist with troubleshooting and resolving your issue.

Veeam

Veeam I/O filter for CDP fails to install on ESXi 6.x 

Introduction  When installing the Veeam Continuous Data Protection (CDP) I/O filter on an ESXi 6.x cluster, the installation may fail with a generic error message that the install failed.  The Issue  This can often be caused by a certificate signing issue with older versions of ESXi 6.x. Per VMware/Broadcom documentation: https://knowledge.broadcom.com/external/article?legacyId=76555 More details about this issue can sometimes be found in the I_O_filter_deployment.log:  Solutions  There are two solutions for this issue:  Solution 1: Upgrade ESXi Version (Recommended)  VMware recommends upgrading to a later release of ESXi.  Version 7 or 8 have been known to work without issues.  Solution 2: Manual VIB Installation on ESXi Hosts   The other solution is to manually install the VIB on the ESXi hosts via SSH and the command line.  It is important to note that the VIB must be installed on all ESXi hosts in each cluster that will be using CDP.  CDP is installed at the cluster level.  After installing the VIB manually, run the Veeam I/O filter install again; it should already see the I/O filter installed and up-to-date, and it will just run the install process again and it should succeed since the I/O filter is already properly installed.  To install the VIB manually on an ESXi host, follow these steps:  1. Locate the VIB files on the Veeam server:  On the Veeam backup server, in the following directory by default:  C:\Program Files\Veeam\Backup and Replication\Backup\Packages  There will be three files that all start with veecdp-offline-bundle:  2. Install the VIB via esxcli command line: SSH into each ESXi host in the cluster and install this VIB using the following command: The –no-sig-check tells ESXi to ignore the signature check, which is what is causing the issue with the install from Veeam 3. Rescan and Synchronize Storage Providers in vCenter: While not usually required, it is recommended to rescan and synchronize storage providers from vCenter. 4. Retry the I/O Filter Installation in Veeam: Return to Veeam and attempt the I/O filter install again.  During the install process, it should see the I/O filter already installed and up-to-date.  Continuing the installation wizard should allow the install process to successfully complete. Conclusion Issues with certificate compatibility can prevent the installation of the Veeam CDP I/O filter on older versions of ESXi 6.x.  VMware recommends to upgrade to version 7 or later to correct this; however, if upgrading isn’t possible, the manual VIB installation process should work, allowing the I/O filter to be successfully installed and function correctly.

Scroll to Top