However, worries about missing information between backups can be overcome if your backup system can incrementally backup between full backups. This is especially important since all the information created since the last backup will be lost if the newest backup isn’t used. Additi onally, always make sure the newest available backup is used for recovery. To ensure restoration will be effective, you should periodically check your restoration software in a test environment. A disaster recovery plan isn’t meaningful unless you have tested the system to make sure you can restore your AD from the available backups. Most of the time, the problem with recovery is n’t about the backup, but the restoration. Ensure that you always have a secondary copy of the backup in a different location.If an administrator changes the tombstone lifetime, perform a full backup immediately.By default, the tombstone lifetime in A D is 60 days, so you should make at least one full backup of your domain controller every 30 days. T he most recent domain controller backup shouldn’t be older than half of the tombstone lifetime.At least one domain controller per domain should be backed up.When formulating a disaster recovery plan, you should keep the following aspects in mind: This blog will list some best practices to secure your AD environment. However, this can provide a false sense of security, and is all the more reason to have a proper disaster recovery plan. One major reason administrators don’t hav e a disaster recovery plan at the top of their priority list is because o f h o w s t a b l e AD is as an infrastructure service. Only a few are better prepared and have a recovery plan for their domain controllers as well. When faced with this question, most AD administrators will only tell you about their object recovery plan. Just ask them about their disaster recovery plan.
It’s easy to m ak e Active Directory (AD) administrators uncomfortable.
0 kommentar(er)
