Backup Copy of existing job

[CBinSyd]

I'm considering relocating my primary backup target from Azure to Wasabi and then having a secondary copy in AWS. My initial plan was to create a copy job to Wasabi, once fully synced make this the Primary target and then create new copy job to target AWS . I would then be able to delete the data in Azure.

I now know there's a few things wrong with this plan and am looking to get some clarity around some of the things I have learnt.

e.g. If you start a copy job on an existing backup it only backs up from the latest restore point and does not sync the historical restore points. What does this actually mean ? For the copy to be any use then you need a full copy of the data for the restore points to reference. So does the copy job do a one time full backup to the new storage - and then start creating restore points. If so, is this a full backup from M365 direct - or is it essentially a restore from the existing backup data ? Or does it only create new restore points on the secondary storage i.e. changed data. This means the copy is actually only useful for newly created data ? In this case I would need to start the backup job from new in order to get 2 viable full backups.

The other thing is around the format of the backup copy - which I understand cannot then be used as a source for another copy job . Has anyone got any details around this and what the limitations are of this copy ?

Thanks .

[Mildur]

Hello Chris

Backup Copy: Copies the latest Restore Point from your primary backup repository to the backup copy repository.

A backup copy job does never "take direct backups" from your M365 tenant.
The name itself is self-explaining. It copies backups, but it does not create backup data.
And it cannot be used to as an alternative to "migrate" your backup repository from one repository to another repository.
We are currently working on options to migrate backup data between different object storage repositories. Unfortunately there is no ETA we can share today.

The other thing is around the format of the backup copy - which I understand cannot then be used as a source for another copy job.
Has anyone got any details around this and what the limitations are of this copy ?

Backup Copy Jobs can only create backup copies from primary backup jobs. No workaround available.

Best,
Fabian

[CBinSyd]

Thanks for the response.

Just to clarify - when I initiate a backup copy all the data required for a full restore, from the latest restore point, is transferred from the primary backup location to the new target location ?

Also - if the primary backup data gets destroyed, you can still use the copy data to restore from, but to continue backing up the tenant you would need to start a completely new job ?

[Mildur]

Hi Chris

1) Correct. First copy session will do a full copy of the most recent restore point. It can be used to fully restore the entire Restore Point. Subsequent copy session only incremental copies of a new restore points.

2) Correct. In that case the primary backup job has to create a new full backup. But full restore back to production will be possible from the backup copy.

Please check this help center pages for more information: What You Do with Backup Copies & Exploring Backup Copies

Best,
Fabian

[CBinSyd]

Thank you. That's very helpful.