Agent-based backups for Windows and Linux, centralized agent management
Post Reply
tgx
Novice
Posts: 3
Liked: 1 time
Joined: Feb 11, 2019 6:17 pm
Contact:

Using Secondary Target in a job vs separate Backup Copy Job

Post by 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
Veeam Software
Posts: 917
Liked: 128 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic
Contact:

Re: Using Secondary Target in a job vs separate Backup Copy Job

Post by 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!

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest