VMware plan configuration returns wrong FQDN when configuring plan
Product: CloudBerry Backup
Versions: VM edition
Product type: All
Platform: Windows
Created at: Jul 30, 2016
Updated at: Jul 30, 2016
Author:
Author: erudinsky
Problem
CloudBerry Backup VM edition is agent-less solution and designed to work with VMware Virtual Machines. Our VM edition is not that mature, so the main position of this product is decent VM archiving. When you configure backup plan and it returns wrong FQDN even you enter IP. This actually returned by VMware API for Data Protection (VADP) and CloudBerry does not handle this accordingly. When your VMware nodes are not part of the domain they may have wrong host files configured.
Resolution
This can be resolved by the following workaround (we are set to address this issue in one of the next release), but for now:
- Go to your C:\Windows\System32\Drivers\etc\hosts
- Add new line with: IP_address of your VMware farm FQDN (for instance 192.168.1.1 vmware.domain)
- Might be ipconfig /flushdns required
Example:
# C:\Windows\System32\Drivers\etc\hosts
127.0.0.1 fiji.cloud.local
Check if you can nslookup your IP and it touches your FQDN, ping it to see if it returns ICMP. Configure your plan.