Skip to main content
  • EN

Hello,

We currently have backup jobs configured in Veeam Backup for Microsoft 365 (VBM365) with a retention period of 6 months.

We would like to stop some of these backup jobs, while retaining the existing backup data for a period of one year.

We have a few questions:

  1. If we change the retention policy of a job to one year and run a final backup, will the new retention period be applied to the previously backed-up data?

  2. If we disable the job after modifying the retention, will the new retention still be applied to the existing backups?

Finally, could you please advise on the best way to ensure that our existing data is retained for one year, even after the backup jobs are stopped?

Thank you in advance for your feedback.

With Veeam for Microsoft 365, retention is applied to the backup repository, not the job. To answer your questions:

  1. Changing the retention policy on the repository will apply to all backups on the repository, including previous backups.
  2. Yes, if you disable the job after applying retention, the new retention will still apply to the existing backups.

With this in mind, the best way to ensure data is kept for a year (assuming your original repository can’t have it’s retention raised to a year) is to create an additional repository with the desired retention, and migrate that data to that repository. However, it appears that this only supports moving from a JET-based repository to object, or JET-based to JET-based

You could also set up a copy job to keep the data for the retention required as well as an alternative solution.

See here - https://helpcenter.veeam.com/docs/vbo365/guide/vbo_new_copy_job.html?ver=80

 

You could also set up a copy job to keep the data for the retention required as well as an alternative solution.

See here - https://helpcenter.veeam.com/docs/vbo365/guide/vbo_new_copy_job.html?ver=80

 

That’s a great idea and much cleaner than trying to migrate the data.

You could also set up a copy job to keep the data for the retention required as well as an alternative solution.

See here - https://helpcenter.veeam.com/docs/vbo365/guide/vbo_new_copy_job.html?ver=80

 

That’s a great idea and much cleaner than trying to migrate the data.

To me migrating data is not a bad idea but copy job is easy. 😀

Morning,

The downside to a copy job is that you’ll only copy the latest restore point not the entire history.

 

For more information on how retention works in VB365 please see:

https://helpcenter.veeam.com/docs/vbo365/guide/retention_policy.html?zoom_highlight=Retention&ver=80

Comment


Terms & Conditions