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:

1. Review job schedules in Veeam Backup & Replication → Home → Jobs.
2. Ensure that one job (e.g., Backup Copy Job) starts only after the dependent backup job finishes.
3. Use the “After this job” scheduling option to chain jobs and prevent overlap.
4. For large jobs or slow repositories, increase the interval between dependent jobs.

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:

1. Verify repository performance and connectivity.
   • Check network adapters, cables, and switches for errors or negotiation mismatches.
   • If using NAS or deduplicating storage, ensure that latency and throughput meet Veeam’s requirements.
2. Monitor performance in Veeam → History → Job Sessions to identify prolonged write operations.
3. If delays persist, consider adjusting repository task concurrency in Backup Infrastructure → Backup Repositories → Select the Repository → Properties → Repository → Increase Limit maximum concurrent task→ Finish.

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:

1. Exclude the following from antivirus and EDR scans:
   • All Veeam program folders (default: C:\Program Files\Veeam)
   • Repository paths containing .vbk, .vib, .vrb, and .vbm files
   • Veeam services and executables (e.g., Veeam.Backup.Manager.exe, VeeamAgent.exe)
2. Schedule antivirus scans outside of backup windows.
3. After adjusting exclusions, restart affected Veeam services to clear stale file handles.

Additional Troubleshooting

If the issue persists:

• Check job logs under
  C:\ProgramData\Veeam\Backup\<JobName>\Job.<timestamp>.log
  to identify which process or file path triggered the lock.
• Use Sysinternals Handle or Resource Monitor → Disk to determine which process is holding the lock.
• If a file remains locked after a crash or network interruption, rebooting the repository server can release the stale handle.

Preventive Recommendations

• Schedule jobs sequentially or use dependencies to avoid concurrency conflicts.
• Maintain proper repository I/O monitoring to catch storage performance issues early.
• Keep antivirus exclusions up to date whenever Veeam is upgraded.
• Regularly review job reports for “file in use” or “access denied” warnings.

If you continue to experience this error, or would like assistance with scheduling optimization or repository performance tuning, please contact Support@Managecast.com.