vSphere 7.0 U2 Support

[HannesK]

Hello RLeon,
https://helpcenter.veeam.com/docs/backu ... ml?ver=110

We (like anyone else) cannot see the future. We document things that broke in the past (that's what we know as opposed to future that is always uncertain). That means for VMware we document the updates that are supported. We know that updates regularly break things. As for patches like the "c" you are asking for never broke anything in the past, we expect everything to work, meaning we support it, yes.

If we would start limiting support on each build listed in https://kb.vmware.com/s/article/2143832, then we would get flooded with requests every few weeks "when do you update the user guide?". So stating support for each build is probably against the interests of most of our customers

Best regards,
Hannes

[rleon]

Thanks HannesK. All cleared.

[Regnor]

@Rleon: You can check the following KB for the supported vSphere versions; only major releases are listed there.
https://www.veeam.com/kb2443
EDIT: Didn't see the posts on the next page, sorry

[Gostev]

we're now thinking to just ship vSphere 7.0 U2 support patch w/out support for CDP as a first step. Then follow up with another patch and included the updated CDP I/O filter driver there.

All, we've just published P20210525 which extends vSphere 7.0 U2 support also to the CDP functionality. Thank you for your patience!

[crackocain]

Hello

Is there any way to disable KB2443 warning? Registry key or etc?

[mkretzer]

@Gostev after P20210525 installation the first backup got stuck in the middle of the backup (only 5 VMs) - currently rebooting all Veeam components. If it does not help i'll open Sev 1 case!

[mkretzer]

After a reboot the same test backups (and more) run without issues again... Still strange.

[Gostev]

Is there any way to disable KB2443 warning? Registry key or etc?

Make sure you actually read it

[Brian_Larsen]

Hey

So is it only 7.0.2.00100 that Veeam currently supports, or any build number from 7.0.2?

Right now in my vCenter i see the following two updates.

7.0.2.00100 Apr 27, 2021
7.0.2.00200 May 25, 2021

Brian

[Mildur]

Read the official post from Hannes:
post416422.html?sid=7f195d2e6af8616a916 ... 79#p416422

a,b,c,d patches are always supported.
7.0.2.00200 is: 7.0 Update 2b

[Brian_Larsen]

Hey Mildur

Thanks for replying.

It is just, if you do update vCenter to version 7.0.2.00200, you get a warning in Veeam B&R:
Your vCenter Server API version is higher than the version this product build has been tested against, which may cause issues with some functionality. Please refer to Veeam KB2443 for vSphere version support information. This warning will not be logged again.

I just downloaded and upgraded Veeam B&R to version 11.0.0.837 P20210525 yesterday, so i strongly assume there is no newer version or patch from Veeam at this moment.

So just wanted to make sure that version is also supported.

[HannesK]

I also have 7.0.2.00200 and I cannot find that warning. Can you please share your case number?

[Brian_Larsen]

Hey HannesK

I don't have a case number. But if you like, i can share logs or anything else you may find relevant.
I can give you some context to explain my scenario, don't know if that helps, but I guess it cant hurt either.
Yesterday i upgraded Veeam B&R to version 11.0.0.837 P20210525. Then i upgraded vCenter, and also the ESXi host to latest version.
I should mention that the vCenter upgrade did not go smoothly, i had to preform the steps explained in this KB article (https://kb.vmware.com/s/article/67179) to make it work.

All backup jobs completed last night, but one job had this warning:
Your vCenter Server API version is higher than the version this product build has been tested against, which may cause issues with some functionality. Please refer to Veeam KB2443 for vSphere version support information. This warning will not be logged again.

So i was just asking here to find out if I do have a problem, or if it is safe to ignore the warning.

[Gostev]

What you experience is certainly not expected, and normally this warning should not be ignored because it indicates you're running an unsupported/untested configuration. You should open a support case and have our support engineers review your logs and make the conclusion what is causing it. Thanks!

[Brian_Larsen]

Hey Gostev

Okay I will open a case just to be sure.
But as far as I understand from all the feedback here, vCenter 7.0.2.00200 is supported by Veeam B&R version 11.0.0.837 P20210525. I have two more similar environments i have to patch, and i feel more comfortable proceeding, now that I know it is supported.

Thanks.

[Gostev]

Well, to me the warning indicates that the patch was not correctly or fully installed, meaning your NOT running a supported configuration.

[Brian_Larsen]

I have created a case (#04842222), and uploaded logs for the job that gave the warning.

[Brian_Larsen]

Well, to me the warning indicates that the patch was not correctly or fully installed, meaning your NOT running a supported configuration.

I understand your point. I will wait and see what the support team finds.

[jamerson]

I am not sure if this been asked before.
but does the latest update support ESXi-7.0U2a-17867351-standard (Build 17867351) ?
we have/must update 4 ESXI servers for one customer I don't want to have a broke backup if we update it.
HPE advise to update the drivers / bios and also the the latest U2A.

[Mildur]

Read the last messages in this topic or use the intopic search button.

post416422.html#p416422

post417308.html#p417308

[FrancWest]

In last nights community update I read there will be a cumulative patch for the V10. Will this patch also include official 7.0U2 support?

[Gostev]

No, only bug fixes for existing V10 functionality - but no new features for sure.

The main idea is to help folks who are stuck with "old" environments due to various legacy platform versions in use and are fine to keep it "static" without any changes for the time being, for example because it is a "dark site" without Internet access.

Those customers who like and can afford to be on the bleeding edge of technology like the latest vSphere version are of course expected to also upgrade Veeam to the latest version.

[FrancWest]

Ok, thanks. If you plan to introduce an LTSC version, will you also think about adding such support? We are now in an officially unsupported configuration since we had to update to U2 because of the vCenter security issue (we were at V7.0 U1 with Veeam V10), but we can't update to V11 yet since our service provider still hasn't updated their systems to V11.

Or perhaps implement backwards compatibility for newer versions with the previous version for cloud providers?

[Gostev]

I think this is something we will definitely try, but based on the history I highly doubt we will be able to universally guarantee. I believe VMware calls these releases "updates" just for them to look minor on paper, perhaps not cause re-certifications in customer environments etc. But this does not really change the reality: these are not updates but rather full blown minor releases on a 6 month dev cycle which bring major changes that are often breaking, and backporting fixes will not always be possible or feasible.

All service providers are fully expected to be on the latest V11 version now. In fact, you won't even be allowed to install this new V10 patch anyway if you have a service providers who is not on V11. Basically, we need to keep the number of possible combinations and test scenarios reasonable for our QC team.

[Gostev]

Heads up, looks like there's a major bootbank regression in ESXi 7.0 U2 which apparently won't be fixed until the next quarter.

[Regnor]

From what I've read so far, it does only affect hosts with SD/USB media?

[NightBird]

Related to this one, isn’t it ?
https://kb.vmware.com/s/article/83376

This KB was released one of the first week of May

[Gostev]

Does not appear to be related based on the Reddit post... very different errors + the cause is not a partition corruption but rather:

scsiPath layer is keeping cancel commands and no commands can push to driver/hardware. So the up layer will not able to communicate with boot device and shows boot device is 'lost'. But on hardware, the device still there, just not able to receive any request.

[NightBird]

vmhba32 so related to sdcard too

[wishr]

Another reminder that an upgrade to the most recent version of any software should not be done immediately after the launch and requires thoroughly testing