O365 Backup Multi-Tenant Setup

[SubThr33]

Hey all,

I am just looking into the o365 backup solution and was wondering if there was a way to segregate each individual backup job to a separate directory?

Cheers,
SubThr33

[foggy]

Hi David, currently this is not possible, but looks like a valid feature request. Thanks!

[njsmee]

Just started using this week, and I would add my voice to this feature request, we have multiple clients and would prefer to separate their data into different backup db's.

[Mike Resseler]

Nigel,
Are you offering this as a service provider already today?

Mike

[njsmee]

Just starting to look into doing so, early days of testing functionality, and only for our centrally hosted multi-tenant clients.

[Mike Resseler]

Nigel,

OK. Got it. Please test as much as you want and open up threads with items you would like to see. Our v1 version was never intended for Service Providers, but this is of course a scenario that is on our table. We would be happy to hear how you are thinking about offering this to your customers.

For the multiple folders. This is indeed a road we are investigating

Thanks
Mike

[njsmee]

Thanks, it lends itself well to Service Providers in that you can have multiple organisations already, so splitting out the db into different db's by organisation would be a natural extension probably, at the moment, we are still working out the best model to offer this under, probably for our tenanted customers as a value add option to our existing O365 offering, cost based on storage and an admin fee, something like that.

Look forward to seeing the evolution.

[bjdboyer]

Definitely a 2-thumbs-up for multi-tenant and separate "job" directories in the repository. We are also a service provider and want to start offering this.

Bill

[cthorpe]

Also add my support for multi-tenant support (MSP and VCSP)

[spilch]

Add my support as well.

[colossus610]

Hey, sweet lookin bandwagon, mind if I jump on for a ride too?
I would like to respectfully add my +1 to the Veeam O365 Backup Multi-Tenancy / Cloud Provider option.
Enjoy your Holidays everyone.

[sunchai]

Add another MSP to the list. With our Datacenter having a direct pipe into Azure and Office365 configuring all of our clients O365 backups take only a few minutes. To utilize the free license most of our clients received we were toying with the idea of Nano servers to provide the separation and multiple license capabilities. Would be nice if that was a more native feature as well as stacking the licenses or making them per organization. Not all of our clients have adopted the Rental model.

[Mike Resseler]

Hi Sunchai,

One of the issues with your idea is that Nano server is not supported as a platform for the solution. Some of the components necessary are not supported (today) on Microsoft nano server.

We are thinking however on how to separate the clients within a same installation and one of those thoughts is by using a different repository per "tenant"

Please keep the thought stream coming, we are actively listening and planning

Cheers

Mike

[JaySt]

With our Datacenter having a direct pipe into Azure and Office365 configuring all of our clients O365 backups take only a few minutes.

You mean Express Route? You have no worries about data transfer costs in that case compared to free transfer when not using Express Route ? Just wondering

[AJ83]

We have 2 affiliate company`s with their own O365 tenant we would like to backup. So the Multi-tenant feature is not only needed for service providers.

[Mike Resseler]

Hi AJ83,

I assume building 2 different O365 (virtual) servers is out of the question in your scenario?

[bulletlynn]

Another vote to have separate repositories for different tenants!

Also to have different retention per repo.

[Mike Resseler]

Thanks Nick!

Is a different retention per repository enough for your needs? As in, each of your tenants will receive their own retention, but only 1 retention for that organization

[bulletlynn]

That would probably work but it might be nice if you could have different retention periods per job under each organization.

Thanks!

[Mike Resseler]

Thanks Nick. Noted down and will be discussed how feasible it is for the next version

[rmehta]

Please add my vote to this request as well.....We want to offer this service to our customers

[Mike Resseler]

Hi Rajeev,

Are you referring to my proposal of having one repository per customer or the request for different retention periods per job?

[cthorpe]

+1 vote to allow for different retention periods per job ... thanks !

[Mike Resseler]

Chris,

Per job can be achieved (in 1.5) if they point to different repositories (PS: different repositories can be on the same volume so...). So you could have a 3-year, 7-year and forever retention (as an example) repository and then point your different job to it