Veeam Office 365: Questions about Infrastructure

[wlacon]

Hello,
i need to install Veeam for Office 365 on-premise.
I have some dubts about it.
I have already a Bare Metal Veeam VBR v.12 (the server is REFS backup repository too). It is not joined to domain.
VO365 and VBR are two different infrastructures so the questions are:
- for veeam O365: server, proxy and repository: do i need to join all to domain or only one of these elements?
- can i install the Veeam Office 365 on Veeam VBR Bare Metal Server? If yes, can i use a another folder on it as repository for O365?
- will VBR and VO365 conflict with each other or any of their roles (es: gateway, proxy, etc)?

Thank you very much.

[Mildur]

Hello Wlacon

The product name is Veeam Backup for Microsoft 365 (VB365).

- for veeam O365: server, proxy and repository: do i need to join all to domain or only one of these elements?

Your choice. All components can work within a domain or workgroup. Active Directory may only be required if you want to protect on-premise Exchange server or a hybrid Exchange deployment.

- can i install the Veeam Office 365 on Veeam VBR Bare Metal Server? If yes, can i use a another folder on it as repository for O365?

Yes, but not recommended. You will find multiple topics about this question here in the forum.
Please also note, our recommended storage solution for VB365 backup jobs is object storage. Especially if you have a large Microsoft 365 environment with thousands of objects or you are a service provider protecting customer data.
As an example, backup copy jobs and immutability are only available for object storage repositories. And you can expect new features around repositories mainly developed for object storage based repositories.

- will VBR and VO365 conflict with each other or any of their roles (es: gateway, proxy, etc)?

The only shared component between VBR and VB365 are the Restore Explorers. If you update one product, most likely you also need to update the other one. Please checkout our compatibility matrix: https://www.veeam.com/kb4325

Also note, VB365 proxy service will require a lot of memory (8-32GB) to run the jet database based VB365 repositories. CPU and Memory resources which will not be available for your VBR backup services (jobs, proxy, repository).
And if you want to protect your VB365 server and it's repositories with a VBR backup job, then a second windows machine for your VB365 installation is a must. Using the same server for both products will make this much more difficult.

Best,
Fabian

[wlacon]

Hello Fabian,
thank you very much about your answers.

I think it's a Full Cloud deployment.
If Hybrid deployment is there a component i need to join to domain absolutely?
Last question because there is a On-Premise Exchange Server but it's used only as managemt role and mailboxs are in Cloud.

I have read the multiple topics about "VBR or VB365 on same machine or not" subject.
I can use the object storage in this infrastructure in this case.
I didn't undestand a element:
- even if i install VB365 server is a Virtual Machine for example, it's not a repository.
The repository will be bare-metal server.
So, to protect them (VB365 server and repository), i need to do two backup job with VBR Server (one for virtual machine and one with Veeam agent for Bare-Metal Server).
Do i undestand right?

Best regards.

[FrankCl2]

You're correct on the necessity of 2 jobs when you have a virtual machine and a physical machine. To be more specific, you'll need to deploy the Veeam Agent for Windows on that physical machine if you want to have a backup.