Contact Us

October 21, 2025

General Cloud Backup, Office 365 Backup, Troubleshooting, Veeam

Veeam for Microsoft 365 Error: Exchange Account Was Not Found

/

The “Exchange account was not found” error in Veeam Backup for Microsoft 365 occurs when Veeam attempts to process an Exchange Online mailbox that it cannot locate in Microsoft 365. This can happen during backup or restore operations and is typically caused by missing mailboxes, deleted users, or permission mismatches. Common Causes and Resolutions Cause 1: The Account Does Not Have a Mailbox Assigned Veeam can only protect users that have an active mailbox in Exchange Online. If a user account exists in Microsoft 365 but no mailbox is provisioned, Veeam will display this error. Resolution: In the Microsoft 365 Admin Center, verify the user has a valid Exchange Online license assigned. If the account should have a mailbox, assign a license and sign in to the mailbox once to complete initialization. If the account is a service or shared account that does not require backup, edit the backup job in Veeam and uncheck the Mailbox option under the user’s settings. Cause 2: The Account Was Deleted or No Longer Exists If the user has been deleted or offboarded from Microsoft 365, Veeam will still attempt to process the object if it remains referenced in the backup job. Resolution: Edit the job → Select Objects menu → Select User → Remove. Alternatively, add the account to the Exclusions list if the job is configured for the entire organization. If the mailbox was recently removed but should be recoverable, restore it from the Microsoft 365 Admin Center → Deleted Users, then rerun the backup. Cause 3: Permissions or Access Have Changed If the organization’s Exchange Online permissions were modified, Veeam may no longer have sufficient rights to access specific mailboxes. Resolution: In Veeam, open Organization → Edit Organization → Connection Settings, and verify the configured Microsoft 365 app registration and service account have Application Impersonation rights and Mailbox Access permissions. In Azure AD, confirm the app registration still has the delegated Exchange Online permissions required by Veeam (full_access_as_app, EWS.AccessAsUser.All, etc.). Rerun the job after confirming access. Additional Notes This error may appear as a warning if other mailboxes complete successfully. To backup shared mailboxes, the backup account must have a valid Exchange license and active mailbox. When offboarding users, it’s good practice to remove or exclude their accounts from backup jobs to avoid recurring warnings. If you continue to experience this error or need assistance verifying mailbox permissions, please contact Support@Managecast.com.

Troubleshooting, Veeam

Veeam Backup & Replication Warning: RPO Violation

/

In recent versions of Veeam Backup & Replication, the RPO Monitoring feature tracks how frequently restore points are created for each backup job. RPO (Recovery Point Objective) defines how much data loss your organization can tolerate between backups—essentially, how often backups must occur to meet your protection goals. If RPO Monitoring is enabled and a job does not create a new restore point within the configured timeframe, Veeam will generate an RPO violation warning in the job session or in the RPO Monitoring dashboard. Common Causes and Resolutions Cause 1: Backup Jobs Are Overlapping or Delayed When multiple jobs are scheduled to run at the same time or share repository resources, one or more may enter a “waiting” state and exceed the RPO window. Resolution: Review the schedule for each backup and copy job under Home → Jobs. Stagger job start times to avoid overlap and resource contention. Consider chaining dependent jobs using the “After this job” option to ensure sequential execution. If your environment has multiple proxies or repositories, balance job placement to improve concurrency. Cause 2: Job Size or Duration Exceeds the RPO Window Large jobs that take longer to complete than the defined RPO interval will consistently trigger RPO warnings. Resolution: Split large jobs into smaller, logical groups (e.g., by department, datastore, or workload type) so each finishes within the target window. Review repository and proxy performance — bottlenecks can extend backup duration. Enable parallel processing if your hardware resources allow, to speed up data movement. Cause 3: RPO Target Too Strict Your defined RPO value may be unrealistic for the current backup window, job load, or infrastructure performance. Resolution: Edit the affected copy job → Target → Advanced → RPO Monitor. Adjust the RPO target to a more achievable interval (for example, from every 1 hour to every 4 hours, or daily instead of hourly). Click OK to save and rerun the job to validate compliance. Additional Notes RPO violations are warnings, not failures — they indicate that your environment is not meeting its defined backup frequency. Use the RPO Monitoring report (available in Veeam ONE or within the Veeam Backup & Replication Console) to identify patterns and recurring delays. If the issue began after upgrading, ensure that RPO Monitoring is configured correctly for all job types (backup, replication, and copy). If you continue to experience RPO violation warnings or would like help analyzing job duration and scheduling, please contact Support@Managecast.com for assistance.

