Off-site backup Copy Job or "normal" Job?

[expert]

Hello,

we have 2 Windows 2019 Repositorys:
- Repository 1 -> Datacenter
<1 Gbit link>
- Repository 2 -> Headquarter

Backup Plan:
- Datacenter: Backup-to-disk repository 1 with xx retentions
<copy job or other job to headquarter over night>
- Headquarter: Backup-to-disk repository 2 (latest retention is sufficient)
- Headquarter: Backup-to-tape

At the moment I configured a copy-job for the main backup jobs and then backup to tape.
Since copy-jobs doesnt support reverse incremental, active full backup etc. I'm not sure if it is better to make identically jobs (clone) for repository 2 to maintain the data integrity from off-site backup (backup-to-disk-to-tape)

Otherwise, a periodically active full backup to the off-site repository 2 could be a problem (1Gbit link).

Any suggestions would be greatly appreciated,

best regards,

Juergen

[PetrM]

Hello,

The scenario described above seems to be correct as you follow 3-2-1 rule and backup copy job is designed especially for this purpose.

One more argument in favor of using backup copy in your case is that it uses forever incremental chain by default and periodic active full is no longer required.

Thanks!

[expert]

Hello Petr,

thanks for the information. But what about data integrity of the copy job data (if active full will never be made)?

regards,

[Vitaliy S.]

For the data integrity, you can use SureBackup jobs with primary jobs (to validate the backup). Please note that backup copy jobs have built-in integrity check that ensures the copy is bit-identical, so there is no need to perform full recovery verification of copied backups again.