Moebius wrote:I guess I'm missing something on how the GFS tape jobs work.
Well, after wasting some time with support tier 1, I asked to escalate my case and tier 2 quickly found some reasons why some of my source jobs were skipped.
What support told me is very interesting, and I believe this has not been mentioned in the user guides or documented anywhere. So here it is.
Veeam support wrote:There are a few things of note:
- Veeam will only search from the restore points that were created after you've linked (added) the source jobs to the GFS tape job. So yes you have to run them at least once again after adding -- this may be a bit confusing.
- If you disable a GFS Tape and then enable it, we'll only look for restore points that were created after you've enabled the job. Here we assume that you wanted to skip a period and don't want any backups from the period that the job was disabled.
- Otherwise the latest restore point is taken and copied/synthesized to tape, if it wasn't already copied before.
This kinda explains why my original strategy won't work. I thought I could send a full copy of all my source jobs to tape with a weekly GFS - even those source jobs that are scheduled to run once a month or on demand. The last sentence says they will be copied only once after their last run, and will be skipped in the following tape backup sessions.
As I told support, I fail to understand the logic behind this "limitation", but I will have to rethink my strategy. I might have to enable the monthly GFS and schedule regular backups even for the jobs that run only on demand at the moment (eg. VMware templates).