Veeam 8 Patch 1, one VM lost the VMDK

[christian.mebs]

Hello,

Since I have upgraded to Veeam 8 Patch 1, I have some problems on 1 VM (SRVAD). My configuration is quite simple, 2 ESX + 1 SAN and 8 VM.
The backup of the différents VM is OK, but after processing the SRVAD, the 2 VMDK are removed from the VM.
I just opened a case with the support team of Veeam: Case 00717834
Just removed the Patch 1 and everything looks good again.

Never had any problems when upgrading Veeam B&R, seems to be an isolated problem ?!?
But I want to be sure, because I have a lot of other clients to upgrade in the next days.

Please keep me inform.
Thanks!

[veremin]

Hi, Christian,

Let’s see and wait what support team says about the issue. The problem might not have to do with VB&R patch#1 necessarily, as there a lot of people who have updated their installations so far and you appear to the be first one to report that.

Also, being image-based solution, VB&R doesn’t touch original .vmdks, working mostly with snapshots.

Just out of curiosity – by saying that .vmdks were removed you mean the corresponding files were deleted completely or were rather detached from the source VM?

Thanks.

[christian.mebs]

Hi Eremin,

Thanks for your quick answer.

The vmdks were only detached from the vm. I need to add that this Vm is also acting as a veeam proxy.
By the way, we removed the patch and everything is fine again. On some others installation, we installed the patch 1 and, like always, the Backup are working fine.

Let's wait for the answer of your support team.
Kind regards

[christian.mebs]

Hi Eremin,

The first answer/action of your support is not very good...
They are asking me to force the proxy to "San Mode", but the proxy has always worked in Virtual App mode, the VM with Veeam is not connected directly to the SAN !!!
Are they really reading the logs ?!?

Well, I am now waiting for a good answer.
I cannot make strange tests with this installation, the VM which is losing the VMDK is AD,DNS, DHCP and File server...
I hope that they will find something !

Kind regards

[Gostev]

Eremin is climbing Kilimanjaro mountain for the next week or so

[christian.mebs]

Eremin is climbing Kilimanjaro mountain for the next week or so

Lucky Man !!!

[Gostev]

Yep, I do hope he is lucky enough to return

[holsten]

I have the same problem, I also opened a Case

[christian.mebs]

I have the same problem, I also opened a Case

I am finally not the only one !!!!

Regardind the poor answer that I have received from the support (They told me that my configuration was not good, but the same configuration was working with Veeam 6.5, 7 and , I decided to make some basic tests.
I removed the proxy from the VM that was loosing the disk, then I install the patch 1 and now the backup is working fine.
Next step, I will deploy the proxy (after one week of monitoring) to the VM and let you know if it's working fine.

Regards,
Christian

[Vitaliy S.]

The vmdks were only detached from the vm. I need to add that this Vm is also acting as a veeam proxy.

Do you mean that you backup your Veeam proxy server? Do you have any errors in VMware VM logs that can be found in the same directory as virtual disks reside?

[christian.mebs]

Hi Vitaly,
I had 2 Veeam proxy: one, the default proxy on the veeam server and another one on the SRVAD (VM that is losing the vmdk)
The 2 VM (Veeam + SRVAD) are backup with Veeam. (and was working before patch1)

[Vitaliy S.]

Ok, thanks for clarification. I wonder if there are any error messages in VM logs when disk are removed from the configuration and are not brought back.

[christian.mebs]

I will check this point and come back to you.
So far, without the proxy role on this VM, everything is going fine.

[averylarry]

I really debated whether to post this. However, I have now had 2 separate installations exhibit this problem. The issue described in case #5198970 has returned in 8.0.0.917 (I did not see it in the initial 8.0 version).

I debated on posting this because I really don't have time to open a support case and generate log files and everything else. I can "fix" it by disabling all but 1 proxy server.

[averylarry]

Gostev/Vitaliy/Alexander/Vladimir etc. -- I probably should have just sent a PM to one of you. Feel free to delete this thread.

[foggy]

Ted, I've briefly reviewed the case (an old and huge one) and hope I'm merging you in the correct thread. Is this the problem you're seeing? I will check with QC whether they have met something similar, however opening the case, if possible, would be much appreciated.

[foggy]

Well, actually contacting support is recommended, since you will be given a private fix for this issue (already available). Also will be included with the next patch.

[averylarry]

Thank you.