Upgrade considerations VBO 365 version 8 100TB stored data on repos

[rtheseeker]

Veeam backup for Office 365 version 7.1.0.2031

Currently we have around 99TB of data going across multiple Azure Object Storage Repositories and then a backup copy sends this data to AWS for long term.

We have jobs for each data type (Exchange, OneDrive, SharePoint and Teams) as per Veeam best practices and separate repository for each datatype as well.

We have scripted the jobs which uses one of the two proxies to write data to the available repository.

Exchange/OneDrive jobs are using Azure Dynamic Group rules which capture a guid of the object to load balance against proxies and repos.

Teams/Sharepoint backup use the script based on the first letter of the site

I am planning on upgrading from Veeam 365 version 7.1.0.2031 to 8; however have few questions

A. would the backup jobs continue to work as they are at the moment; or would it require a change in the way jobs are created once the platform is upgraded?

B. I understand PostGresSQL is installed and it does indexing against each repo; would the jobs be stuck and wont trigger till this indexing is complete or is it something that runs in the background and current jobs will continue to function. How much time does it takes for 100TB data to be indexed?

C. I am raising a request to update the app permission first; is there any thing else that we should be taking into consideration?

D. Also, the Teams api is now charged; would it stop the existing teams sites from backup

[Polina]

Hi Rajeev,

A. Existing backup jobs will continue to work, and their configuration will remain.

B. Indexing is performed by a proxy service. It sends information about all existing restore points from repositories to the PostgreSQL database. Indexing is a background operation that does not impact backup jobs operation and working with repositories. If you explore backups from a repository that is being indexed, some restore points may not be visible until indexing is completed.

C. Key considerations are covered in the Release Notes. But I'd suggest you first wait until the next patch for v8 is released (it's expected soon) and also involve a Veeam system engineer to plan for the upgrade to v8.

D. You pay only for the backup of Teams change messages, other Teams data - files, metadata, etc - is protected for free. And v8 respects your current backup settings - if you were protecting team chats, they keep being protected; if chats were out of the backup scope, they remain not protected after the upgrade.

Hope it helps

[rtheseeker]

what would be the process to engage a Veeam System Engineer
C. Key considerations are covered in the Release Notes. But I'd suggest you first wait until the next patch for v8 is released (it's expected soon) and also involve a Veeam system engineer to plan for the upgrade to v8.