The Knowledge Base contains articles written by the user community and CloudBerry engineers on services and products offered by CloudBerry Lab. Browse topics by category, or use the search box to find answers to your questions.

Check out new videos about Managed Backup Service

Related KBs:


KB 1032
Jul 7, 2016

VMWare ESXi free (also known as VMWare Hypervisor) in conjunction with CloudBerry lab can fire up this error.

Eugene

KB: 1035
Last updated: 2016-07-30

VMware plan configuration returns wrong FQDN when configuring plan

This article will be deleted as this product behaviour has been fixed. However we keep this for the customer with old version of the CB Backup (5.0 or earlier).

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:

  1. Go to your C:\Windows\System32\Drivers\etc\hosts.
  2. Add new line with: IP_address of your VMware farm FQDN (for instance 192.168.1.1 vmware.domain).
  3. Might be ipconfig / flushdns required.

Example:


type C:\Windows\System32\Drivers\etc\hosts
[... something else ...]
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.

comments powered by Disqus