Veeam copy VS Vmware Clone

[vbourbeau]

Hi,

I'm new with Veeam and it have something I don't understand. I have a host with 2 datastore (2 different Raid controler) when I do a vmware clone it took 2 min so around 180mb/s. But when I do a Veeam copy or replication of the same host with same datastore it took 20 min +- 20mb/s.

Why? What can I do to optimise that? Is because the data travel between LAN?

Thank you

[Vitaliy S.]

What does Veeam replication job show as the main bottleneck? You can review that in the job session details.

[vbourbeau]

In the load section I see:

Load:Source 3% > Proxy 10% > Network 0% > Target 99%

[Shestakov]

Vincent,
Since the bottleneck is target, what transport mode was used for the target proxy?
It should be written in the brackets after " Using target proxy Proxy name for vm/disk name"
Thanks!

[Vitaliy S.]

Target bottleneck means that target datastore is the "weakest" component here. Can you please tell us a bit more on our setup?

[vbourbeau]

I don't have proxy
The Veeam server are locate on the ESX where the problem are.
I'll try to configure a proxy on it it's the first time I do it. In fact I don't realy know what the proxy do more...

[Shestakov]

You can grant a proxy role to VM on the target host to leverage hot-add transport mode.
The Data Mover Service on the target proxy uncompresses VM data and stores it to a datastore in a native VMware format.

[vbourbeau]

Ok here are my infrastructure

ESX1
SAN1
ESX2
SAN1
LOCAL Storage

VEEAM
VM on ESX1
Proxy (use with Virtual appliance mode)
VM on ESX2
VMTest
VM to backup (20go)
on ESX2 SAN

Test done:

Clone with vmware VMTest from SAN to LOCAL Storage take 2 min
Replicate with veeam and proxy from SAN to LOCAL Storage take 15 min

[DaveWatkins]

If your proxy is on ESX1 and the local storage which is the target of the backup is on ESX2 then it'll be using the management interface for that portion (I think) and that will be your problem, but the Veeam proxy on ESX2 and it'll probably start working as you expect

[Shestakov]

Dave is correct, to speed up replication you should grant some VM on ESX2 a proxy role.
Another way to improve replication performance is WAN Acceleration.

[vbourbeau]

yes the Proxy are on ESX2 where the local storage are.
and the Veeam server on ESX1

For WAN Acceleration I think I need other license.

[Shestakov]

Do you have both source and target proxies? If yes, they should be used for the replication job automatically.
WAN acceleration between 2 sites is available in Ent+ license only.
Thanks!

[vbourbeau]

When I look here https://helpcenter.veeam.com/backup/vsp ... e_hiw.html

I notice that the hot-added disk are the source one... No where is said the target disk are hot-added to the VM.

[Shestakov]

Because that`s the chapter about backup, not replication.

[vbourbeau]

I try backup job, replication job and file copy. All with proxy on the host in lan mode and virtual mode. +- 20 mb/s
And a VM clone on vsphere +- 200 mb/s

[Shestakov]

Could you confirm that transport mode used for backup job is "hot-add"?
It should be written in the job`s logs as:
Using backup proxy VMware Backup Proxy for disk Hard disk 1 [hotadd]
If the transport mode is hot-add, what is your bottleneck statistics?
Thanks!

[vbourbeau]

I try virtual appliance and when I look on the proxy I see 2 disks mount on the proxy. The first one are the source disk and the second one the destination.
In my case both are on different storage. And with windows perfmon I monitor the read write on both and I got 20 mb/s.
After this test I add 2 disks on the proxy, don't have choice to format in NTFS here. And I copy file between them... I've got 200 mb/s.

I don't understand... I create the same patern.

[vbourbeau]

Shestakov

I don't find any line looking like yours. The closes one are:
Using backup proxy proxy1 for [VolB1] printsvr/printsvr.vmdk

but I found lot of "hotadd" in the log. [HotAddDisksRemover]

[Gostev]

Please work with our support to help you with ensuring hot add is used on both sides, this will allow Veeam job to complete faster than VMware clone.

[vbourbeau]

Here the support answer:

"Veeam Copy is a full block for block and target is always thick provisioned, whereas VMware Clone only copies used blocks and can maintain disk format. Obviously these two can be compared as they are not the same thing in the slightest."