Failed to detect backup files to copy to tape

[Guido]

I created a new tape backup job to have the option to select only the latest chain.
Now the job fails with the message: Failed to detect backup files to copy to tape.
We use Incremental backups daily, active full monthly.

[veremin]

Kindly, open a ticket with our support team, as it's pretty hard to understand the root cause of that behaviour without seeing log and actual infrastructure. Thanks.

[Samirang]

Hi,

Same problem

When, i choose all full backup chain to tape it's working
When i choose last backup chain to tape:
" failed to detect backup files to copy to tape from Backup Job"
When i look logs for this job, i have "invalid date format"

Case # 00739268

[Dima P.]

Steffen,
Awesome, thank you for sharing!

[it.loepa]

Will there be a correction in patch for this?

[Dima P.]

Hi it.loepa,
Will check it with QA and update this thread. Meanwhile, could you, please, describe why changing the time format is not possible for you? Thanks in advance.

[it.loepa]

Hello d.popov,


It's not that it's not possbile, but changing regional settings for a user is somewhat less then perfect.
In the Job Actions Logs all formats are then also English (US), if you have to do some scripts with that user.. same problem.
The solution is good for temporary.. but not a solution forever.

Regards
Chris

[Dima P.]

Understood. Thanks Chris, I'll update this thread if I hear any update from QA.

[RH2203]

This problem was exactly like my issue. Resolved by changing the date to English (US) .
Whilst changing that isn't a problem like it.loepa It's a work around, would like to get a fix for that so that it can be used in English UK without a problem.

Regards

[DavidS]

Thank you Steffen, that was also the solution for me, this problem bugged me a couple of hours...

But that can't be the final solution, merely a workaround. I hope veeam will fix this issue

[SyNtAxx]

This doesn't resolve the issue for me. This is beyond ridiculous. I'm running out of room to write down all my Veeam Support Case numbers.

[SyNtAxx]

Case # 00875532

[trustblomme]

Hi,

on Friday I have updated my system to the latest pacth 8.0.0.2030 and since then I receive the following error in my tape jobs:

Failed to detect backup files to copy to tape from X Backup job.
Job had failed unexpectedly.

Job X has finished normally.

Any tips or ideas? I have already opened a case for this problem.

Case: [ID# 00966462]

Thanks in advance,

Steven

[Shestakov]

Hi Steven, please try the workaround described above:

1. check which user starts the service "Veeam Backup Service"
2. login to the backup Server with this user (step 1)
3. change time Format to "English (United States)" and "short date: MM/DD/YYYY"
4. if the Service "Veeam Backup Service" starts with "Local System", please Change this settings as explained in the guide

Thanks!

[trustblomme]

Hi Nikita,

I did try this implementation but without any succes. I received an patch from veeam support buth without any update.
I post the provided solution.

Steven

[Dima P.]

Steven,
So modification of the time zone did not help - that’s odd. Can you please clarify you confirm the described error with the tape jobs created before the update or newly created tape jobs are affected as well? Thanks

[trustblomme]

Hi Dimitry,

I still have try to test the setup where I change the time zone and apply the patch. I have only experienced the error on my existing jobs and after installing the latest patch.

Thanks,

Steven

[Dima P.]

Thanks for clarification Steven! Let us know how it goes.

[trustblomme]

Hi Dimitry,

Time zone + patch is als not working for me. Patch provided to me genarates error when saving tape jobs. I have recontacted support to look into this.

Steven

[trustblomme]

Hi,

The patch provided to me was for a previous version of Veeam. Support recommends to recreate my tape jobs but that is no solution for me, I want to know the reason of this erro

Situation:

- Tape jobs are working fine
- Apply latest patch
- Tape jobs are not working anymore for certain backup jobs.

Already tested:

- Change of regional settings (would be a bug that veeams has to fix as quick as possible)
- Patch installation for wrong Veeam version -> no solution there

I will keep everybody posted.

Steven

[veremin]

Hi, Steven,

If you're not satisfied with the solution provided, you can always ask to escalate your case to the support management. All you need to do is to click "Talk to a Manager" button on the customer support portal.

Thanks.

[namiko78]

Any update on this? I'm getting the same problem, and the fix hasn't worked. Does it require a reboot? Do you have to do this on the repository servers also? Does the fact that i'm using a backup copy repo affect this? I've not had this problem on the main backup storage.

[Dima P.]

Hey namiko78,

Can you please open a support case? The issue is still under investigation, so any fresh troubleshooting info can help us in getting this resolved. Thanks in advance.

[Andreas Neufert]

In my situation I used an external Tape Server and Repository that are not on the Veeam Server.
I used a separate user for this server (to add the server to managed server objects). Adding this "User and Roles" as Backup Admin solved the problem.

[trustblomme]

Hi,

any update on this problem.

I'm still getting the error every few weeks. If you remove the source backup job, start a full backup of that job and re-add the job to the tape job (last chain only) the error will be gone.

The create tape synthetic full tape is causing this error it seems.

Steven

[Dima P.]

Steven,

Can’t find any details in the thread on your tape backup schedule and synthesized full backup schedule – can you elaborate, please? Also do you backup incrementals to tape?