Backup AD server using NBU agent for Hyper V

[Symctec]

Hello,

I need to backup AD server via agent for Hyper-V(VHD level backup), is it possible to perform GRT restore for AD objects and is there a config guide available for this?

Best Regards,

Raj

[sdo]

AFAIK, not supported yet for Hyper-V VM style backups.  IMO, you need to perform a client backup from within the VM.

[Symctec]

Thanks...any idea if a full DR of the AD vm can be done using vhd backup? Will the AD database be consistent? Best regards...

[sdo]

This doesn't look good for "VM" style backups of DCs:

https://technet.microsoft.com/en-us/library/d2cae85b-41ac-497f-8cd1-5fbaa6740ffe(v=ws.10)#backup_and_restore_considerations_for_virtualized_domain_controllers

.

IMO, I'd follow the MS tech note and stick with normal file system, and therefore System_State: (i.e. Shadow_Copy_Components:) backups of AD servers...

...because it appears that the only valid way to recover a DC requires a pathway through Directory Services Restore Mode which requires the use of a System_State: backup to recover AD in a DC.

[sdo]

Some good discussion points in this:

http://www.altaro.com/hyper-v/how-to-back-up-and-restore-domain-controllers-virtualized-on-hyper-v/

[Symctec]

Thanks sdo for the replies, looks like the NBU product management has still some catching up to do with regards to Hyper V agent, BackupExec being an SMB product can perform GRT restore from a VHD backup. Probably NBU is depending too much on VMware to win a deal every time :))

Cant enable accelerator as well for a Hyper V type policy :(

[sdo]

Well, when it comes to backups of DC's and their AD content, then... IMO the same points about being super careful with AD recovery and therefore super careful with DC backups all rings true no matter which backup product we use, or whichever backup style we thought we might be able to use... because AD is so very difficult to manage from a backup/recovery perspective.   So, it would posit that the more fancy a backup product is then the more we might be lulled in to thinking that so-and-so fancy feature will save our skin in an AD recovery situation... whereas, the truth is, it won't... because there are very few ways to properly recover AD, and all of them require standard/simple almost traditional backup methods.  My point is, that all the R&D in the world isn't going to help us with AD recovery.

The other thing is that we forget how old VMware is.  Of course VMware and backup product integration is more mature, but then VMware have concentrated on their hypervisor platform and pretty much left the backup data life-cycle elements to the experts.   Hyper-V 2008 was a baby.  DPM 2008, not worthy of comment.  Hyper-V 2012 is heading in the right direction.  DPM 2012, well, still not there.  Let's wait and see what the backup product vendors can do with Hyper-V 2016... because... Hyper-V is clearly starting to accrue a level of increased adoption, but is it enough for backup product vendors to take serious notice... and... no matter how much notice a backup product vendor might want to take... if the door is closed... (because the hypervisor vendor has their own backup product)... then the door will never be truely open.   So, then, we, as backup admins have to decide... when we have input, would we recommend hypervisor "A" or hypervisor "B" ?   Which is easier to work with?  With which of them are we more likley to actually be able to recover data?  Which is more flexible?  Which has more features to suit real world complex operational IT?  I think we all know where we would land, with big sites, and small sites.

And medium sized sites... generate a lot of discussion.