file share backup retention settings

[ejenner]

Hi guys,

What are people doing with these settings on this page for the new type File Backup which came in with Version 10?

[Natalia Lupacheva]

Hi EJ,

could you please clarify what exactly you are looking for?
Just in case, these settings are described in helpcenter:

3. Use the Keep all file versions for the last field to specify how long copies of all recent file versions in the selected file share must be kept in the backup repository. You can restore the entire file share to any restore point within the period specified in this setting.
If, for example, Keep all file versions for the last is set to 30 days, the backup repository will store all file versions that appeared at the file share during the last 30 days. At the scheduled time on the 31st day, the file share backup job first backs up new file versions and saves them to the backup repository. Right after that, file versions older than 30 days (created on the 1st day) are either deleted from the backup repository or moved to the archive repository if the Keep previous file version for check box is selected and the archive retention is configured.

4. If you need to keep versions of some files for a longer time after they are moved from the backup repository, you can configure archiving options to move file versions to a cheaper archive storage, for example, an object storage.
To use the archive repository, select the Keep previous file versions for check box. In the fields on the right, specify the number of months or years during which backup files must be retained.

This setting denotes a time period starting from the creation of the backup files in the backup repository, not from the moment when the file versions are moved from the backup repository to the archive repository.

So the configuration here depends on your needs.

Thanks!

[ejenner]

I'm asking for opinions from other people on how they've configured it and how they decided what to implement.

[foggy]

Hi EJ, these settings should be entirely defined by the RPO for files adopted in your company, so is specific to every environment. But let's see if anyone chimes in with his experience.