Good afternoon! I have recently started seeing an issue where mailbox backups via Veeam Backup for o365 are not performing a complete backup. For instance, I have a mailbox that has a 10.77 GB main mailbox and an archive of 5.27 GB archive - this is according to o365 via Get-MailboxStatistics in PowerShell. Yesterday, I configured a Veeam Backup for o365 job to back up both the main and archive for this user. The job completed successfully but only exported 405.9 MB total for both the main and archive - after exporting to a pst the main mailbox is 298 MB and the archive is 219 MB. This isn't the first user I've seen this happen with lately but I am starting to not trust Veeam Backup for o365. Has anyone else noticed this behavior and/or figured out how to fix?
For background, we are fully cloud-based on o365 and Veeam Backup for o365 software is running on a dedicated Windows 2012 R2 virtual machine with plenty of free space on the local repository.
I am seeing the following errors in the Veam.Archiver.Proxy log but the job is completing without error:
4/25/2018 2:58:28 PM 26 (3640) Waiting before next processing attempt: 00:00:30...
4/25/2018 2:58:57 PM 52 (3732) Trying to resume...
4/25/2018 2:58:57 PM 52 (3732) Exchange Web Services error code: ErrorServerBusy
4/25/2018 2:58:57 PM 52 (3732) Error: Failed to synchronize item changes
4/25/2018 2:58:57 PM 52 (3732) Error: The server cannot service this request right now. Try again later.
4/25/2018 2:58:57 PM 52 (3732) Warning: Exchange Web Services request failed
4/25/2018 2:58:57 PM 52 (3732) Unable to process mailbox. Server cannot service the request
4/25/2018 2:58:57 PM 52 (3732) Waiting before next processing attempt: 00:00:30...
4/25/2018 2:58:58 PM 48 (3316) Trying to resume...
4/25/2018 2:58:58 PM 58 (3076) Trying to resume...
4/25/2018 2:58:58 PM 26 (3640) Trying to resume...
4/25/2018 2:58:58 PM 58 (3076) Exchange Web Services error code: ErrorServerBusy
4/25/2018 2:58:58 PM 58 (3076) Error: Failed to synchronize item changes
4/25/2018 2:58:58 PM 58 (3076) Error: The server cannot service this request right now. Try again later.
4/25/2018 2:58:58 PM 58 (3076) Warning: Exchange Web Services request failed
4/25/2018 2:58:58 PM 58 (3076) Unable to process mailbox. Server cannot service the request
4/25/2018 2:58:58 PM 58 (3076) Waiting before next processing attempt: 00:00:30...
4/25/2018 2:58:58 PM 48 (3316) Exchange Web Services error code: ErrorServerBusy
4/25/2018 2:58:58 PM 48 (3316) Error: Failed to synchronize item changes
4/25/2018 2:58:58 PM 48 (3316) Error: The server cannot service this request right now. Try again later.
4/25/2018 2:58:58 PM 48 (3316) Warning: Exchange Web Services request failed
4/25/2018 2:58:58 PM 48 (3316) Unable to process mailbox. Server cannot service the request
4/25/2018 2:58:58 PM 48 (3316) Waiting before next processing attempt: 00:00:30...
4/25/2018 2:58:58 PM 26 (3640) Exchange Web Services error code: ErrorServerBusy
4/25/2018 2:58:58 PM 26 (3640) Error: Failed to synchronize item changes
4/25/2018 2:58:58 PM 26 (3640) Error: The server cannot service this request right now. Try again later.
4/25/2018 2:58:58 PM 26 (3640) Warning: Exchange Web Services request failed
4/25/2018 2:58:58 PM 26 (3640) Unable to process mailbox. Server cannot service the request
4/25/2018 2:58:58 PM 26 (3640) Waiting before next processing attempt: 00:00:30...
One of the reasons for ErrorServerBusy is because the EWS monitoring detects that the limit for the requests that are from a Client to a Mailbox server was reached. Therefore, the Client returns an ErrorServerBusy response code to all EWS requests to the Mailbox server.
Second: What is your retention?
Finaly: I see too many of those so please create a support call so they can dig deeper. Post the support call ID here and the outcome after investigation also
Thanks! I will go ahead and create a support ticket and report results here. Our retention was originally 90 days - we are just creating mailbox backups and exporting to a pst for employee terminations and occasionally for litigation purposes. I have juggled the retention down to a day but still have the same issue.
The retention in VBO works according to the change data of an item. Which means that if your retention is 90 days, you only protect new/ changed/ deleted items that are younger than 90 days. Therefore you won't find anything older than that.
Try to change the retention to longer (x years, depending on your legislation) and then the mails should be visible
Thanks for the advice, you are completely correct in that it is the retention that is causing my issues. I changed it to "Keep forever" and backups are now running normally. I also lowered my thread count to see if that helps with EWS errors. My assumption was that a retention policy on the repository would pertain to how long backups are retained on the repository. My fault for making assumptions without doing my research. I thank you very much for your help.
