JamesNT wrote:Upon restore, it is important to note that the cluster the domain controllers were running on no longer exists. VEEAM wants to, upon choosing to do a full VM restore, look for that cluster and restore to that. Not an option.
JamesNT wrote:After reading this thread, we noted that we did NOT have Application Aware Processing turned on for the domain controllers. However, given the approach we have to take to restore the DC's, with having to do individual files and then import them using Hyper-V manager, would that make a difference for us? Or are we destined to have to always bring in one DC and remove the other every time we do a restore?
Upon restore, it is important to note that the cluster the domain controllers were running on no longer exists. VEEAM wants to, upon choosing to do a full VM restore, look for that cluster and restore to that. Not an option. So in order to restore the backup, we have to choose to restore the individual VHDX files and config files to a folder on one of the hosts, use Hyper-V Manager to import the DC's, setup a new cluster, then move the domain controllers into the new cluster.
I'm 99% sure this is a known issue and is slated to be fixed in V9U2. The work around for this issue is to simply perform a VM Files restore to manually restore the files rather than leveraging the Entire VM restore option
Gostev wrote:Team, let's create a support KB on authoritative AD restores with Veeam (step by step). Please coordinate with QC and Support. Thanks!
JamesNT wrote:Can we confirm this? I can't seem to find the feature that a Hyper-V guest can be restored by choosing Full VM Restore to a different host or cluster anywhere for version 9.
Gostev wrote:Support KB article is already available > KB2119
JamesNT wrote:We choose the option in Veeam to restore only files then use Hyper-V Manager to import the VM.
JamesNT wrote:The article does not mention when the registry entries may be deleted. Can anyone elaborate?
Users browsing this forum: Bing [Bot] and 1 guest