Skip to main content
  • EN

After a successfully instant restoration of hyper-v vm to another hyper-v host, not able to open AD users and computers, it is throwing error of not supported OS version.

 

Was the backup done with application aware processing turned on?  Otherwise you will have crash consistent which is not good for Domain Controllers.

What errors are you seeing?  What OS is the VM?  What version of Hyper-v are you using?  Did you check the logs in Veeam - C:\ProgramData\Veeam\*

Hi @juggu -

As suggested, can you provide more details on the process you took? 

  • How is the VM backed up?
  • How was the VM restored? Entire VM? Instant Recovery?
  • Other info Chris asked you for (Are you using AAIP? OS of VM and HV host?)

Can you share a screenshot of your error? Make sure to remove any pertinent biz info.

 Created backup job of microsoft hyper v virtual machine.

Selected instant restore option and migrated to production option. In restored vm when i try to open AD users and computers. This error pops up.

Can you restore it successfully on the same HV host? Are you able to try that? 

Is AAIP enabled in the backup job, as was asked earlier? 

Yes AAIP is enabled. Do not want to restore on same hyper v host. But trying a scenario where source gets corrupted and then be able to restore to another hyper v host

Entire vm restore option is available for just nutanix ahv, using veeam 12.1, not able to find entire vm restore option.

From the Home node > Backups section, click Disks, expand the Job then select VM to restore. There is no Entire VM option in the ribbon or by rt-clicking? 

No option of wntire vm on ribbon as well as by right click. 

At this point @juggu , I think it best you get ahold of Veeam Support. 

Okay Thanks will do that.

Okay Thanks will do that.

Keep us posted what they find out.

After the restore with Veeam, domain controllers first boot into Directory Services Restore Mode and try to perform a non-authoritative restore. If there are other domain controllers available and automated reboot should happen afterwards and the DC is back online. In case of a single DC environment or DR test his will take some time before the DC is back online. All the details are described here: https://www.veeam.com/kb2119

Did you see a reboot after restoring the DC? And how long did you wait after the initial boot?

 

 

 

I forgot about that KB thanks for sharing it Regnor.   That is more than likely the issue.

Comment


Terms & Conditions