For an authoritative restore with Veeam, see below for some additional steps, which are required. Due to this, the logic of Veeam Backup & Replication was developed accordingly, and by default, it performs automated, non-authoritative DC restore, assuming that it was not the only DC in place. In addition, restoring a DC in authoritative mode can be harmful and cause further damage. In most scenarios, a non-authoritative restore is what you need because it’s usually a multi-DC environment. With an authoritative restore, the DC claims itself as the only one with correct information and a valid database, and it authoritatively updates other DCs with its own data. The difference between those two restore types is that within a non-authoritative restore, the DC understands that it was out for a while, so it lets other in site DCs update its own database with the latest changes that occurred when it was down. Whenever you’re about to restore a DC, first determine whether a non-authoritative restore is enough, or if should you go further and perform an authoritative restore. Performing a restore of a Domain Controller in non-authoritative mode Here are the benefits of using DFSR over FRS. Refer to this article to determine whether FRS or DFSR is used in your domain. If the first domain controller of the domain was promoted to Windows Server 2008 functional level or higher, then you’re using DFSR. Since Windows Server 2008, DFSR has been a default option for SYSVOL replication. It was replaced by the DFSR in later Windows Server OS (operating system) versions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |