Enabling File Backup Encryption

[jcofin13]

If you have a immutable storage and backup nightly with synthectic fulls happening once per week and offloading to aws. You want to go into your job settings --> storage-->advanced-->storage tab and check "enable backup file encryption" .....will turning that on after you have many established backups cause any issues?

Meaning...will it:
1. cause a new backup chain to start?
2. a new full backup to be needed doubling the space used for the backup job?
3. cause any issues with the data doubling or growing in size for the aws data?
3. any other issue?

Im noticing a job id like to turn it on for but i dont want to create a mess.

[Mildur]

Hello jcofin13

Enabling encryption on an existing job requires an active full backup. A new chain is started and FastCloning cannot be used with the old existing backup files.
It will require more space till your old backups chains can be deleted according to the retention policy.

Best,
Fabian

[jcofin13]

Thank you. That is what i was afraid of.

Right now some of those jobs were set with "keep certain full backups longer for archvial purposes" and for 5 years. I suspect those are then immutable for 5 years then and wont age out for a very very long time.

[jeremyrogers]

IIRC, the Immutability period will reflect the value set on the repository, not the retention settings within the job itself. Your GFS backups will not be immutable beyond that value.

[jeremyrogers]

Clarification: the "Make recent backups immutable for xx days" value under Repository section (assuming an LHR repository is in play) or similar if using another vendor's repository solution that's Veeam-managed.