General Cloud Backup, Troubleshooting, Veeam

Veeam Backup & Replication Error: File Being Used by Another Process

/

The error “The process cannot access the file because it is being used by another process” is a common issue in Veeam Backup & Replication environments. It occurs when Veeam attempts to read or write to a backup file that is temporarily locked by another process. These conflicts are often caused by scheduling overlaps, slow storage performance, or antivirus activity scanning the backup files. Common Causes and Resolutions Cause 1: Scheduling Conflicts Overlapping backup, copy, or replication jobs can attempt to access the same backup files simultaneously, resulting in file lock conflicts. Resolutions: Cause 2: Network or Storage Performance Issues When data transfer to or from the repository is slower than expected, a job may still be writing to a file when another process tries to open it. Resolutions: Cause 3: Antivirus or Third-Party Software Locking Files Antivirus, endpoint protection, or indexing software may temporarily lock Veeam’s backup files (.vbk, .vib, .vrb) during real-time scans. Resolutions: Additional Troubleshooting If the issue persists: Preventive Recommendations If you continue to experience this error, or would like assistance with scheduling optimization or repository performance tuning, please contact Support@Managecast.com.

General Cloud Backup, Troubleshooting, Veeam

Veeam Backup & Replication Error: Failed to Open Storage for Read/Write Access / File Does Not Exist

/

When a backup job fails with the errors “Failed to open storage for read/write access” or “File does not exist,” it typically indicates that Veeam was unable to access or write to the backup repository. These issues are often caused by connectivity problems, permission misconfigurations, insufficient storage, or file locks that prevent normal access. Common Causes and Resolutions Cause 1: Repository or Storage Connectivity Issues If Veeam cannot reach or communicate properly with the repository, it will fail to open the backup file for read/write operations. Resolutions: Cause 2: Insufficient Free Space When the repository runs out of space, Veeam cannot write incremental or full backup data, often producing the same error message. Resolutions: Cause 3: Permissions or Ownership Issues If the credentials Veeam uses do not have sufficient rights on the repository, the job may fail to open or write to the storage file. Resolution: Cause 4: File Locks or Interference from Other Software Antivirus, backup agents, or volume snapshot tools may lock Veeam backup files (.vbk, .vib, .vrb), preventing read/write operations. Resolutions: Advanced Troubleshooting If the above resolutions do not resolve the issue: Preventive Recommendations If you continue to experience errors after performing these steps, please contact Support@Managecast.com for assistance.

General Cloud Backup

Veeam for Microsoft 365 Error: Failed to Resolve Personal Site Owner

/

The “Failed to resolve personal site owner” error in Veeam Backup for Microsoft 365 occurs when Veeam cannot validate or identify the owner of a Microsoft 365 personal site (OneDrive/SharePoint). This typically happens when a personal site is included in a backup job—often through an organizational or group selection—but the associated user account cannot be resolved. Common Causes Resolutions Resolution 1: Verify or Reassign the Personal Site Owner In SharePoint Admin Center, confirm that the personal site has a valid owner: Resolution 2: Create a Dedicated Job for the Personal Site If the personal site cannot be resolved but still needs to be backed up: Resolution 3: Exclude the Personal Site from the Job If the personal site data is not required for backup: Additional Notes If you continue to experience issues, need help reviewing personal site ownership, or have further questions, please contact Support@Managecast.com for assistance.

Scroll to Top