Disaster recovery programs appreciate bare-metal recovery (BMR) for its promise of fast and convenient full system restores. Gone are the days of re-building servers from scratch. Now, entire servers, complete with operating system, applications, settings, and drivers, are restored with a few clicks. Of course, life is never that simple.
Despite the buzz of BMR, there are many underlying issues with the approach, particularly for recovery of Active Directory (AD). For starters, if domain controllers (DCs) are infected or disabled by a cyberattack, BMR can actually do more harm than good. That’s because BMR backups, like system state backups, contain boot files, executables, and other OS artifacts where malware can linger and re-infect restored DCs.
Considering that cyber disasters now inflict more business damage than natural disasters and strike more frequently, BMR is not the “failproof” approach that it hoped to be. Join Redmond Intelligence for a free, live webinar that details 5 of the most dangerous pitfalls of BMR for AD, and how to harden your DR processes to combat today’s emerging threats.
New cyber-first requirements for AD recovery:
- Fully automate forest recovery
- Prevent re-infection from BMR and system state backups
- Restore to any hardware (virtual or physical)
- Regain control of a compromised AD
- Ensure the integrity of highly sensitive forests
