O365 backup as a service

[hgreguric]

Hello,

I am an engineer in a service provider team and we want to add O365 backup as a service to our Cloud Connect SP environment. Documentation on the implementation on the helpcentre is very brief and I am a bit lost how is this suppose to be done, I will write down the steps how I understood it and please correct me if I am wrong:

SP side
1. Install O365 on the same VM where Veeam backup and Replication for Service Providers is installed?
2. How do you connect this two or you just create storage for tenants in the VBR?

Tenant side
1. Tenants have to have installed 0365 Veeam backup somewhere and then add a Cloud repository account? How do they do this? How do you backup your O365 data from the tenant side to the Service Provider side?
2. How do you connect tenant side with SP side?

If there is some more detailed documentation on the topic please let me know, thank you.
Kind Regards,

[Mike Resseler]

Hi @hgreguric

SP Side
1. Correct
2. You need to create a repository per tenant. We do advice object storage, but JET DB repository per tenant is also possible

Tenant Side
1. You can't do this. O365 backup is very different from VBR. The tenant will not install VBO at all because you will be responsible for connecting to the O365 side and download the data. This means that all the data will be on your side and not on the tenant side. The tenant will use a locally installed Veeam explorer for Exchange / SharePoint / OneDrive (and soon Teams) to connect via cloud connect to your VBO installation and restore data.

[hgreguric]

Thanks @Mike Ressler

I still have some questions how to setup this.

SP side:

1. Can we install O365 on a separate VM or it has to be installed on the same VM as VBR connected to Cloud Connect?
2. We have a scale out repository in our Cloud connect environment from which create add quota to tenants can this work? If I understood you can have O365 backup as a service only with JET DB repository or some object storage?

Tenant:
I understand so the Tenant has to install VBR and Veeam explorer for Exchange/Sharepoint/One drive, but I don't understand where do we create jobs? How do we create jobs?

We will add tenant organizations in our VBO on SP side and create jobs? This part is not clear to me, so we will be adding multiple organizations to our SP O365 and connect tenat organizations to tenant storage we have created on the cloud connect side?
Could you please elaborate on this a bit I would really appreciate it.

Is it enough that the user only installs Veeam explorer for Exchange/Sharepoint/One drive on their side? (This part I understand they have the explorers on their side to browse and restore data).

Kind Regards,

[Mike Resseler]

Hey @hgreguric

1. Not at this moment. The VBO controller needs to be on the same server as VBR in order to use cloud connect. Additional proxies can be on different servers obviously.
2. Repositories from VBR are a complete different thing. Personally, in a service provider setup, I would install the VBO controller (so the first server where you install the software) at the VBR server, and then deploy at least one new server that will be a proxy. This proxy will do the active work (backup/ storing data/ etc...). Connected to this proxy you can choose to add local disks (or a few others, see here: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=40) or (we believe this is the future for services as this) an object-storage repository. (S3-compatible, or AWS/ Azure/ IBM when you run it in the cloud)

Tenant:
Jobs are created on YOUR side. You agree with the tenant what you will protect (and charge for it) and you will create the job. Another way is to create a portal with our REST API's and let the tenant do some work themselves (see an non-official supported example here: https://github.com/nielsengelen/vbo365-rest).

You will indeed add multiple organizations in your installation, and to be multi-tenant, you would need to create a repository per tenant (in the case of object storage, different folders)

Installing only the explorers is not enough, because you need the possibility to connect to Cloud Connect. But letting the tenants install the VBR Free edition is enough if they don't have VBR today.

[hgreguric]

Thanks Now I have a bit better understanding of the whole process.

I still have a couple of questions?

1. Is it possible to use Enterprise manager and self service portal for tenants to create jobs themselves or to atleast be able to do some form of administration?

2. If I understood correctly since we are using direct attahed storage, we should attach the storage to a newly provisoned proxy and then in VBR Cloud Connect add that VM as a proxy and a repository. Once we create a tenant their folder will be created on a proxy server and we will be able to create a repo for them via VBO?

Kind Regards,

[Mike Resseler]

Hey,

1. No, not at this moment.
2. Not in VBR cloud connect, simply on the VBO UI. Cloud connect is only used as a communication mechanism for the Veeam explorer (with the tenant) against the VBO server. But all the other interaction is done between VBO controller and VBO proxies and Cloud connect is not needed for it.