https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IzMDc0IiwiaGFzaCI6ImU1Y2M0YTU0LTZhOTktNDVhNi1hYjk0LTg5MTNkNGVlZTM5NSJ9
1-800-691-1991 | 9am - 8pm ET
EN

How to Configure Antivirus Exclusions for Veeam Backup for Microsoft Office 365

Challenge

Deployment of required Veeam Backup for Microsoft Office 365 services and executable files fails because of the antivirus software.

Solution

Add the following paths to the exclusion list of your antivirus software on the Veeam controller server:
  • C:\Program Files\Veeam
  • C:\Program Files (x86)\Veeam
  • C:\Program Files\Common Files\Veeam
  • C:\Program Files (x86)\Common Files\Veeam
  • C:\Windows\Veeam
  • %programdata%\Veeam
  • The folder that contains repository databases
Add the following paths to the exclusion list of your antivirus software on the remote backup proxy server:
  • C:\Windows\Veeam
  • %programdata%\Veeam
  • The folder that contains repository databases.

More information

Should you have any questions, contact Veeam Support.
KB ID:
3074
Product:
Veeam Backup for Microsoft Office 365
Version:
3.0 and later
Published:
2019-12-24
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later