I thought it was generating a synthetic full and only that, but it's putting that plus the month old VBK (beginning of my chain) on tape.
But without virtual full backup how would you deal with .vbk that gets updated constantly (when retention is reached), as well as, corresponding increments (one of which is deleted and one has its references to previous restore point changed)?
v.Eremin wrote:The files to tape job seems to be the preferable option here, indeed. You said that the source backup job cycle killed the secondary job, but it would have killed even a backups to tape job if you had had one with virtual full backup disabled.
So, it appears to be the matter of tuning the schedule of source job, so that, the primary job doesn't interrupt the secondary one. That might be done either by playing with schedule or using pre-job activity which purpose would be let a source job wait till the files to tape job is finished.
Else you will always end up with two VBKs on tape as soon as the retention expires on disk
Users browsing this forum: No registered users and 1 guest