Comprehensive data protection for all workloads
Post Reply
it.loepa
Novice
Posts: 4
Liked: never
Joined: Feb 19, 2015 9:32 am
Full Name: Loepa IT
Contact:

Version History / Release notes

Post by it.loepa »

Am I the only one who is confused by the Version History / Release notes Update Versions?

I personally don't really see corrections from 2 to 2a or 2b, I've got the feeling that these are simply the same entries in release notes.
For instance I've got the feeling that this sentence:
Tape- Synthesized full backup enhancements. Synthesized full backup functionality has been reworked for better reliability, performance and support for very large backup files.

is mentioned in every release. So because I have some kind of issues I can't control, if there has something change. Normally I'm happy with the new features / release notes at veeam but these two updates confused me a lot. :?:
veremin
Product Manager
Posts: 20283
Liked: 2258 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Version History / Release notes

Post by veremin »

Update 2 was superseded by Update 2a which then has been superseded by Update 2b. That's why Release Notes contains cumulative information, so, people updating from patch#1 know what is fixed and added in the subsequent product version. Thanks.
VladV
Expert
Posts: 224
Liked: 25 times
Joined: Apr 30, 2013 7:38 am
Full Name: Vlad Valeriu Velciu
Contact:

Re: Version History / Release notes

Post by VladV »

But what about what 2a and what 2b contains for people coming from 2?
veremin
Product Manager
Posts: 20283
Liked: 2258 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Version History / Release notes

Post by veremin »

Just sever bug fixes including VDDK 6.0 issue with virtual disks having the same name. Excerpt from one of the weekly digests:
Gostev wrote: B&R 8.0 Update 2a was officially released around 10 days ago, but as you may have noticed, B&R update check still does not "see" one. The reason is yet another critical issue we have found in VDDK 6.0 last week, which forced us to rebuild the update code again, now as Update 2b – adding a workaround for this single issue. While it's again a corner case, it may results in B&R quietly creating unrecoverable backups for certain VMs, which previous versions of VDDK had no issues processing (see KB2042 for more information). Sadly, VDDK 6.0 has been one of the worst VDDK releases in terms of the amount of new bugs introduced. More evidence to keep using SureBackup for catching those environment-specific issues!
Thanks.
Gostev
Chief Product Officer
Posts: 31526
Liked: 6700 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Version History / Release notes

Post by Gostev »

Let me explain this a little bit more. First, there is no difference in the release notes between any of the Update 2 builds, so don't look for them. The only difference between different builds is a handful of point bug fixes in the newly introduced functionality.

We did not publish any of the initial (pilot) Update 2 builds through the update notification functionality built into B&R v8, and Update 2b was actually the first build that was published. Thus, the differences between pilot builds and the final build does not need to be widely known, as most of the users will go straight to Update 2b. That said, our support does have all the information on those point fixes between pilot Update 2 builds available, and will be happy to share with you.
Post Reply

Who is online

Users browsing this forum: Baidu [Spider], Ivan239, Semrush [Bot] and 119 guests