Skip to main content
  • EN

Fellow Veeam Legend ​@MarkBoothman shared an interesting post on the VUG UK Community page and I thought it highly relevant to also be shared with the main Community as a whole as well.

Today Anton Gostev, Chief Product Officer at Veeam, created a couple posts on the Veeam Forums I think those anxious for the release of Veam Backup & Replication v13 should be aware of. Starting in v13, Veeam is beginning to deprecate some features, as well as streamline system requirements to make their product better, more secure, and performant. The posts can be viewed at the links below:

VBR v13 Deprecated Features

VBR v13 System Requirements

One item of note some of you Linux gurus should really be aware of in the Systems Requirements is the deprecation of CentOS completely → whether VBR or Agent for Linux. So keep that in mind. Some older OS and application versions are also being dropped. So if you haven’t migrated your systems/applications to a newer OS/version, you might want to start considering doing so soon, at least if you want to migrate to VBR v13.

One other major item to note for VBR, and I’ve shared this a few times in some question posts here on the Hub the past couple yrs → Reverse Incremental Backup Method will be going away. Yep...that’s correct. Time to get off that dated method if you haven’t already 🙂 For the rest of the info Anton shared, again...click either link above.

Best.

They're dropping the retention based on restore points. I believe many customer will need to adjust to that. I understand why the change but I always liked the restore point retention because it's easier to understand and explain to the customer how it works.

​@wesmrt - I made a comment in that Deprecation post asking for clairification if that was the case. Yeah..that’s gonna be a big deal for me. I don’t get that personally. I don’t use “Days”. And, I don’t want to. I backup up every 30min on a couple jobs so it’s critical to lose Restore Points as soon as they’re expired so I can regain storage space. There’s been times waiting for the whole next ‘Day’ to occur would be an issue. Most times, I’m fine, but there are times in the beginning of the school yr (I work at a school district) where a lot of data really gets added to some systems, increasing backup sizes (i.e. change rate increase).

​@wesmrt - I made a comment in that Deprecation post asking for clairification if that was the case. Yeah..that’s gonna be a big deal for me. I don’t get that personally. I don’t use “Days”. And, I don’t want to. I backup up every 30min on a couple jobs so it’s critical to lose Restore Points as soon as they’re expired so I can regain storage space. There’s been times waiting for the whole next ‘Day’ to occur would be an issue. Most times, I’m fine, but there are times in the beginning of the school yr (I work at a school district) where a lot of data really gets added to some systems, increasing backup sizes (i.e. change rate increase).

When space is tight I have way more control with points over days.

 

I get that compliance would require so many days, instead of points. but I’d prefer to not blow up the SAN and end up with no restore points 😀

Yep, which is/was my point (no pun intended) to keep restore points. That’s a bad deprecation imo.

Comment


Terms & Conditions