Switching to encryption in copy job

[FrancWest]

Hi,

Case #04471735

we decided to enable encryption on our existing copy jobs. So after enabling it, we did an active full to activate it on the copy jobs. However, after doing the active full, this isn't listed as a restorepoint of type full. Only the incrementals after that active full are listed as a restorepoint with type 'incremental'. Why is this?

Also, how can we cleanup the existing chain, so that only the encrypted restorepoints are present in the repository? Since this was quite a new repository, we don't mind losing the old restorepoints after some newer encrypted restorepoints are begin created. Will manually deleting all restorepoints before the active full and then rescanning the repository work?

Franc.

[foggy]

Hi Franc, for proper cleanup, you can use the forget missing restore points functionality - delete the older part of the chain manually and then 'forget' them in the Veeam B&R console.

[FrancWest]

Hi, ok, so that's a valid procedure to do in this case when switching to encryption on a existing copy job?

And what about the active full not being listed as a restore point? I was afraid that deleting the files before the active full and forgetting the missing restore points might led to issues, since the active full isn't listed as a restore point in the console.

[foggy]

You do not need to remove previous restore points after switching to encrypted backups, but if you want to do so - you can do it this way, right.

As for the active full issue - I'd recommend taking a closer look at what happened with the help of our engineers.

[FrancWest]

Ok, will do, thanks!

About the removing. We are going to use these backup copies as a source for storing them off-site, so we need them to be encrypted. Since these unencrypted restorepoints will also be used for GFS retention, we can't have the risk of storing them unencrypted externally. And deleting them all, prior to doing the active full is risky also, since we all know Murphy

[veremin]

Can you provide a screenshot of backup properties where the newly created full backup isn't properly listed? As to deleting restore points prior to running active full, if you're uncertain about the consequences of this action, you can simply cut and paste these restore points to different location to have an option to import them in case something goes wrong. Thanks!

[FrancWest]

Hi,

the screenshot is attached to the case. Are you able to access it from there? This afternoon I have a call with the engineer to look into it.

[foggy]

About the removing. We are going to use these backup copies as a source for storing them off-site, so we need them to be encrypted. Since these unencrypted restorepoints will also be used for GFS retention, we can't have the risk of storing them unencrypted externally. And deleting them all, prior to doing the active full is risky also, since we all know Murphy

GFS mechanism uses the current full as the basis, so nothing to worry about - old (unencrypted) restore points will not be used for creating new GFS ones.