We encountered problems with Copy to Tape Jobs including VM Backup Jobs and Endpoint Backup Jobs. The Copy to Tape Job stated each session inside the Copy to Tape Job with "Success", but in fact there was nothing of the Endpoint Backups copied to tape. I realized, that this could not be correct, since I expected to have more tapes to be used and taken offside for this Copy to Tape Job. Further analyses showed, that there was nothing of the Endpoint Backups copied to tape, with the following entry in the Session Log of the physical host: Source backup files detected. VBK: 0, VBK map: 0, VIB: 0
. Veeam support could'nt tell me why there was never created a Systhetic Full and there was never copied anything of those Endpoint Backups to tape. In my opinion, in this situation, with no copy on tape, there should be a "Warning"
state instead of "Success".
The only thing, which got my copy job to work was, to include also the Incremental Backups inside the Copy to Tape Job. This is not what we want, since we have many VM Backup Jobs (with Reverse Incremental Backups) included in the same Copy to Tape Job and want this Copy to Tape Job only to include the last Full Backups. After this first real succesfull Copy to Tape Job, I do not have to include the Incremental Backups anymore and the Copy to Tape Job still includes the Endpoint Backups.
An important side note: This article is very important to understand the Virtual Full Intervalls:https://helpcenter.veeam.com/backup/vsphere/virtual_full_intervals.html
The imotant part inside this article is, that there should at least be a source side Endpoint Backup before the next Copy to Tape job starts AND it has to be created not on the same day as the last Copy to Tape Job was running (after midnight, after the last Copy to Tape Job was running).
Nevertheless, I would like to have a "Warning"
if there was nothing copied to tape, which will trigger further analysies.