As a heads up, we're planning to initialize our update servers with Veeam Backup & Replication V11 this week. This is mostly for our partners to prepare for some calls from their clients in conjunction with the notification. As a reminder, we notify paying users of new major releases with a significant delay – only once the new version stabilizes and has most of the known regressions and common support issues patched up. The update notification from the backup console generally means that in our opinion, everyone will be better off upgrading to this new release because we passed the threshold where pros of upgrading overweight the comfort of sticking with a previous release aka "don't touch what's working" principle.
Nevertheless, here I must also share that soon and for the first time ever we will be releasing a new cumulative patch for the previous major release (V10). As you know, according to our existing support policy non-current releases are not supposed to get updates in principle. So, why are we doing this? The primary reason for this exercise is to do a real-life test our R&D processes and workflows for compatibility with the possible introduction of a long-term support channel (LTSC) in the future. While we're still defining what we can realistically do to have periodic LTSC releases without impacting the pace of our innovation too much, it is clear that such releases will require on-going patching – which is what we're "training" on doing here. For the cumulative patch to be actually useful for V10 users, we will include fixes to a few common support issues and bugs that directly impact TCO, as well as backport some security improvements from V11. This way, customers who need to stick with V10 for whatever reason will be in a much better place. Nevertheless, V11 remains the recommended release without a doubt.