-
- Enthusiast
- Posts: 51
- Liked: 61 times
- Joined: Feb 11, 2019 6:17 pm
- Contact:
Using Secondary Target in a job vs separate Backup Copy Job
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!
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!
-
- Veeam Software
- Posts: 3626
- Liked: 608 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
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!
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!
-
- Novice
- Posts: 7
- Liked: never
- Joined: Jul 30, 2020 2:12 pm
- Contact:
[MERGED] Backup copy job vs secondary target?
Hi,
We're setting up secondary targets for a backup job. Obviously, in order to do this one must first create a backup copy job. I'm confused as to how these work together. In the backup copy job I need to define an object to copy, and in the backup job I need to define the backup copy job to run. This seems redundant to me. Why do I need to set up this two way relationship? Am I misunderstanding something?
We're setting up secondary targets for a backup job. Obviously, in order to do this one must first create a backup copy job. I'm confused as to how these work together. In the backup copy job I need to define an object to copy, and in the backup job I need to define the backup copy job to run. This seems redundant to me. Why do I need to set up this two way relationship? Am I misunderstanding something?
-
- Veteran
- Posts: 1143
- Liked: 302 times
- Joined: Apr 27, 2020 12:46 pm
- Full Name: Natalia Lupacheva
- Contact:
Re: Using Secondary Target in a job vs separate Backup Copy Job
Hello,
moved your post to the existing thread. Please take a look at Petr's answer, I believe it helps.
You can use separate backup copy jobs if that's what you need for your environment.
Thanks!
moved your post to the existing thread. Please take a look at Petr's answer, I believe it helps.
You can use separate backup copy jobs if that's what you need for your environment.
Thanks!
-
- Novice
- Posts: 7
- Liked: never
- Joined: Jul 30, 2020 2:12 pm
- Contact:
Re: Using Secondary Target in a job vs separate Backup Copy Job
Hm, well, I still don't fully understand how it works. But if my backup jobs only process a single machine, it should be enough to just create the backup copy job, without also adding the copy job as a secondary target for the backup job?
-
- Veeam Software
- Posts: 3626
- Liked: 608 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
Yes, it's enough, those are just two different methods to add a source into backup copy job.
Thanks!
Thanks!
Who is online
Users browsing this forum: No registered users and 3 guests