Skip to main content
Solved

Significant increase in incremental backup size (Microsoft 365)


  • Comes here often
  • 10 comments

As of the 27th March we have seen a significant increase in incremental backup size for our Microsoft 365 backup… Peaking at 800GB+ on the 31st! 

We have different jobs configured for different sources, for example we have separate jobs for:

  • User Mailboxes
  • Shared Mailboxes
  • SharePoint Sites
  • OneDrive Sites

Looking at the size of each backup job, I think the increase in backup size is primarily due to the user mailbox jobs; the other jobs look ‘normal’ in terms of their size. 

  1. Is anyone else seeing a sudden increase in backup size in the last couple of weeks? 
  2. Does anyone have any tips for pinpointing where the increase is coming from? 

Best answer by Stabz

Hey,
One of my customer just report me this problem, after a research, there is a kb for this https://www.veeam.com/kb4483

The problem is on the MS side 😕

View original
Did this topic help you find an answer to your question?

12 comments

Stabz
Forum|alt.badge.img+8
  • Veeam Legend
  • 335 comments
  • Answer
  • April 3, 2024

Hey,
One of my customer just report me this problem, after a research, there is a kb for this https://www.veeam.com/kb4483

The problem is on the MS side 😕


  • Author
  • Comes here often
  • 10 comments
  • April 3, 2024
Stabz wrote:

Hey,
One of my customer just report me this problem, after a research, there is a kb for this https://www.veeam.com/kb4483

The problem is on the MS side 😕

Thanks - this looks like it could be the cause! When did your customer first see the increase? 


kristofpoppe
Forum|alt.badge.img+9
  • Veeam Vanguard
  • 110 comments
  • April 3, 2024

We also see this on multiple tenants. Especially last week.

Cherriis VBO management platform images

 


Stabz
Forum|alt.badge.img+8
  • Veeam Legend
  • 335 comments
  • April 4, 2024
EMcS wrote:
Stabz wrote:

Hey,
One of my customer just report me this problem, after a research, there is a kb for this https://www.veeam.com/kb4483

The problem is on the MS side 😕

Thanks - this looks like it could be the cause! When did your customer first see the increase? 

Since last week like you, 26-27 March


dloseke
Forum|alt.badge.img+7
  • Veeam Legend
  • 1427 comments
  • April 4, 2024

I’m seeing an increase as well, but I’m also having issues viewing my buckets in Wasabi (possibly outage-type issue, I have a case open), but looking at my overall dashboard, I see an increase in my consumption over the past month as well.  However, this graph isn’t nearly as dramatic as what you’re seeing because most of my data is in VBR buckets and not for VB365 so may really temper the overall growth.  I’m guessing once I can view my individual buckets it may be more telling.

 


  • Author
  • Comes here often
  • 10 comments
  • April 4, 2024
dloseke wrote:

I’m seeing an increase as well, but I’m also having issues viewing my buckets in Wasabi (possibly outage-type issue, I have a case open), but looking at my overall dashboard, I see an increase in my consumption over the past month as well.  However, this graph isn’t nearly as dramatic as what you’re seeing because most of my data is in VBR buckets and not for VB365 so may really temper the overall growth.  I’m guessing once I can view my individual buckets it may be more telling.

 

Rather than checking the utilisation from the Wasabi bucket side, you could do the storage consumption report from Veeam - this is where my graphs are from 😀


dloseke
Forum|alt.badge.img+7
  • Veeam Legend
  • 1427 comments
  • April 4, 2024

Well, that was my next stop, but I do some reporting on my bucket sizes at the beginning of the month, so that’s where i had started anyway.  :-)  Also, support got back to me and I might have something blocking internally...so the hunt begins.


  • Author
  • Comes here often
  • 10 comments
  • April 8, 2024

Update: 

Our incremental backups still appear to be significantly larger and therefore this does not appear to be the same behaviour as documented in https://www.veeam.com/kb4483
 

 


  • Author
  • Comes here often
  • 10 comments
  • May 10, 2024

MS365 support have confirmed a fix has been implemented for this: 

 

As per product engineering team, a fix has been rolled out in Exchange Online backend to mitigate the impact.

 

Our backups seem to be back to normal, for now… 😀


  • New Here
  • 1 comment
  • May 16, 2024
EMcS wrote:

MS365 support have confirmed a fix has been implemented for this: 

 

As per product engineering team, a fix has been rolled out in Exchange Online backend to mitigate the impact.

 

Our backups seem to be back to normal, for now… 😀

Can you pls provide source for this fix.

Statement isn't mentioned in https://www.veeam.com/kb4483


  • Author
  • Comes here often
  • 10 comments
  • May 16, 2024
GreySlater wrote:
EMcS wrote:

MS365 support have confirmed a fix has been implemented for this: 

 

As per product engineering team, a fix has been rolled out in Exchange Online backend to mitigate the impact.

 

Our backups seem to be back to normal, for now… 😀

Can you pls provide source for this fix.

Statement isn't mentioned in https://www.veeam.com/kb4483

I had a case open with Microsoft 

  • Case #: 2404100050001099

Looking at https://www.veeam.com/kb4483, there is the following statement:


Due to changes we [Microsoft] are making to optimize search and compatibility functionality within our service, this action led to re-indexing for some of our customers' data. The re-indexing is not indicative of a change to fields material to our BCDR and storage partners, so we will be working on a change to minimize the re-indexing that is prompting another backup of customer data. We made changes over the weekend [of 2024-04-20] that should pause the unexpected behavior and those changes will be in place until Microsoft and our partners are able to make longer term enhancements to avoid future issues from taking place.
Thank you for your patience.


  • Author
  • Comes here often
  • 10 comments
  • September 2, 2024

This has happened again… 😕

https://www.veeam.com/kb4483


Comment