by a1lenski » Fri Dec 07, 2012 7:03 pm people like this post
Hi All, I have a very odd issue with a backup running from Veeam 18.104.22.168,
First Time the Job Ran (Full) The source VM was backed up using Hot Add, successfully. Second Run (Reverse Incremental), At the Hott Add stage, the disk form the source VM is added to the Replica VM of the Veeam VM running the Job, as opposed to the Veeam-VM itself, this causes the backup to fall back to Network mode and Run at a slower transfer rate.
I am running 5.0 VMware, Both The Veeam-VM and its replica Veeam-VM_Replica are within the same Virtual centre.
by dellock6 » Fri Dec 07, 2012 8:31 pm 1 person likes this post
Usually Veeam-VM_Replica is powered down and kept only to failoveer in case Veeam-VM crashes, so how can it happen the job do hotadd to this VM??? Maybe you created the replica VM using default settings, and you ran replica while the VM itself was doing hotadd-based backup? I've seen this behaviour while replicating some proxies: they were doing hotadd backups, so they had their own disk (scsi0:0) and several other disks coming from the hotadd. Replica tried to replicate also all these disks. Configuring replica to replicate only scsi0:0 solved the issue... Do not know however if this is your case...
by a1lenski » Mon Dec 10, 2012 3:33 pm people like this post
HI Guys, Thanks for the responces, It does seem very strange. I am pretty sure the Replica-VM was produced when no backups were running. It is in a powered off state incase of a crash, since I am not 100% on its stae when created I will blow away the replica VM and re-create.
I have only seen this with one particular Job so far but I was not watching while the other scheduled Jobs run as I am investigating a slow backup issue for that particular Job, I created the Job after updating Veeam to current version. I changed how the repository was being accessed from a CIFS connection to an iSCSI one provisioned directly to the Veeam-VM using the MS initiator. This has improved the backup speed. I can check and advise if this occurs with any other jobs.
I am thinking that somehow the GUID for the VM is wrong / confused and when Veeam is calling the VMware backup API it is selecting the wrong machine, the power state of the VM shouldn't matter when adding or removing disks to it, as Hot add is just attaching the VMDK to the VM using the Vmware API.
by foggy » Tue Dec 11, 2012 10:12 am people like this post
As far as I know, it is not possible to have two VMs with the same UUID in vSphere environment, so this should not be the case. However, VM UUID conflicts can be easily identified with the help of Veeam ONE, for example (it will report the "VM instance UUID conflict" alarm in this case).
I would recommend to investigate this with our technical support, probably debug logs will reveal the reason of this behavior.
by pcrebe » Mon Apr 21, 2014 1:20 am people like this post
Hi, I've got the same problem. Veeam sw hot adds disks to proxy replica servers, that are turned off, using failing over to network mode. I need deselect the Automatic proxy servers option and specify the proxy servers i want use.
I've EnableSameHostHotaddMode active for the nfs locking
by v.Eremin » Mon Apr 21, 2014 8:53 am 1 person likes this post
What has been said above still applies here - the situation when VB&R tries to attach disks to powered off VMs looks unexpected. So, feel free to open a ticket with our support team and let them investigate it directly. Thanks.