This utility will quickly modify the Veeam Service Provider Console (VSPC) Settings for disabling the API throttle and Microsoft 365 Exchange Explorer WCF Timeout Setting within VSPC. Please do not run this utility unless directed by Managecast support. Download to the VSPC server and run the EXE.
The warning “Completing backup copy interval for GFS full creation” appears at the end of a backup copy interval when Veeam needs to “seal” that cycle by creating the GFS full (weekly, monthly, or yearly) restore point. It’s informational—Veeam wraps up the current copy cycle and then either synthesizes a full on the target or performs an active full, depending on your GFS method. Why It Happens GFS schedule hit: The day/time for a weekly, monthly, or yearly point has arrived, so Veeam finishes the running copy cycle and creates the archive full.Full type matters: When to Take Action Most of the time, no action is needed. If you’re seeing long runs or warnings piling up, check the following: It’s Veeam saying, “I’m ending this copy cycle now so I can make the scheduled GFS full.” It’s normal. Only make adjustments if it’s colliding with your backup windows or impacting duration—adjust the copy interval or schedule, align GFS dates, and choose Active Full for GFS on dedupe targets. For more information, please contact us at Support@Managecast.com.
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: 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: 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: Additional Notes If you continue to experience this error or need assistance verifying mailbox permissions, please contact Support@Managecast.com.
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: 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: Cause 3: RPO Target Too Strict Your defined RPO value may be unrealistic for the current backup window, job load, or infrastructure performance. Resolution: Additional Notes If you continue to experience RPO violation warnings or would like help analyzing job duration and scheduling, please contact Support@Managecast.com for assistance.
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.
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.
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.
During an update or upgrade of Veeam Backup & Replication, you may encounter the error message: “SSPI authentication failed for user.” Even when running the installer or updater with administrative privileges, this issue can still occur. It’s most often related to a mismatch between the Windows account used for the original installation and the one currently running the update, or to a change in the system hostname after installation. Common Scenarios Case 1: Hostname Changed After Installation If the Veeam installation was performed under a local administrator account and the server’s hostname was later changed, the mapping in PostgreSQL’s authentication file (pg_ident.conf) no longer matches the current system identity. As a result, the SSPI handshake fails during authentication. Case 2: Different Administrator Account Used If the update is being run under a different administrator account than the one originally used for installation, the PostgreSQL service will reject authentication due to an unmatched user mapping. Resolutions Case 1: Edit the pg_ident.conf File 1. Open the file:C:\Program Files\PostgreSQL\15\data\pg_ident.conf(Note: The PostgreSQL version number may vary depending on your installation.) 2. Scroll to the bottom of the file and locate the section labeled:MAPNAME SYSTEM-USERNAME PG-USERNAME You can also add additional administrator accounts here if multiple users manage the environment. 3. Update the entries to reflect the current system username or hostname. Example: 4. Save the file and restart the PostgreSQL-Veeam service. 5. Rerun the installer or update process. Tip: Always create a backup of pg_ident.conf before making changes. Case 2: Run the Updater with the Original Admin Account 1. Log in using the same Windows administrator account that was used during the initial Veeam installation. 2. Re-run the updater or installer from that session. 3. Once the update completes successfully, verify that all Veeam services start normally and can access the configuration database. Additional Notes If the SSPI authentication error persists after applying these fixes, please contact Support@Managecast.com for further assistance.
The “Failed to expand object” error in Veeam Backup & Replication typically occurs when Veeam attempts to enumerate or query a virtual infrastructure object (such as a VM, datastore, cluster, or host) but cannot retrieve its components. This issue is most often related to environment configuration or permission mismatches between Veeam and the underlying vCenter/ESXi infrastructure. Common Causes and Resolutions Cause 1: vCenter or ESXi Connectivity Issues When Veeam cannot communicate properly with vCenter or a managed host, it may fail to expand objects during job initialization or inventory enumeration. Resolution: Cause 2: Incorrect or Expired Credentials If the credentials used to connect to vCenter, ESXi, or a Windows repository have changed or expired, Veeam will be unable to access the associated objects. Resolution: Cause 3: Insufficient Privileges The account used to connect to the host or vCenter must have adequate privileges to query inventory objects and perform backup operations. Resolution: Additional Notes If you continue to experience this error or need further assistance, contact Support@Managecast.com for additional troubleshooting guidance.
Backup or replication jobs in Veeam Backup & Replication may sometimes report the following message: “VM disk size changed since last sync, deleting all restore points.” At first glance, this can look like a serious problem — losing all restore points sounds alarming. However, this behavior is intentional and protective. Veeam is designed to maintain data consistency and will automatically reset a replication or backup chain if it detects a change that could make incremental data unsafe to use. During every backup or replication cycle, Veeam compares source VM’s current virtual disk configuration to the metadata stored from the last successful job. If it detects any differences, it assumes the disk layout has changed and that existing restore points are no longer valid for incremental synchronization. When this happens, Veeam takes a cautious approach to preserve data integrity: This ensures the next restore point reflects the VM’s current, correct disk configuration, preventing corruption or restore failures in the future. Best Practices When Veeam detects that a VM’s virtual disk configuration has changed, it intentionally resets the backup or replication chain to prevent inconsistencies and ensure that all future restore points are reliable. By planning disk modifications around full backups and maintaining awareness of storage-related changes, you can avoid unnecessary fulls while keeping your replication and backup data consistent and trustworthy. For more information, please contact support@managecast.com.
