Tape GFS and source full backup

[mamosorre84]

Hello,

my primary jobs are configured with incremental + weekly active full (no synthetic).

My first question is: are there any differences between active full and synth full in GFS tape job mechanism?

Second question: GFS tape job wait for a new restore point appear, ok..but do you mean that the primary full job must start on the same GFS day, finish on the same GFS day or both?

Thank you

Marco

[veremin]

My first question is: are there any differences between active full and synth full in GFS tape job mechanism?

No

Second question: GFS tape job wait for a new restore point appear, ok..but do you mean that the primary full job must start on the same GFS day, finish on the same GFS day or both?

It doesn't mean that. GFS tape job will wait 24 hours for a new restore point to appear, if this doesn't happen, it will look at previous dates for GFS candidate. Kindly, read corresponding section of our user guide.

[mamosorre84]

I've read this https://helpcenter.veeam.com/docs/backu ... tml?ver=95 but I think I didn't uderstand very well..

I switched from daily incr+ weekly synth full to daily incr+ weekly active full+used per VM two weeks ago.

All active full starts on Tuesday-Wednesday and finishes on Wednesday.

GFS tape job starts on Wednesday at 00:00

There is a tape job running now (started last wednasday), and the problem is that for some jobs it has copied the most recent full, but for other jobs it has also syntesized old full (it has created a full map backup from the last NO USED PER VM job) !

I hope I've explained well the situation..

I can send you some screenshots if you want.

Thanks

Marco

[veremin]

If all source jobs create full backups on Wednesday, GFS tape job executed on that day should have copied all full backups without exception instead of synthesizing virtual backup from previous increment.

If this did not happen, reach our support team for further investigation. Prior to doing this, upgrade to Update 1 (there have been several issues with GFS candidate selection logic in 9.5 GA).

Thanks.

[mamosorre84]

Change from synthetic full to active full+used per VM parameter may have influenced this strange behaviour?
Anyway, I wait the job end and I analyze better the situation.
Veeam is already 9.5 update 1.
Thank you
Marco

[veremin]

Change from synthetic full to active full+used per VM parameter may have influenced this strange behaviour?

Nope, full backup creation mode should not affect GFS backup to tape job.

[mamosorre84]

I've opened a support case #02124062

[mamosorre84]

Solved, the problem was the primary jobs's linking date.
I've re-linked primary jobs and all worked fine.
Thank you
Marco