Accelerates recovery from cyberattacks
Simplify, automate, and accelerate Active Directory forest recovery with unmatched security, flexibility, and options to meet the needs of your business continuity and disaster recovery plans.
Adapts to any disaster - Handle any Active Directory disaster recovery scenario, from attribute changes to SYSVOL corruption to full AD forest disasters.
Automates AD forest recovery - Automate the Active Directory forest recovery process, including the 40+ steps outlined in Microsoft's AD forest recovery best practices.
Provides flexibility and choice - Choose the best method for your situation, whether that’s phased recovery, restoring AD to a clean OS, or bare metal recovery.
Delivers clean, malware-free recovery - Eliminate the risk of malware reinfection throughout your AD forest recovery with scanning for malware and minimizing its hiding places.
Active Directory is a prime attack target
Organizations impacted by ransomware
Average downtime due to ransomware
Attempted attacks on Entra ID accounts
More than 20 years of Active Directory recovery expertise
|
|
FAQ
Active Directory Recovery is the process of restoring Active Directory (AD) services and data after a catastrophic failure or cyberattack, such as ransomware. It involves rebuilding domain controllers, restoring AD databases, and reestablishing forest-wide services to bring the AD environment back to a functioning state. Active Directory recovery is critical because AD is the backbone of most organizations' IT infrastructure and identity services, controlling user authentication, access to resources, and application functionality.
Active Directory recovery encompasses several types of operations, ranging from granular object restoration to full forest recovery. For minor issues, online granular restore allows you to recover individual attributes or objects without restarting domain controllers. This is useful for correcting accidental changes or deletions. For more severe scenarios, there are multiple options for full recovery. Bare metal recovery (BMR) allows you to recover all volumes of a domain controller to new or different hardware. Restore to clean OS enables you to restore AD onto a new Windows Server while reducing the risk of reinfection. Phased recovery lets you prioritize the restoration of critical domain controllers to get essential services running quickly.
With Microsoft-provided tools and manual processes, Active Directory forest recovery is a difficult, time-consuming, and error-prone process. In fact, Microsoft’s “Active Directory Forest Recovery Guide” outlines 40 high-level steps that must be performed correctly and in the proper sequence – on each DC. In addition, many of the steps aren’t operations that AD administrators are familiar with; they are tedious, often command-line based steps, so it’s very easy to make mistakes that can re-corrupt your directory and require you to start over. Quest Software reduces risk by automating every one of these manual steps. In fact, ESG Research validated that Recovery Manager can restore AD at least five times faster than the manual AD forest recovery process.
Most data protection tools simply do not suffice for AD disaster recovery. As noted above, in an AD forest recovery, you must coordinate the configuration effort across multiple DCs. Failure to do so can run the risk of USN rollback, RID bubbles, RID reuse, lingering objects in the Global Catalog, and other issues that can cause serious issues with Active Directory functionality. But most traditional data protection solutions simply focus on getting individual DCs to a “healthy” state – and leave all the coordination work to you.
VM snapshots are no substitute for an enterprise AD disaster recovery solution. Using snapshots for forest recovery will almost always result in data consistency problems that are difficult to resolve. Since the data on DCs is constantly being updated and the replication process takes time, snapshots of different DCs almost always contain inconsistent information. Snapshots can also include malware, which gets restored with everything else on the DC. Plus, if you store your VM snapshots in the default location, they’re an obvious target for ransomware encryption, rendering them useless. And logistically, control over VM snapshots resides with the virtualization team, complicating the AD team’s recovery operation. The virtualization team may not know the AD snapshots are an essential part of the disaster recovery strategy and may not protect them appropriately.