Will "Copy all backups..." chains still need seal?

[s.eng]

Hi,

With the new feature "Copy all backups to object storage as they are created", will the chain still need to be sealed? Or could I run Forever Incr with this one?

Thanks

[HannesK]

Hello,
no and yes

Best regards,
Hannes

[Gostev]

Right. Since the whole idea of Copy mode is the immediate copy, it would be unreasonable to require backups to be sealed as this would mean not a single increment could have be copied by definition.

Move mode on the other hand was specifically designed to offload older backups such as GFS restore points, so there this requirement makes sense. And it simplifies things dramatically (as all offloaded backup files are guaranteed not to change on-prem, where they are now represented as stubs).

[crackocain]

Hi

I want to ask use both copy and move mode scenario.
Cloud Connect Scale out Repository Capacity tier settings
Move backups 0 days
Copy backup checked
All jobs is Backup copy jobs

In this scenario all backups move and offloaded object storage right? Local disks are all empty?

[Gostev]

No, local disks will not be empty, as move only works for sealed backups. Thus, the current incremental chain will never be offloaded. However, having the last few restore points on-premises is what you really want anyway for fast and FREE restores (otherwise, you will be paying egress and API charges for every restore).

Besides, even when restoring from older restore points which are already offloaded to object storage, Veeam uses on-prem backups as the source of matching data blocks, which also helps to reduce restore costs dramatically - as only delta with the closest on-premises restore point needs to be retrieved from the cloud (so usually just a few percent of the restore data size).