Maintain control of your Microsoft Office 365 email data
pmansfield
Enthusiast
Posts: 43
Liked: never
Joined: Jun 30, 2015 3:59 pm
Contact:

Re: Mailbox backup failures since 01/01/17

Post by pmansfield » Jan 20, 2017 10:34 am

I was given links to a B&R 9.5 update, plus an update to O365, and that has fixed the problem.

Last nights backup of mailboxes went without a hitch.

Mike Resseler
Veeam Software
Posts: 4993
Liked: 528 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: Mailbox backup failures since 01/01/17

Post by Mike Resseler » Jan 20, 2017 12:18 pm

Hi All,
As promised. Appeared on the website seconds ago, the long awaited update that fixes the issue, including some other fixes also. Everything can be found in this KB: https://www.veeam.com/kb2224!

Brgds,
Mike

mcrape
Veeam Vanguard
Posts: 53
Liked: 20 times
Joined: Jun 27, 2011 7:39 pm
Full Name: Matt Crape
Contact:

Re: Mailbox backup failures since 01/01/17

Post by mcrape » Jan 23, 2017 1:38 pm

For the sake of others, I had some minor issues with the service not starting when I upgraded.

I use a non-domain repository, which entails changing the service's logon account. During the install, the logon credentials were swapped back to the default 'Local System' account. After I changed them back to my custom account, everything worked fine.

Mike Resseler
Veeam Software
Posts: 4993
Liked: 528 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: Mailbox backup failures since 01/01/17

Post by Mike Resseler » Jan 23, 2017 1:54 pm

Matt,

Thanks! I'm sure it will help others

Cheers
Mike

ottl05
Influencer
Posts: 11
Liked: 1 time
Joined: Oct 16, 2014 11:29 am
Contact:

Re: Mailbox backup failures since 01/01/17

Post by ottl05 » Jan 24, 2017 7:22 am

with the update backups are working again.

jonsibar
Novice
Posts: 5
Liked: never
Joined: Jan 24, 2017 9:52 am
Contact:

Re: Mailbox backup failures since 01/01/17

Post by jonsibar » Jan 24, 2017 9:59 am

I got hold of the hotfix before it was public, and the backups worked fine. However, we do get an error for unlicenced users. From what I understand, Update 1 for Veeam Backup for Office 365 is only going to give a warning.

Are there any differences between the pre-release-hotfix and the public Update 1? I can't install it since the build number is the same (912), so I would presume the hotfix and public update is identical?

Dima P.
Veeam Software
Posts: 8783
Liked: 647 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Mailbox backup failures since 01/01/17

Post by Dima P. » Jan 24, 2017 11:47 am

jonsibar,

Kindly, check with the support team. Most likely the fix you are referring to was included in the update.

jonsibar
Novice
Posts: 5
Liked: never
Joined: Jan 24, 2017 9:52 am
Contact:

Re: Mailbox backup failures since 01/01/17

Post by jonsibar » Jan 24, 2017 11:56 am

Update: Seems like the retry of the job was the one that failed. The 'main' job reported only with a warning.

foggy
Veeam Software
Posts: 16957
Liked: 1380 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Mailbox backup failures since 01/01/17

Post by foggy » Jan 24, 2017 12:10 pm

Judging by the build number, you have the update that went public already installed.

Any chance you previously tried to process all mailboxes, while now adding mailboxes explicitly? Behavior is a bit different in these cases, due to some internal logic (in the first case the job will give an error for each unlicensed mailbox and finally fail after retry). As a workaround, you can try to assign and revoke licenses from these mailboxes in Office 365 admin center, this should ensure Veeam Backup for Office 365 doesn't touch them.

jonsibar
Novice
Posts: 5
Liked: never
Joined: Jan 24, 2017 9:52 am
Contact:

Re: Mailbox backup failures since 01/01/17

Post by jonsibar » Jan 24, 2017 1:23 pm

Actually, it's the other way around. We initially started out backing up a few mailboxes, and increased the number gradually to see how long the backup would take. In the end we switched to 'all mailboxes'

foggy
Veeam Software
Posts: 16957
Liked: 1380 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Mailbox backup failures since 01/01/17

Post by foggy » Jan 24, 2017 2:53 pm

Ah, ok, this explains the difference in behavior, not the fact you have some different version of the update code.

dustinn3
Influencer
Posts: 15
Liked: 6 times
Joined: Oct 14, 2013 1:53 pm
Full Name: Dustin Newby
Contact:

Re: Mailbox backup failures since 01/01/17

Post by dustinn3 » Jan 24, 2017 11:19 pm

I have the same issue. Set to all mailboxes and first job shows a warning status but shows 42 failures in the job, then 3 retries all have status failed.

foggy
Veeam Software
Posts: 16957
Liked: 1380 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Mailbox backup failures since 01/01/17

Post by foggy » Jan 25, 2017 2:35 pm

Just to avoid further confusion, the unlicensed mailbox issue is a different one, the original 'Object reference not set to an instance of an object' issue started to occur on January, 1st and discussed in this thread is fixed by the Update 1. The behavior you're describing is expected for such mailboxes (not licensed in Office 365).

dustinn3
Influencer
Posts: 15
Liked: 6 times
Joined: Oct 14, 2013 1:53 pm
Full Name: Dustin Newby
Contact:

Re: Mailbox backup failures since 01/01/17

Post by dustinn3 » Jan 25, 2017 7:17 pm

Thanks for the clarification foggy. I'll put in a feature request.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest