Veeam User Warns About Item-Level Retention in Microsoft 365 Backup (Restore it All Podcast #102)

A Veeam user warns of what he felt is a confusing option in Veeam Backup for Microsoft 365. He says he likes the product, but that the first retention setting mentioned in the documentation (item-level retention) might not do what you think it does. He thinks everyone should use snapshot-level retention, which behaves more traditionally. We also discuss IBM Spectrum Protect (AKA TSM) a little bit, as they also use that product. Our guest is speaking on conditions of anonymity, so we gave him a fake name (Puddleglum) and altered his voice in the recording. (Want to talk about your environment, but don’t want to use your name? We’d love to have you on and we’ll keep you anonymous too!)

----- Signature and Disclaimer -----

Written by W. Curtis Preston (@wcpreston). For those of you unfamiliar with my work, I've specialized in backup & recovery since 1993. I've written the O'Reilly books on backup and have worked with a number of native and commercial tools. I am now Chief Technical Evangelist at Druva, the leading provider of cloud-based data protection and data management tools for endpoints, infrastructure, and cloud applications. These posts reflect my own opinion and are not necessarily the opinion of my employer.

2 thoughts on “Veeam User Warns About Item-Level Retention in Microsoft 365 Backup (Restore it All Podcast #102)

  1. Jacob W. Stateman says:

    Differences between “item level” and “snapshot level” retention modes are well written in the product documentation… And, oh, well… Mr. Preston works for a Veeam competitor… This explains a lot.

    • W. Curtis Preston says:

      You clearly didn’t listen to this podcast episode, nor any others that we have. We talk about Druva competitors all the time. We’ve had customers and representatives of multiple products on the podcast. We even have @backupdave from Veeam coming up in an upcoming episode. So please take your ad hominem attack (and invalid email address) elsewhere.

      Our guest said he likes Veeam and is an overall happy customer. He approached us and asked to warn other Veeam customers about this feature. Neither he nor we ever based the product.

      As to your comment on the documentation, it was his misunderstanding of the documentation that created the problem. So perhaps the documentation could use some clarification.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.