Failed to create backup file because it is already present

[pmillard5000]

Hi there,

I have this new backup job that is failing with the following error:-

Code: Select all

Processing COM2.***.*** Error: Failed to create backup file because it is already present on the file system. Agent link: G:\Backups\Backup Job Infrastructure EW - COM2\COM2.***.***.vm-423805D2018-03-13T125127.vbk

I have checked the location it is pointing to on the backup rep and there is nothing there.

I have rescanned repositories, even recreated a brand new backup job to back this VM up but no joy, keeps failing with the same message.

There seems to be absolutely nothing on this error online.

Contacted support, case # 02673622.

Has anyone got any ideas?

Many thanks,

Peter

[csydas]

Hey Peter,

I had this once, and I think we ended up just remapping the job to the backups. I guess see what support says, but if push comes to shove, just recreate and point it at the existing backups and see what happens.

[pmillard5000]

Cheers for that.

Its a new backup job after migration to 9.5 so no backups to map to.

Recreated job and still the same issue.

Support have taken a copy of the Veeam DB and are looking to see if they can see the issue in there.

[jroberts]

Did anyone ever find a solution? We got our first backupcopy job to go but all subsequent copy jobs have failed with the same error. Even deleting all files on the target do not yield any change.

[sg_sc]

The same error after deleting copy jobs, and recreating them.

[Mike Resseler]

Hi SG-SC and jroberts,

The OP had an issue with the name of his VM. Because of that name, the backup file couldn't be saved since the windows OS didn't allow that specific name to be stored.
There might be obviously a different reason in your case.

I would suggest to both creating a support call (post the CASE ID here and the follow-up after investigation with our engineers)
Thanks
Mike