Placeholder for Veeam 11a download link

[pirx]

After reading todays Digest I thought I could support you guys with this and speed up things a little... *scnr*

-> https://www.veeam.com/kb4215 <-

[wishr]

Hi Pirx,

Thank you a lot for your help!

As usual, we'll publish the links to the KB articles in the sticky topic of the corresponding product sections. Links to the corresponding topics: VBR, VONE.

Stay tuned!

[Gostev]

-> insert link here <-

Insertion completed successfully!

[Mildur]

Thanks
I will wait for Veeam One V11a, before trying out the new Update.

[wishr]

Hi Everyone,

Veeam ONE 11a is now available as well. Please refer to the link in my previous post for download details and what's new.

Thanks!

[Mildur]

Thanks

[marius402]

Can anyone please confirm the SHA-1 or MD5 checksum fir VBR 11A?

[marius402]

Thanx, Veaam posted the MD5. Solved problems

[dcolpitts]

The SHA1 and MD5 checksums don't seem to match what is posted. I've downloaded the .ISO multiple times, on multiple systems, at multiple customer locations locations this morning and I'm getting:

MD5: 54db9074a262e8ffe55f30197e037209
SHA1: 6871a6aa52c3b8ff3474f73aedde45c601fdfc97

While the KB says I should be getting:

MD5: 725278D59A1907221416A0B51486B7E6
SHA1: 75E5E38CCEC7C01CC07A99F2B9897D0BD0A4CE08

[veremin]

KB is being updated and currently provides a bit outdated information regarding ISO checksum, it will be fixed soon. Thank you for raising this.

I will post here, once the issue is resolved.

[veremin]

The KB article has been updated.

[Gostev]

This is because ISO was replaced to address the issue caused by updating VBR before updating VBO365 installed on the same server.

[pirx]

I see that there are new download, I guess its time for GA now? Is there already an update for RTM -> GA?

[Mildur]

GA Build is the same as EA. I don‘t think, that there will be a Day One Update.
The note in the release notes about EA was removed.

https://www.veeam.com/kb4215

[BrianBuchanan]

KB 4215 still seems to have the wrong checksums.
Wrong MD5: ba8e2a6c92286a5bfed3b714e03861cd
Wrong SHA1: db02d2dbb111e98a4eb9d4380a94c121c9da2b42

Code: Select all

certutil -hashfile "VeeamBackup&Replication_11.0.1.1261_20210930.iso" md5
MD5 hash of VeeamBackup&Replication_11.0.1.1261_20210930.iso:
54db9074a262e8ffe55f30197e037209
CertUtil: -hashfile command completed successfully.

certutil -hashfile "VeeamBackup&Replication_11.0.1.1261_20210930.iso" sha1
SHA1 hash of VeeamBackup&Replication_11.0.1.1261_20210930.iso:
6871a6aa52c3b8ff3474f73aedde45c601fdfc97
CertUtil: -hashfile command completed successfully.

Which match dcolpitts message above, so unless everyone is getting the wrong iso?

[pirx]

I also have hash SHA1: 6871A6AA52C3B8FF3474F73AEDDE45C601FDFC97 for VeeamBackup&Replication_11.0.1.1261_20210930.iso. I also see that the build number did not change from RTM to GA.

[veremin]

The product .iso was updated and replaced on the website on the October, 5th. The current .iso is VeeamBackup&Replication_11.0.1.1261_20211005.iso. The KB article provides new checksums for it.

However, the link in the KB has not been updated and still referenced the previous build. Kudos to the web-team we have just fixed it.

Now everything should fine: the build and its checksums should match.

Thanks!

[pirx]

So I have same build 11.01.1261 but VeeamBackup&Replication_11.0.1.1261_20210930.iso. So it's a different ISO but same build. Is there anything I have to do?

[veremin]

The previous build had some issues with deploying Veeam Backup for AWS appliance directly from backup console. We have fixed in the latest build.

If this is not something you are interested at, you can leave everything as is.

Thanks!

[pirx]

We usw Veeam4AWS, but can I update from a new ISO with same build number? Or will there be a 0 day update?

[veremin]

How exactly you are using it? Are regularly deploying those appliances from a backup server? Or just connecting to the ones already deployed in cloud?

[pirx]

We are just starting to use it, currently there is one AWS and one Azure appliance, they both existed before updating to v11a.

[veremin]

Then you can continue managing those appliance with your current build - no issues there. Thanks!