You can check the Advanced settings and turn on the processing of the latest backup as noted here - https://helpcenter.veeam.com/docs/backup/vsphere/advanced_advanced.html?ver=120
Also check this documentation it is good.
Hi @Chris.Childerhose . Thanks for sending that. I already have that box checked, but the weekly job still isn’t copying to tape. It only makes sense that it should copy, but I’m stumped why it isn’t.
Are you using a standard or GFS media pool. Is the job GFS to tape? Not sure and might require a support ticket.
Hi stryker54141,
from my point of it doesn’t make sense to have 3 jobs of the same target and copy all backup to the tapes as full backups.
From my point of view is easier to set one job with synthetic backup for each day and into scheduler set periodically backup with backup window 20:00-08:00, where frequency is 8 hours, so evening and morning you will have backup. And in GFS set for weekly backup (so i will remove synthetic backup for that day).
I know that some backup software does not support GFS, so solution was with multiple jobs, but by Veeam is easy to have one.
If you use 3 jobs for one VM, then CBT is not helpful, then you can run active full backup every day.
Because i f one job will do backup, and then second, then this second job will reset CBT anyhow.
@stryker54141,
Just to confirm, when you tell you have synthetic fulls every nice, you’re talking about in the SOURCE jobs? (the weekly)
Or you scheduled the Virtual Full schedule in the tape job as shown on that user guide page? Virtual Full only works if your source chain is Forever Forward Incremental, and I’m guessing your weekly job runs fulls?
REgardless, the way the tape logic works is:
1.
- Check what jobs are added to the tape job
- List the backups on repository
- LIst the backups on tape
- Compare the two lists, whatever is on repo but NOT on tape, queue for backup to tape
- COnfirm the backup should be moved to tape, and then do so
If a backup on repo already exists on tape for that tape job, the job will not back it up again.
So as I understand you, you want that the weekly backup is backed up each night regardless of whether it was backed up previously, am I correct?
Hi All. Thanks for all of the great responses.
@Marcel.K - I should have mentioned that each of my three jobs are backing up different sets of VMs. For VMs that rarely change, I am backing them up only once a week.
@ddomask - I have virtual fulls scheduled on the tape job so that my tape always contains a full backup. (I think I’m understanding the use of “virtual fulls” correctly?) And yes, I want that job backed up each night regardless of whether or not it was backed up previously. That way I can hold one tape in my hand that has all of my backups.
Got it, so any given tape should have the most recent backup chain from each of your three jobs, correct?
For the twice-daily and weekday jobs, not difficult at all.
The weekly one will be a bit challenging to force copy-to tape each day, and regrettably will require multiple tape jobs backing up the same job. This is not really a problem for VBR, it’s just inconvenient to have that many jobs 
Each of the jobs can point to the same media pool, no issue.
But for the immediate future to accomplish backup the most recent backup no matter what, multiple tape jobs will be required for the weekly one.
@ddomask - Thanks for all of your help with this! I might just dump the weekly backup job and lump those VMs into the daily one. Since they don’t change a lot, it shouldn’t add too much to my repos.
