Last week I had to troubleshoot a tape (GFS) backup problem. I guess the solution could be interesting for others too.
I this environment, synthetic full and tape backup are scheduled at the same day. Full prior to tape jobs. Normally we do see any problems with this configuration. But last week we saw this error in the tape job:
12.01.2022 07:04:45 :: Error: Storage ('c97b8ddb-a9dc-4b49-b441-dc1031100a58', CreationTime '08.01.2022 23:15:25') not found
As a result the whole job failed.
After taking a look at the logs, I found out, the related storage object was a VIB-file of one of the backup jobs, tape job had to bring to tape.
[08.01.2022 23:45:07] <01> Info [CTapeVmTaskBuilder] Storage c97b8ddb-a9dc-4b49-b441-dc1031100a58, mediaset: Weekly, path: servername.vm-187205D2022-01-08T231525_8F3A.vib, creation time: 08.01.2022 23:15:25, is synthetic: True, is synthetic full: True
Although the disk backup job was running at the time, the file was not there at all. Why? The reason was quite simple: At this day a synthetic full was scheduled. So VBR creates a VIB-file that is replaced by a VBK-file at the time of merging. Therefore the error in the tape job: Tape job starts and searches for backup files to bring to tape. Here the restore point of the VIB-file was selected. But the backup job has not performed the merge by this time. Later, when tape job wanted to access the VIB-file, it was replaced by the VBK-file - because of merging for synthetic full. In our case, disk backup job needed a re-try and therefore the merge-process was much later than normally.
When you suffer from this error more often, you could try to create some time buffer between full and tape job. Another solution could be to configure tape job to use already existing restore points instead of waiting for new respectively currently running ones.
The only thing I cannot answer is: why does the whole job fails when just one file of one backup job was missing?