VBO 3.0 Upgrade Repository

[Mike Resseler]

Hi Dustin,
If we understood it correctly, you are upgrading from 2.0 to 4.0, which means the repository needs to make some major changes (it is actually the one from v2 to v3, so from v3 to v4 that issue isn't there anymore).

Can you let us know your support number for follow-up?

[dustinn3]

Mike,

I was actually going from 2.0 to 4.0 and ran across it. Gostev pointed me to a note on page 12 saying it may take significant time upgrading from 2.0 to 4.0 so I'll eat crow on this, although significant is is a pretty vague term to describe a time frame from minutes to multiple days. It ended up taking about 40 hours to upgrade the repository.

[Mike Resseler]

Thanks for letting us know Dustin

[YouGotServered]

Polina, I am having the same issue with my VBO 4.0 upgrade taking multiple days and there is absolutely no documentation in the release notes about the amount of time it will take. I'm already on day 2 and it's still at 20% on a 2 TB disk. I'm also appalled that a backup vendor would knowingly let a customer deploy a product that will take their system offline for multiple days without any type of warning.

I do see this in the release notes, but it only talks bout v2 to v4. Are you going v2 to v3 or v3 to v4?

"Important note: When upgrading from version 2.0 to 4.0, it may take significant time to upgrade repositories containing SharePoint data due to many underlying changes introduced for SharePoint Online processing and data storage. The upgrade process requires an additional 15% of free space of the current repository size."

I will say that I went from v3 to v4 and I'm at 26% 5.5 hours later on a repo with about 11TB of data. I'm not seeing the spike in data usage I saw from v2 to v3, however. Our repo has exchange, SP, and OD data.

Seems like the release notes may need to be updated to say when upgrading to v4 from any version, you may see long upgrade times.

[Mike Resseler]

Cory,

To be honest, we did not expect long delays from v3 to v4. Could you DM me (when the job is done) and sent me the links? I would like to review them with the team.

[YouGotServered]

Mike,
Not sure exactly how long it ended up taking. I started the upgrade around 10:30am CST, it was still going by 5:30pm, by the time I logged back on at 8am CST the next day, it was done. I'll DM you. Thanks!

[Mike Resseler]

Hi @YouGotServered,

We reviewed it and saw the total time which is OK. Going from v2 to v3 would have taken much longer with that amount of data. However, I do believe we should add something additional to the RN to point out that "waiting to see the upgrade finish" might not be the best idea

Thanks for your help
Cheers
Mike

[tjurgens]

The release notes for v4 say this:

Important note: Upgrading backup repositories from version 3.0 to 4.0 may take significant time to complete and the upgrade duration highly depends on the amount and type of backup data in a repository. According to the test results, it may take up to 8 hours in the setup with 1 TB of data in a backup repository. Plan for an appropriate maintenance window when your backup repository that is been upgraded is not available for use. Note that upgrading version 2.0 repositories to 4.0 requires a bigger maintenance window due to many underlying changes to backup repositories. The upgrade process requires an additional 15% of free space of thecurrent 2.0 repository size and may take up to 17 hours per 1 TB of data in a backup repository.

This is really useful and I wish I had saw this earlier.

That said, I am struggling to find any way to actually check the status and which part of the repo is currently being upgraded. The best I can see is the timestamps on each folder year:


Is there any other way using VBO to see what the current status of the upgrade is? I think it would silence a lot of the concerns over a long upgrade if there was any actual status beyond a percentage completed - preferably in the GUI, but even if its just logged in a file somewhere it would help.

[DanielJ]

I just wanted to chime in that I upgraded two VBO servers today from v3 to v4 (one organization on each), more or less identical settings and repository hardware, and amount of saved data. The main difference is that one uses item retention and the other snapshot retention. The one with item retention took 1.5 hours/TB to finish, the one with snapshot retention just 15 minutes/TB. So there seems to be a lot of variation in time required for the upgrade.

[Polina]

Hi Tyler,

With the extended logging enabled, you can get more details on the process. Here's an example:

Code: Select all

1/16/2020 1:55:26 PM   27 (1788) Attaching database C:\VeeamRepository\2019\repository.adb...
1/16/2020 1:55:26 PM   27 (1788)   Checking configuration database version...
1/16/2020 1:55:26 PM   27 (1788) Warning: Unsupported configuration database version: 305, expected: 405
1/16/2020 1:55:26 PM   27 (1788) Invalid database version: C:\VeeamRepository\2019\repository.adb
1/16/2020 1:55:26 PM   27 (1788) Database instance added to database pool: 2019
1/16/2020 1:55:26 PM   27 (1788) Starting repository database 2019 upgrade...
1/16/2020 1:55:26 PM   27 (1788)     Executing action: Global...
1/16/2020 1:55:26 PM   27 (1788)     Executing action: ItemsHistoryUpgradeActionV30...
1/16/2020 1:55:26 PM   27 (1788)     Executing action: ListsUpgradeActionV30...
1/16/2020 1:55:26 PM   27 (1788)     Executing action: ItemsUpgradeActionV30...
1/16/2020 1:55:26 PM   27 (1788)     Executing action: FilesUpgradeAction...
1/16/2020 1:55:26 PM   27 (1788) Repository database upgrade completed
1/16/2020 1:55:26 PM   27 (1788) Database version has been incremented to 405

[vaibhav]

Hello Team,

before configuring jobs for users i want to check if we can segregate jobs based on workload (mailbox, share point and one drive).
please confirm if this can be achieved

[Mike Resseler]

Hi Vaibhav,

Yes, that is perfectly possible