Image Based Backup Retention
I know that image backups are different, but the settings are the same for retention. That's where I'm getting confused. I thought setting the file version age to 90 would give me a nice spread of files. Most of the time you only need the most recent version of a file, and occasionally one previous version if they save over top of something
I assumed with 90 day file version age I'd have a minimum of the file at 3 points in time: month 1, 2, and 3's full backups. Now that you got me thinking, I guess without versioning turned on the full backups will contains 3 copies of the same file if it hadn't changed in the last 90 days. I think that's generally OK. I think that I thought the daily block jobs would give me more versions.
Realistically, if I tell my customer 90 day retention on their backup I want to be able to grab the file from the last 90 days. If they deleted it 180 days ago, that's too bad (if we agreed to 90). If I had "always keep the last version" on will that force an old blocks/full to stay around forever? I don't think I've seen that, maybe because people don't generally delete files as much as just adding more.
The reason I haven't messed with versions on block level might be my misunderstanding: If I have a file that changes daily and the full job runs every 30 days, and daily block level jobs... Wouldn't I be able to have 30 versions of that same file? Or without versions are we deleting the ones in the previous blocks? Maybe in this scenario keeping 3 version of the file will actually make the jobs smaller?
Can you provide a suggested settings for a block level job? for 30 or 90 days retention? I feel like I'm still fuzzy, although I've never had issues with the settings previously I think I had last version on, but I'm confused about that warning message after what tech support said about it.