From:
http://blogs.dirteam.com/blogs/jorge/archive/2010/08/12/restoring-the-sysvol-non-authoritatively-when-either-using-ntfrs-or-dfs-r-part-3.aspx
This post focusses on restoring the SYSVOL when replicated through the DFS-R mechanism. For the previous posts see here and here.
SYSVOL Replicated Through DFS-R - Authoritative Restore - Steps To Take
To perform an authoritative restore of the SYSVOL when using DFS-R, use the following steps:
- Start the Registry Editor
- Navigate to "HKLM\SYSTEM\CurrentControlSet\Services\DFSR"
- Create a key called "Restore" (only time only)
- Create a string value called "SYSVOL" (only time only)
- For the string value called "SYSVOL" assign the value of authoritative
- Navigate to "HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore"
- Create a key called "SystemStateRestore" (only time only)
- Create a string value called "LastRestoreId" (only time only)
- For the string value called "LastRestoreId" [1] assign the value of 10000000-0000-0000-0000-000000000000
- Stop the DFSR Service
- Start the DFSR Service
From the command-line the same can be achieved through:
- REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\DFSR\Restore" /v SYSVOL /t REG_SZ /d "authoritative" /f
- [1] REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\SystemStateRestore" /v LastRestoreId /t REG_SZ /d "10000000-0000-0000-0000-000000000000" /f
- NET STOP DFSR
- NET START DFSR
[1] When a backup application performs a system state restore, it must indicate that it has done so by setting the LastRestoreId registry value. The LastRestoreId is a GUID that is formatted as 00000000-0000-0000-0000-000000000000. The GUID has to be different each time a restore is requested. For example, if you have the LastRestoreId set as 10000000-0000-0000-0000-000000000000, for the next restore you have to set it to a different GUID, such as 20000000-0000-0000-0000-000000000000. For more information about setting LastRestoreId, see Registry Keys and Values for Backup and Restore.
As soon as the DFS-R Service starts, the following events appear with information about the non-authoritative restore.
Event ID 2109
Event ID 2110
Event ID 4106
Event ID 4108
SYSVOL Replicated Through DFS-R - Non-Authoritative Restore - Steps To Take
To perform a non-authoritative restore of the SYSVOL when using DFS-R, use the following steps:
- Start the Registry Editor
- Navigate to "HKLM\SYSTEM\CurrentControlSet\Services\DFSR"
- Create a key called "Restore" (only time only)
- Create a string value called "SYSVOL" (only time only)
- For the string value called "SYSVOL" assign the value of non-authoritative
- Navigate to "HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore"
- Create a key called "SystemStateRestore" (only time only)
- Create a string value called "LastRestoreId" (only time only)
- For the string value called "LastRestoreId" [1] assign the value of 10000000-0000-0000-0000-000000000000
- Stop the DFSR Service
- Start the DFSR Service
From the command-line the same can be achieved through:
- REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\DFSR\Restore" /v SYSVOL /t REG_SZ /d "non-authoritative" /f
- [1] REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\SystemStateRestore" /v LastRestoreId /t REG_SZ /d "10000000-0000-0000-0000-000000000000" /f
- NET STOP DFSR
- NET START DFSR
[1] When a backup application performs a system state restore, it must indicate that it has done so by setting the LastRestoreId registry value. The LastRestoreId is a GUID that is formatted as 00000000-0000-0000-0000-000000000000. The GUID has to be different each time a restore is requested. For example, if you have the LastRestoreId set as 10000000-0000-0000-0000-000000000000, for the next restore you have to set it to a different GUID, such as 20000000-0000-0000-0000-000000000000. For more information about setting LastRestoreId, see Registry Keys and Values for Backup and Restore.
As soon as the DFS-R Service starts, the following events appear with information about the non-authoritative restore.
Event ID 2109
Event ID 2110
Event ID 4110
Event ID 4102
Event ID 4604
Cheers,
Jorge