On page 22 of "Avamar 7.0 for Windows Server User Guide" it states:
To back up Active Directory data in preparation for disaster recovery, perform regular System State backups of the domain controllers:
◆ On a Windows Server 2012 or Windows Server 2008 computer, use the Windows VSS plug-in to perform the backup. When you perform the backup, clear the Create Disaster Recovery Backup checkbox on the Options tab. When you clear the checkbox, you can only use the backup for online restore, not BMR.
I am trying to understand if this is a requirement for Win2k8/12 system state backup, why is that option checked by default ? Is there any harm with leaving that option checked ?
The "Disaster Recovery" checkbox invokes the Automated System Recovery (ASR) writer when performing a system state backup. Backups generated using the ASR writer can only be restored offline (i.e. by booting from a suitable WinPE image) so they are not suitable for restoring Active Directory online and vice-versa.
This checkbox is checked by default because creating a bootable system state backup is the right thing to do for the majority of systems -- Active Directory is the exception.
So if I read the documentation correctly, you need 3 jobs to fully backup an AD server:
1. File system backup
2. VSS backup for BMR
3. VSS backup for AD?
If anyone can clear this up that would be great. I would also like to see granular restore capabilities on the AD data, but I hope to think that it's on the road map for future releases, if not it might be a sticking point for some companies.
The "Disaster Recovery" checkbox invokes the Automated System Recovery (ASR) writer when performing a system state backup. Backups generated using the ASR writer can only be restored offline (i.e. by booting from a suitable WinPE image) so they are not suitable for restoring Active Directory (which must be done online) and vice-versa.
key sentence, that helps. All of our domain controllers are VMs so in addition to file system/VSS backup they will also be backed up at VM level backup. That should remove the requirement for BMR and for that option to be checked.
@sconstable_illumina is asking a good question, do we need to break up AD controllers backup into two datasets:
I don't imagine there are many instances where you'd need to run a file restore on a Domain Controller but I guess you never know.
If file level backup and restore is required for physical DCs, you would need multiple datasets -- the DC would have to be protected using regular file system backups in addition to the non-DR VSS backup (and the DR VSS backup if enabled). For VMs, you have more options. If you're already protecting these systems at an image level, you could use VMware File Level Restore (FLR) in place of agent-level file system backup and restore. FLR has limitations on the number and size of files so make sure you test it and confirm that it meets your needs.
ok, so let's say there are multiple, geographically dispersed DC in ones organization where Dataset #3 will never be needed. Any issues with combining Dataset #1 and Dataset #2 into one Dataset ?
ionthegeek
2 Intern
•
2049 Posts
7757
0
Posted March 18th, 2014 10:00
The "Disaster Recovery" checkbox invokes the Automated System Recovery (ASR) writer when performing a system state backup. Backups generated using the ASR writer can only be restored offline (i.e. by booting from a suitable WinPE image) so they are not suitable for restoring Active Directory online and vice-versa.
This checkbox is checked by default because creating a bootable system state backup is the right thing to do for the majority of systems -- Active Directory is the exception.