Tchater maintenant avec le support
Tchattez avec un ingénieur du support

NetVault Plug-in for FileSystem 13.0 - User Guide

Restoring System State Backups

This section includes the following topics:

•
About System State restore
•
System State restore considerations
•
Supported restore methods for Active Directory
•
Supported restore methods for SYSVOL Directory
•
Prerequisites
•
Restoring System State data
•
Restoring cluster database on Windows 2008
•
Additional considerations for domain controllers

About System State restore

System State restore allows you to recover a functional system without reinstalling the Windows operating system. It can be useful when you want to perform the following:

•
Perform a rollback (for example, overwrite the corrupted system data)
•
Perform a disaster recovery

Typically, when you perform a System State restore, all components are restored to their original location. However, the NetVault Plug‑in for FileSystem also allows you to restore the System State data to an alternate directory without affecting the active system. Restoring System State in a situation other than system recovery is not recommended.

While restoring the System State data on a Domain Controller, you need to select a method for restoring distributed services like Active Directory and SYSVOL. The restore method determines whether the restored data gets replicated to other servers or not. The method you choose depends on the number and configuration of Domain Controllers in your environment.

System State restore considerations

Consider the following when restoring system state backups to a second system:

•
The System State Backups can only be restored to the same system or an alternate system with the same hardware (that is, same make, model, and configuration). There should not be any driver, hardware, or firmware differences between the source and destination systems.
•
On Windows 2012, Windows 2008, and Windows 2008 R2, System State recovery is only supported on the same operating system instance. It is not supported on a reinstalled operating system on the same or different hardware.
•
Bare Metal Recovery (BMR) and System State Recovery have different objectives.
•
The NetVault Bare Metal Recovery Plug-ins use VSS to take a snapshot of a bootable volume (for example, C:\), and back up that volume at block level. There is no file system awareness during this process. During restore, the system is booted in an offline state using WinPE (preferred) or the Linux-based VaultOS, and the bootable volume (C:\) data is restored at block level. This method is recommended to recover a system that is in unbootable state, or to perform a full system recovery to an alternate system
•
System State Recovery recovers the System Registry, COM + Database, Certificate Services, Active Directory, SysVol, and other system state components to a previous known state. Problems can occur when you use a backup of C drive and System State to perform a full restore to an alternate system.
For more information about these issues, see the KB article https://support.microsoft.com/en-us/help/249694/how-to-restore-a-windows-installation-or-move-it-to-different-hardware from Microsoft.

Supported restore methods for Active Directory

Microsoft supports the following methods for restoring the Active Directory on a Domain Controller:

•
Non-Authoritative Restore: During non-authoritative restore, the distributed services on a Domain Controller are restored from the backup media, and the restored data is then updated through normal replication. Non-authoritative restore is typically performed when a Domain Controller has completely failed due to hardware or software problems.
•
Authoritative Restore: During authoritative restore, an entire directory, a subtree, or individual objects can be designated to take precedence over any other instances of those objects on the Domain Controllers. Through normal replication, the restored Domain Controller becomes authoritative in relation to its replication partners. Authoritative restore is typically used to restore a system to a previously known state, for example, if one or more Active Directory objects were erroneously deleted.
•
Primary Restore: Primary restore is used when the server you are trying to restore is the only running server of a replicated data set (for example, the SYSVOL and FRS).
 
* 
NOTE: The NetVault Plug‑in for FileSystem supports only non-authoritative restore of the Active Directory.
Performing an Authoritative Restore of Active Directory Objects

The NetVault Plug‑in for FileSystem supports only the Non-Authoritative restore method. When you restore the Active Directory using the plug-in, the objects are restored with their original update sequence number. The Active Directory replication system uses this number to detect and propagate Active Directory changes among the other servers. The data that is restored non-authoritatively appears as old data and does not get replicated to the other servers. The Active Directory replication system updates the restored data with the newer data available on the other servers.

To perform an authoritative restore of the Active Directory data, you must run the “ntdsutil” utility after you have restored the System State data, but before you restart the server. The ntdsutil utility lets you mark Active Directory objects for authoritative restore. When an object is marked for authoritative restore, its update sequence number is changed so that it is higher than any other update sequence number in the Active Directory replication system. This change ensures that any replicated or distributed data that you restore is properly replicated or distributed to all servers. For more information about ntdsutil, see the relevant Microsoft documentation.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation