Using Secondary Target in a job vs separate Backup Copy Job

[tgx]

Using Secondary Target in a job vs separate Backup Copy Job

I am curious when each case has a benefit over the other.
Are they not in effect achieving the same result?

I am doing a backup to DAS, then to NAS, then to Cloud.
Most of my jobs have a single backup to DAS with a separate job that handles the Backup Copy to NAS to Cloud (NAS/Cloud is my Scale Out Rep).
Recently I have experimented with including as a secondary target (same scale out repo) in the main job. Both seem to do the same thing.

Any tips on which is better if any? Just looking to make sure I'm not making some critical noobie mistake that causes me heartburn later.

Thanks!

[PetrM]

Hello,

Basically, these two methods allow us to achieve the same result. The only difference is that you can use different sources of data when you add workloads in the backup copy job wizard whereas specifying secondary target makes possible to add a backup job as a source of data to already existing backup copy at the level of the primary backup job creation wizard.

Thanks!