no vm's made on vm copy job

[renebos]

Using 6.5.0.128 - 64bit

I am trying to make a vmcopy job and actually copy a vm from my esx 5.1i cluster to a standalone esx5.1i server. It starts perfectly but after the job finishes i see a new folder on the datastore but no vm is registered to the standalone esx5.1i server.

What is going wrong or is this not even possible.

I did it in a previous version the other way around, from standalone to cluster, that went well.

Thanks in advance.

Rene

[Vitaliy S.]

Hi Rene,

Can you please clarify a bit - do you see empty folder on the target datastore or you do see the VMs, but they are not registered on the ESX(i) server?

Thanks!

[Dima P.]

Hello Rene,

Could you please also clarify:

- Copy job ended up with no error on (?)
- The VM was not registered; however you do see a folder inside the data store. If it's indeed include *.vmx file - you can try to add this VM to your inventory manually?

Thank you.

[renebos]

It does copy the files to the target datastore, it creates a folder like "vmname (vm-nr)"

And there is a warning in the job. Could not perform threshold check for backup location "<datacenterRef>ha-datacenter................

A manually import from "browse datastore and add to inventory" goes well.

[renebos]

Was there not a "MOVE" option in the previous versions?

[Dima P.]

Hello Rene,

Thank you for the update.
This is by design behavior - after you use VM Copy it creates a fully copied VM folder and then you need to add this VM manually to your inventory.

For the "Move" option, that sounds exactly like the Quick Migration feature. You can use it in Veeam B&R > Virtual Machines > Right click on the VM and choose Quick Migration

Hope that this is what you were looking for,
Thank you.

[renebos]

The QuickMigration was exactly what i was looking for, but unfortunately the targetdevice is not supported through its license (free version?)

[Dima P.]

Hello Rene,

In case you are using Free Esx(i) - you are correct. There is a huge discussion about it here http://forums.veeam.com/viewtopic.php?f=24&t=10691

To cut the long story short the explanation is following:
Veeam utilizes an API provided by VMware. If that API is open Veeam will Backup/Recover. The API is closed on Free ESXi. The API is open on any licensed version of ESXi.