After reading this blog: https://community.veeam.com/blogs-and-p ... eness-9406 looks like the Veeam backup infrastructure can now be migrated to Linux appliances with PostgreSQL DB and Linux VMs for the Backup proxy.
Since the Linux appliances and the virtual machines are not joined to Active Directory as member servers, I am wondering what the requirements are for all of the service accounts. Additionally, I have on-premises Hyper-V and VMware that need to back up to the physical Linux Veeam Immutable Repository server.
Please share some thoughts and the AD service Accounts I must create and its privilege as well.
-
Backup.Operator
- Expert
- Posts: 115
- Liked: 7 times
- Joined: Oct 31, 2022 11:39 pm
- Full Name: Backup Administrator
- Contact:
-
vnikiforov
- Product Manager
- Posts: 17
- Liked: 2 times
- Joined: Aug 17, 2022 5:03 am
- Full Name: Vladimir Nikiforov
- Location: Romania
- Contact:
Re: Veeam Backup service account requirements
Hello,
Backup Proxies can be Linux and not domain-joined for quite some time.
Regarding the required Service Account Permissions, these permissions for each scenario or application are documented in Help Center: Permissions V13
We also have a dedicated vSphere permission guide, if granular vSphere permissions are required: Vsphere V13
The same goes for Restore Permissions.
Each Explorer requires a user account with different permissions: Explorers V13
Something to keep in mind: If you want to use Veeam Software Appliance (Rocky Linux based image), it comes with some Kerberos limitations/considerations. As an example, protecting VMs on a Hyper-V Cluster requires a domain joined backup server. Hyper-V Clusters do not support Deployment Kit yet: Before you begin
Backup Proxies can be Linux and not domain-joined for quite some time.
Regarding the required Service Account Permissions, these permissions for each scenario or application are documented in Help Center: Permissions V13
We also have a dedicated vSphere permission guide, if granular vSphere permissions are required: Vsphere V13
The same goes for Restore Permissions.
Each Explorer requires a user account with different permissions: Explorers V13
Something to keep in mind: If you want to use Veeam Software Appliance (Rocky Linux based image), it comes with some Kerberos limitations/considerations. As an example, protecting VMs on a Hyper-V Cluster requires a domain joined backup server. Hyper-V Clusters do not support Deployment Kit yet: Before you begin
---
BR,
Vladimir
Veeam Software
BR,
Vladimir
Veeam Software
Who is online
Users browsing this forum: Google [Bot] and 20 guests