Hi Veeam Product Team,
Case # 07761005
I'd like to suggest an improvement regarding how missing backup files during tape jobs are reported and handled.
Current Behavior
When a (large and long) quarterly tape job is executed and a backup file (e.g., a .vbk) that had been marked for copying is missing (in between deleted by retention), the software currently logs an error such as:
"Full backup: Unable to get backup with id 'xxxxxx'"
In these cases, the job itself might complete successfully apart from the missing file, but an error is still displayed. The message itself lacks actionable details and context, making troubleshooting difficult.
Why change is needed
Missing a backup file in this scenario often doesn’t indicate a critical failure – the job performs as expected for the available data.
Generic error status and message create unnecessary alert noise and do not help administrators assess the real impact.
Suggestions
Enhance the corresponding message to provide more context and actionable advice (clarify what happened and its impact).
From my perspective, this would be a nice-to-have information, since the job itself operates as designed and completes successfully.
Thank you for considering this suggestion! If more details or logs are needed to illustrate the scenario, please have a look in the closed case.
Best regards,
Ronald
Case # 07761005
I'd like to suggest an improvement regarding how missing backup files during tape jobs are reported and handled.
Current Behavior
When a (large and long) quarterly tape job is executed and a backup file (e.g., a .vbk) that had been marked for copying is missing (in between deleted by retention), the software currently logs an error such as:
"Full backup: Unable to get backup with id 'xxxxxx'"
In these cases, the job itself might complete successfully apart from the missing file, but an error is still displayed. The message itself lacks actionable details and context, making troubleshooting difficult.
Why change is needed
Missing a backup file in this scenario often doesn’t indicate a critical failure – the job performs as expected for the available data.
Generic error status and message create unnecessary alert noise and do not help administrators assess the real impact.
Suggestions
Enhance the corresponding message to provide more context and actionable advice (clarify what happened and its impact).
From my perspective, this would be a nice-to-have information, since the job itself operates as designed and completes successfully.
Thank you for considering this suggestion! If more details or logs are needed to illustrate the scenario, please have a look in the closed case.
Best regards,
Ronald
Statistics: Posted by Samba222 — Jul 28, 2025 3:19 pm
