In order to use the LUN on ESXI B you need to deploy a VM that can have storage added to it and then added to Veeam as a Repository to send the data to.  Veeam does not send directly to ESXi datastores.

Hi, you can do this two ways, firstly instead of a backup you can “replicate” your VM to ESXi host B, this way it’s an uncompressed “ready to go” VM on the second host. Alternatively you’d need a VM on host B with a VMDK that you would use as a second repository server and backup to that disk.

Id suggest if you only need short term protection (say a few days to go back through) a replica will be easier potentially.

Are these hosts in the same network or different sites etc?

Yes this is definitely another option to save deploying a server on host B.

Hi! Firstly, thanks for the quick answers!

Ok, i see...Wow so much time wasted, haha.

I think will create a VM on the ESXi host B, because it needs to be incremental or differential.

But when you say replica, it’s going to “copy” the whole 60Gb ?

Another question, if you know the answer :

Can i assign this “backup-lun” to Windows 10 iSCSI initator ?

The replica will copy the initial 60GB but then just increments after that.  Yes you can assign the LUN to the iSCSI on Win10 long as it can see should be no issue.  Then add that as repo to Veeam.

If you make a VM with a VMDK no need to attach an iSCSI LUN as the VM will see it as a local disk.

Never time wasted, it’s time learning!

Chris has answered the points around incrementals etc already

If you’re new to Veeam check out the Veeam University section for some quick getting started style videos, might help you lay the foundation of the plan in your mind.

Ok thanks for your precious help guys! Thanks for you prompt responses again, as i am in lack of time!

Wish i could give you both the Best answer!