[v10] Map Backup copy job files with GFS to Backup job

[P0ll@rd]

Hello!
I am working with Backup Copy Job to achieve GFS retention. So my monthly backups are labeled with tags. My backup jobs and backup copy jobs files are hosted by the same server on 2 different repositories. In v10, there is GFS backups directly in Backup Job so I was thinking to stop my Backup Copy Job and use GFS on my Backup Job instead. GFS Backup job also use tags on backups to set up retention like in Backup Copy Jobs. Do you know if my GFS retention will be kept if I map my Backup Copy job files in my Backup Job ?

[HannesK]

Hello,
The GFS creation on backup copy jobs and backup jobs work different. So you cannot map them. I do not understand what you mean with "tags" when it comes to GFS, but I feel it's not relevant to me.

Best regards,
Hannes

PS: as I saw more than one customer loosing the backup server with all backup data... I recommend to implement the 3-2-1 rule

[P0ll@rd]

OK I understand that Backup Copy Jobs and Backup Jobs work different so I cannot map one to another. I saw that the proces to create GFS files are different.
For the "tags" I mean that the backup files are labelled with W,M,Q ou Y to apply retention and it is the same parameters for both kind of jobs:


That's why I thought it was possible to switch bteween these two kinds of jobs.

PS: There is tape export to prevent data loss if Veeam server crashes

[veremin]

Those "tags" just illustrate the GFS retention cycle applied to the restore points. As Hannes mentioned, it does not mean that you can map backup job to backup copy job. Thanks!

[PetrM]

Hello Benjamin,

Just one more comment:

In v10, there is GFS backups directly in Backup Job so I was thinking to stop my Backup Copy Job and use GFS on my Backup Job instead.

I don't think that the comparison of backup job GFS and backup copy job is correct because you achieve different goals using these features:
The GFS (regardless of job type) makes possible to retain data for longer period of time and backup copy job allows you to follow 3-2-1 rule as Hannes mentioned.

Thanks!

[frankive]

with SOBR, is there any reason at all to use backup copy job?
Can we configure the retention on the backup job itself, and backups will go to the performance extent first. Then based on policy the data going pass the GFS will be offloaded to the archive tier (f.ex amazon). This will allow you to follow 3-2-1 rule?
If so, is there possible to map ut the exising GFS jobs in a backup copy job to the backup job as Benjnamin wants?

[HannesK]

with SOBR, is there any reason at all to use backup copy job?

sure. every customer who does not want / cannot send data to object storage needs the backup copy job.

Then based on policy the data going pass the GFS will be offloaded to the archive tier

capacity tier first. archive tier is a V11 feature (this thread started for V10)

This will allow you to follow 3-2-1 rule?

in copy mode: yes. with move: no.

If so, is there possible to map ut the exising GFS jobs in a backup copy job to the backup job as Benjnamin wants?

sorry, I do not understand the question. That thread is almost a year old and your questions look unrelated to the topic

[frankive]

OK, i'll try to reprashe:

If we want to have GFS-retention (which we always has and always will) we have always used the Backup Copy Job to a SOBR with a local performance extent and a Object Storage for Archive.

What you are saying now is that we don't really need to use the Backup Copy Jon feature anymore if we want to get the data to Object Storage.We can just use the Backup job itself since it now has GFS built-in.

Is this assumption correct?

[frankive]

I can see there is customers with the same quiestions here:
https://www.reddit.com/r/Veeam/comments ... n_new_gfs/

The answer seems to be in this scenario we don't need the backup copy job anymore.

Nice!

[veremin]

Is this assumption correct?

Correct, you can achieve your goal without backup copy job. Thanks!

[foggy]

Where will you have the third copy of your data in this case?

Anyway, answering your original question, currently you cannot map a primary backup job to backup files produced by a backup copy job.

[frankive]

regarding the 3-2-1:
the copes will be: 1. The production hyper-v VMS 2. the local extent (production window) 3. object storage (copy mode)
https://www.veeam.com/blog/how-to-follo ... ation.html

[Simon_LBC]

I'll try to be the more clear as possible!

I have a huge (20 TB) backup job to a first repository (on-site) with a backup-copy job to a second repository (off-site).

I am currently deleting my on-site repository because it's not required anymore and I want my modify my Backup Job to now use the second repository (off-site) only.

Is there a way to "re-map" or "reuse" the data from the Backup-Copy Job that is already on my repository for my main backup job? Because I really want to avoid re-seeding the 20 TB full backup... that would be a nightmare honestly because it usually took like 5 days.

Thank you!!

[HannesK]

Hello Simon,
backup copy jobs cannot be converted / mapped to backup jobs. It's something we have in our mind, but no time estimation is possible.

Best regards,
Hannes