Moving VBM server+repo, plus also starting new repos

[MoranJ2000]

Hi.

I'm hoping to get some guidance on the above.

Situation: I've got VBM running on a physical PC (6.0.0.385) with a single job backing up my entire organization to a single repo about 1.5 TB in size (encompassing about 85% Exchange, 10% OneDrive, and 5% Sharepoint).

I set up VBM in relative haste a few years ago, and it's worked well for me but now I need to relocate it to a new physical PC due to the current PCs CPU/RAM limitations and the fact that it's running low on storage.

In retrospect, I wish I'd set up the current VBM with separate jobs and repositories for Exchange, OneDrive, and Sharepoint. I'd like to rectify that going forward, especially because although our use of OneDrive and Sharepoint has been limited, I expect it to increase in the coming months. But of course I also need to keep the existing repo.

I've already set up a new system and installed the same version VBM on it, and it seems to me that what I need to is move my existing repo to the new PC, then create three new jobs and repos (four if you count Teams, i guess) to use going forward.

But not really sure the best way to go about that without potentially creating a big mess (presumably the new repos will contain a lot of the same data as the old one), and not even sure if that's the preferred thing to do, or if perhaps there's a better/simpler way I'm not thinking of.

I'd appreciate any tips or suggestions.

Thanks.

Joe

[Mildur]

Hi Joe

We have documented the process to move VB365 to a new server in a KB:
https://www.veeam.com/kb2649

If you want to migrate the different backup types (SPO,OneDrive, Mailbox, Teams) to different repositories, you have to use a Powershell command:
https://helpcenter.veeam.com/docs/vbo36 ... ink&ver=60

I suggest you first migrate the repository first to the new server with kb2649 and test a restores.

Splitting the repository with the PowerShell commands could be a lot of work. Have you considered creating new repositories and start new backups to this repositories. You can let the backups on the migrated repository age out and remove the repo when the retention is over.

What‘s the amount of data you have to backup? Size and object count?
For the repositories, I would just create 2 for smaller tenants:
- 1 for Sharepoint, OneDrive and Teams
- 1 for Mailbox

Thanks
Fabian

[MoranJ2000]

Thanks for your response Fabian.

I'm not certain how many objects are in the repo, only that it's about 1.5 TB in size and overwhelmingly Exchange mailboxes, because although it backs up the entire org, our use of OneDrive has heretofore been minimal, and our use of SharePoint almost non-existent.

I defintely don't want the headache of splitting up the current repo, and if I start a new repo for Exchange, I'm essentially re-backing up most of that data, creating redundancy, eating up disk space, and also causing confusion for me when it comes time to do a restore-- i.e. do I restore from the migrated repo or the new one?

Based on your suggestion, my thinking now is to move the current repo, create a new job for it that backs up not the whole org, but just Exchange. Then, then create a new job and repo for OD, SP, T. This way, duplication is kept to a minimum.

Does this seem reasonable to you? Anything I might be missing by going this route?