Retention policy "type" greyed out?

[mrhcarlin]

This is probably a super obvious question, but I was just wondering why I can't change the retention policy type (item-level and snapshot-based) on a repository after the fact?

Admittedly my mistake, but I've set up my SharePoint and mailbox backups with the wrong retention policy type and need to change it to meet my organisation's needs.

Thanks,

Matt

[Mike Resseler]

Matt,

You need to start over again I'm afraid. Create a new repository with the correct retention policy. Point the job to the new one (Yes, this will be a new full backup) and keep the old repository so it gradually gets empty after the retention is over. (So you don't lose restore points, unless you don't care about older points at this moment).

We can't change it because the database schema for those two is not the same and therefore not compatible

Hope it makes sense
Mike

[mrhcarlin]

Hi Mike,

Thanks for the very quick response - perfectly explained!

I think I'll just start from scratch then because I've only run one job, so there's little chance of losing data in the time it'll take to start over.

Thanks again

Matt

[Ben.online]

Hello,

Is the "start over" procedure still the best/only way to go?
or can the migrate data https://www.veeam.com/kb3067 powershell be used.
It's not quite clear from the limitations

so migrate local to local repo on same disk with snapshot instead or item retention.

Kind regards

[Polina]

Hi Ben,

Move-VBOEntityData will do the job. You will get a notification that you're moving the data between repositories of different retention types, but other than that everything will work fine.
Do not forget about the difference between the two retention types and that this difference will define the completeness of the backup data set in your new repository.
For example, when moving from item-level to snapshot-based, some older historical data can be missing in the target repository after the move:
A tenant has 3 years of data (2024, 2023, 2022)
Repo A is item-level, 1 year
Repo B is snapshot-based, 1 year
If you 'start over' to repo B, it will get all the data from '22 to '24. But if you move backups from repo A, data created in 2022 that hasn't been modified since that time will be missing.

Makes sense?

[Ben.online]

Hello Polina,

Yes that makes sense.
Move is an option but will likely not create a complete backup set containing all data in the old repo and 365 tenant
So a new repository is the way to go for us.

Kind regards