Dima P. wrote: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.
What makes you think this looks like a bug?
v.Eremin wrote:The tape job should be stopped as it has less priority in comparison with backup job (secondary vs primary destination). Thanks.
Blake (newfirewallman) isn't talking about tape synthetics. If a backup to disk job kicks off while a regular backup to tape job is running (not a synthetic), the tape job will stop. From my understanding, if the files we are reading are required to be locked for the tape job, the tape job will be stopped, because it has less priority than the backup to disk job.