We won't be able to meaningfully troubleshoot such items over the forums as it will require review of the debug logs.
I cannot explain the discrepancy just with screenshots, but Support will be able to tell what the job identified as backups that needed to be moved to tape, so please proceed with Support as prescribed.
Share your case number once created, thanks!
David Domask | Product Management: Principal Analyst
Response obtain, but cant understand it.
If someone knows how to put on tape only the full backup of VMs to tape each days i thank it a lot.
I think i'm going to go back to V12 that works well, and dont renew hte licences and see what other software i can use
While I was replying to you, I figured out what was going on. Honestly, the folks at Veeam are clueless. What we want is a full backup on every tape job. The problem is that the tape job is a mess. Sure, we say we want a full backup every day, but when we have a lot of VMs to back up and the tape drive is slow, we back up the VMs late in the evening and do the tape backup overnight. But since we’re not on the same day, the tape drive says, “I have nothing for today.”
That’s where the “reverse incremental” option was brilliant.
The engineers at Veeam (if they’re really engineers) need to check whether the tape job is part of a chain of jobs and add some intelligence to it.
Another thing : Why when you create a "classic" backup job HOST is added automaticaly with VMs selected ???? and you have to remove it manually from the job ????
Just one last thing: the “reverse incremental” option is available for jobs “imported” from V12, so why not keep it available????
So, ladies and gentlemen, if you want your tape backups to go smoothly, you need to do everything on the same day.
Please ask VEEAM to update the documentation to explain this (the V13 documentation isn’t up to date because they’re still referring to reverse incremental backups, which no longer exist) and to include my comment in the V13 FAQs.
Reverse incremental is not recommended anymore for performance reasons and is considered a “legacy” backup mode. Reverse Incremental has the highest I/O demands on Repository servers; Reverse Incremental works by always having a Full backup as the most recent Restore Point which allows for fast restores; incremental backups are merged into the Full Backup file, and older data is copied from the Full Backup to a VRB file which is added to the Backup Chain for recovery from older Restore Points. Reverse Incremental will be removed in Veeam Data Platform v13 and later versions.
