Setup for multiple tenants

[JKring]

Hi,

We have just about started to offer our customers 365-backup and I would like some advice here before we dig ourselfs a too deep hole.

We run VBO on a local server and have added our customers as just another organization and use the same repository for everything.
Recently I was tasked to move VBO to a dedicated server and found that it takes so long to transfer the data that we will miss one scheduled backup.

I'm planning to suggest to my manager that each customer should be on their own repository since it would (in my opinion) give a few advantages.
a. I could have moved the customers data to the new server one by one.
b. In case a customer ends the contract and want us to give them their stored data, we would be able to comply more easily.
c. Each customer can choose their retention time since it is set in the repository.

Does any of you have a similar setup and can suggest a best practice for how set it up for multiple customers?

Thank you in advance.

[JKring]

Just had a quick look in the the section Architecture for service providers in the Technical Deployment and Configuration Guide.
Seems like we should have done it like that in the first place.

Is it possible to export one customers data to a separate repository? Or should I point them to a new repository and just keep the old repository until retention time is over?

[nielsengelen]

You can move data via PowerShell using Move-VBOEntityData. An example script with a GUI mover can be found on GitHub.