Update 4a and 6.7U2

[mkretzer]

Now that 6.7U2 is out: how long will it take for Veeam to verify if 6.7U2 is safe to use with 4a?

We plan to upgrade our VCenter from 6.0 in the next week and are thinking about going directly to U2.

[Gostev]

Normally a couple of weeks after GA date (regular full regression testing cycle length), after that it will depend on the results.

[mkretzer]

Thanks. How big is the risk if we just update VirtualCenter and not the hosts at first?

[Andreas Neufert]

Usually it breaks something there. But as Anton shared in the release notes we did extended tests with early access versions and Update 4a and made it compatible with the early access version. As there are changes between these version and the release, we want to be sure and perform full regression testing, so that our customers will not have negative experience with it.

[Andreas Neufert]

I double checked the download page of VMware and it is still not there. It was just the announcement I guess.

VMware noted at their blog:
https://blogs.vmware.com/vsphere/2019/0 ... prise.html

Michael Adams - Sr. Director of VMware vSphere Product Marketing
April 4th, 2019
Sorry about any frustrations. When we publish a blog about functionality it will be available within that quarter.

So we can not test final version until it is released. (Of course we continue to test with the pre-release versions that VMware shared with us. So far so good.)

[Drizzt]

I got the updates through Update Manager today.

I am deploying it it my lab

[chalac]

6.7U2 hast just been released and is now available for download.

[mkretzer]

Is Veeam already testing with the final code? Are there first results?

[Gostev]

We're busy updating our labs as well.

[jmc]

Hello, everybody,

I accidentally didn't think about Veeam anymore and upgraded the vCenter to version 6.7 U2. After noticing that it wasn't a good idea, I tested everything and couldn't find a problem.

I tested the following (all in production environment)
- Backup (Full and Reverse Incemental)
- Restore Full VM and also FileRestore Windows
- backup copy
- Sure Backup
- vcenter rescan

so far there have been no problems. But I don't have any special storages, only direct and cifs.

The ESXi are still running under 6.5 last patches.

I think I was lucky in this case, that not so much was changed, which is important for the backup.

mfg
jeff

[Andreas Neufert]

Hi Jeff,

we made some changes in Update 4a to address some things like new virtual hardware version. At this point in time we worked without issues against the vSphere 6.7 U2 Early access version. As shared above we will need to do a sanity check with a complete regression testing QA run to claim official compatibility and support.

Thanks for understanding and again thanks for sharing your experience.
Andreas

[jmc]

Hello, Andreas,

you're absolutely right and usually I'm always waiting for your official release, too. I have no idea why I didn't think about it yesterday.

For that @all please wait for the release of Veeam. That I don't have any problems so far doesn't mean that it's the same for all installations.

Jeff

[Andreas Neufert]

Some news from Anton Gostev from the weekly Forum Digest:

VMware vSphere 6.7 U2 has been released last week – so we've updated our labs with the GA version and are running it through its paces now. I don't expect any issues, because the GA build appears to be the same as the RTM build – which we have been testing against for the last couple of weeks. And as you know, Update 4a already has the required code modifications for vSphere 6.7 U2 support included (like virtual hardware version 15 compatibility) based on the pre-release U2 builds. Overall, this vSphere release worked much better for us thanks to VMware opening access to the pre-release builds – big kudos to them for doing this, and to everyone who helped this happen with their [sometimes very vocal] feedback!

[bovie2k]

I figured since its been about a week I would check in and see if there is any new news on 6.7U2 Support?

[Gostev]

Please see my first post in this thread

[cedrock]

Hi Veeam Team

Is there an official channel to get the newest information and update about this?
We need 6.7U2 badly but wait for veeam to be ready...

Many thanks

[Andreas Neufert]

Hello Ced,
thanks for your request. We will update release notes and communicate it throug forum digest and on request posts like this one.

[Gostev]

Hello everyone, our QC has now completed the full regression testing cycle of Update 4a against vSphere 6.7 U2, and found no issues. So, we're now ready to officially support vSphere 6.7 U2 with Update 4a. I've already notified the support management of this. Thanks!

[mkretzer]

@Gostev
Excellent! Thank you for this information! Will the documentation/release notes of 4a be updated?

[Andreas Neufert]

Yes, in the next working days

[masonit]

Hi

Is 6.7 U2 supported with only Update 4?

\Masonit

[Andreas Neufert]

Hi Magnus, only with Update 4a as we have added some functionallity for vSphere 6.7 U2. https://www.veeam.com/kb2926

[ibrahimbayrak]

Hi,

i need to install Veeam B&R U4a but, i have to install first Veeam B&R U4 and i cound not find that update. i found that links https://www.veeam.com/kb2883 . That article have download link but, when i try to download it, i downloaded another one. i search that update build number : "Veeam Backup & Replication 9.5 U4 9.5.4.2399 " thanks for your helps.

[wishr]

Hi Ibrahim,

Please check here. You may download the 4a ISO.

Thanks

[Andreas Neufert]

Please use the download link at: https://www.veeam.com/kb2926
When you use the iso it will first install U4 and automatically update the installation to U4a during the process.
Or you can download just the update.

KB2883 is the Day 0 Update for those that have used the Update 4 RTM version, mainly our partners.

[ibrahimbayrak]

Hi Wishr and Andreas,

Thanx a lot. I will try your solutions.

[rb4]

Does this include support for 6.7U2a?

[Gostev]

New builds of supported vSphere versions (which are essentially bug and security fixes roll ups) are always supported by default. This is no different from how we support new Windows Updates in the Microsoft world, for example. Thanks!