Does anyone know if the following issues are fixed in the new Update 3a that just went into the RTM build stage?
1) https://forums.veeam.com/veeam-backup-r ... 90-15.html
2) https://forums.veeam.com/veeam-backup-r ... 86-30.html
3) https://forums.veeam.com/veeam-backup-r ... 47591.html
4) https://forums.veeam.com/veeam-backup-r ... 46-30.html
5) https://forums.veeam.com/veeam-backup-r ... 48016.html
Thank you.
-
- Enthusiast
- Posts: 68
- Liked: 4 times
- Joined: May 09, 2017 6:33 pm
- Full Name: Mike G
- Contact:
-
- Chief Product Officer
- Posts: 31796
- Liked: 7297 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: question about Veeam Update 3a
Yes.
Basically, Update 3a should include fixes for every issue that had a hot fix created before beginning of June or so. And all of the above issues were reported in the early days of Update 3. I know most of them very well either from the corresponding forum threads, or based on the hotfix download statistics
In general, our updates are always cumulative, and there are only three possible reasons why existing hot fixes may not be included in the immediate update, from most to least likely:
1. They were simply too late to be included into the immediate product update (arrived after update's code lock). In this case, we will re-issue one for the new product build shortly after the update has been shipped - and include it in the following update.
2. The issue affects a single (or a handful) of customers, while the hotfix needs more thorough testing and/or is too risky to include for the entire customer base. In this case we will also re-issue one for the corresponding product build shortly after the update has been shipped - and make the decision whether to include it in the following update, or just keep hotfixing it indefinitely.
3. Human error is always possible, although quite unlikely these days when every support issue tracked directly in TFS. I don't remember any of such occurrences in the past years.
Thanks!
Basically, Update 3a should include fixes for every issue that had a hot fix created before beginning of June or so. And all of the above issues were reported in the early days of Update 3. I know most of them very well either from the corresponding forum threads, or based on the hotfix download statistics
In general, our updates are always cumulative, and there are only three possible reasons why existing hot fixes may not be included in the immediate update, from most to least likely:
1. They were simply too late to be included into the immediate product update (arrived after update's code lock). In this case, we will re-issue one for the new product build shortly after the update has been shipped - and include it in the following update.
2. The issue affects a single (or a handful) of customers, while the hotfix needs more thorough testing and/or is too risky to include for the entire customer base. In this case we will also re-issue one for the corresponding product build shortly after the update has been shipped - and make the decision whether to include it in the following update, or just keep hotfixing it indefinitely.
3. Human error is always possible, although quite unlikely these days when every support issue tracked directly in TFS. I don't remember any of such occurrences in the past years.
Thanks!
Who is online
Users browsing this forum: Bing [Bot], Vitaliy S. and 154 guests