NBU Instant Recovery and vmotion
I have a very small VMware environment--about 10 VMs--that lives on one ESXi host, and I am backing it up with a VMware policy. I was looking into Instant Recovery--spinning up a VM that was needed, then using vmotion to move the VM over into the ESXi environment... but I was told that we do not have vmotion capability. Someone else on the team had thought vmotion was a feature that came with our 5240 appliance (i.e. we could vmotion the vm back into place) but I thought this was a feature that vmware had to supply. Any tips or info, including links with info on this specific type of case would be helpful. Thanks in advance for your help.Solved803Views0likes1CommentVMware Instant Recovery - ESXi resolving Media Server
Media Server is also the Backup Host: Windows Server 2008 R2 with NetBackup 8.0 ESXi: vSphere 5.5 Symptom: Instant Recovery for VMware fails with NetBackup Job Status 130 (regular VMware backups & restores were ok). Troubleshooting NFS shows the VMware message: "Operation failed, diagnostics report: Unable to resolve hostname '<MediaServer_hostname>'" associated to the VMware task "Create NAS datastore". Workaround: We added the Media Server name in the /etc/hosts file in the ESXi. Instant Recovery worked immediatly after this. My question: Do the ESXi always need to resolve the NetBackup Servers for Instant Recovery to work? I know the documentation recommends that the ESXi name should be published in the DNS (always a good VMware practice), but I didn't knew the ESXi themselves had to locally resolve the Master/Media/Backup-hosts servers too. I try not to touch the ESXi configuration, if possible.Solved1.6KViews0likes1Comment
