1-800-691-1991 | 9am - 8pm ET
EN

Veeam Backup for Microsoft Office 365 – Repository database size is approaching (or has exceeded) the limit

KB ID: 2681
Product: Veeam Backup for Microsoft Office 365
Version: 2.0
Published: 2018-07-24
Last Modified: 2020-08-13

Challenge

Backup jobs display either of the the following warnings:

  • “Repository database size is approaching the size limit of 60 TB. Current database size is 58 TB. To learn how you can free up and reuse space in your database, please see KB article 2681.”
    User-added image
     
  • “Repository database size limit has exceeded the size limit of 60 TB. Current database size is 60 TB. To learn how you can free up and reuse space in your database, please see KB article 2681.“
    User-added image

Cause

The Repository database cannot grow over 64 TB due to the JET Blue database engine limitations. Should this limit be reached while some transactions are still uncommitted, the database will be left in a dirty shutdown state with no option to recover it, as there is no more free space to commit those transactions.
To avoid such scenario, a warning and a fail-safe mechanism were hardcoded into Veeam Backup for Microsoft Office 365. The warning will appear once repository database file reaches 58TB, and the error will block any jobs from writing into such file once it reaches 60TB.

Note: Space is calculated based on the size of the database file and available space within the file. Thus, if you have a 60TB container (file) and 50TB of it marked as free space, you will receive neither warning nor error
 

Solution

Remove excessive data with PowerShell cmdlet Remove-VBOEntityData or move some of the backup data to another repository with Move-VBOEntityData.

KB ID: 2681
Product: Veeam Backup for Microsoft Office 365
Version: 2.0
Published: 2018-07-24
Last Modified: 2020-08-13

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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case.

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please go back try again later.