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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyNDEyIiwiaGFzaCI6Ijk0NzJiZTE0LTQ1ZDQtNGM1YS1hZTQyLWIwNjA1MzQ3NzkyNSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Cannot browse backups of Office 365 mailboxes that have been made in December

Challenge

Cannot browse backups of Office 365 mailboxes that have been made in December 1-8, 2017.

Solution

1. Make sure you have Veeam Backup for Office 365 version 1.0.0.912 or 1.5.0.1099
2. Download and unpack hotfix here
3. Install VeeamBackupOffice365_1.5.0.1309.msi and VeeamExplorerExchange_9.6.0.1308.msi
4. Confirm the backup can be browsed
 
If there are any remote proxies in use:
1. After both .msi files are installed, stop Veeam Backup Proxy for Microsoft Office 365 Service on the Remote Proxy Server
2. Copy all files (C:\Program Files\Veeam\Backup365\Packages\Proxy) from Server that has Veeam Backup for Microsoft Office 365 Service running to remote Proxy (C:\Windows\Veeam\Backup365Proxy)
3. Start Veeam Backup Proxy for Microsoft Office 365 Service
4. Confirm the backup can be browsed
KB ID:
2412
Product:
Veeam Backup for Microsoft Office 365
Version:
1.5
Published:
2017-12-05
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