Now let’s get back to your issues and questions:
Dave338 wrote: The option to backup only latest chain that appears if you have more than one full on the target seems the salvation, but I'm testing and seems only working on the first run of the job...
It is true, however, we recognize this functionality to be highly requested – so it’s now in the top priority list.
Dave338 wrote: Problem occurs basically when using Forever Forward. One your retention period is reached, the full vbk file gets modified every day… But the initial problem is solved? Or I will continue getting 2 fulls on tape every week because my "old" vbk is modified
It should be solved in the Update2. If you see any duplicated .vbk it should be counted as bug and reported to support team
newfirewallman wrote:this is intended behavior. The tape job will always fail if the backup job kicks off…
Have to admit it’s totally looks like a bug. I’ve already forwarded all your findings to QA team for investigation. Will follow up on this one once I hear anything.
newfirewallman wrote:Hmm, I'm wondering if the choose latest is selectable via the powershell snapin?
Not possible. Only via hard links workaround provided in this thread
Dave338 wrote:my monthly backup will be syntethised 10 days later than I want, after the retention date has been expired
It will check the synthesized full backup schedule every backup to tape job run, so if the restore point still persists on repository and was not previously written by this tape job – then yes, but, please, keep in mind the general recommendation to have the tape job’s retention longer than the disk job.