-
- Expert
- Posts: 239
- Liked: 13 times
- Joined: Feb 14, 2012 8:56 pm
- Full Name: Collin P
- Contact:
Domain Controller Backups
Is it possible to use a non-domain admin account for 'application-aware image processing' to backup a domain controller?
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Domain Controller Backups
Hi Collin, no, to perform AAIP on a domain controller, an account that is a member of the DOMAIN\Administrators group is required. Thanks!
-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Jul 26, 2018 5:40 pm
- Full Name: Kenneth Erard
- Contact:
Re: Domain Controller Backups
I'm seeking update guidance on this, too.Is it possible to use a non-domain admin account for 'application-aware image processing' to backup a domain controller?
Today, I'm using a dedicated account that is a member of BUILTIN\Administrators in each domain. That account is named as the guest processing account in my jobs protecting domain controllers. Was wondering if we could use BUILTIN\Backup Operators or something privileged like that instead of Administrators.
-
- Product Manager
- Posts: 20415
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Domain Controller Backups
As mentioned above,
foggy wrote:no, to perform AAIP on a domain controller, an account that is a member of the DOMAIN\Administrators group is required
-
- VP, Product Management
- Posts: 7081
- Liked: 1511 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Domain Controller Backups
The only way would be to do crash consistent backups. At AD object restore you will be asked for the AD database place (if not standard) and for an account that you want to use for restore.
It is important to check that you systems run Windows 2016 or higher and the AD is 2016 mode or higher so that you will not have any replication issues when you restore a crash consistent AD server.
I suggest that when you restore a crash consistent AD server, that you always manually start it in non Non-Authoritative Restore mode.
The other option would be to use an AD admin account but strip down the rights with group policies so that the account can not modify/start anything security related.
The Admin rights are needed for our VSS processing as we on demand use an VSS requestor that need local admin rights for implementing it.
It is important to check that you systems run Windows 2016 or higher and the AD is 2016 mode or higher so that you will not have any replication issues when you restore a crash consistent AD server.
I suggest that when you restore a crash consistent AD server, that you always manually start it in non Non-Authoritative Restore mode.
The other option would be to use an AD admin account but strip down the rights with group policies so that the account can not modify/start anything security related.
The Admin rights are needed for our VSS processing as we on demand use an VSS requestor that need local admin rights for implementing it.
Who is online
Users browsing this forum: No registered users and 28 guests