In some cases, backup repositories automatically created by setup during upgraded from v5 may start writing data into C:\Windows\SysWOW64 if backup files used to reside in the root folder of the volume.
Root cause is still unknown but this KB will assist you in getting your jobs writing to the correct repository. A patch will be released at a later date.
1) The repository for the backup job(s) will need to be deleted however you cannot delete the repository with jobs linked to it so what you can do is create another repository pointing to the same location.
2) Move the Veeam files (VBK, VRB, VIB, VBM) from the SysWow64 folder back into their original locations with the rest of the backup files for your jobs.
3) As long as you have a VBM file for each set of backups you can then simply go into Backup Repositories (under Backup Infrastructure) and re-scan the repositorie(s) that you just created. Veeam should then see that the backup files reside in that directory.
4) Go into your Backup jobs and point back to the newly created repository and click the Map Backups link. Your jobs should pick up where they left off and you shouldn't have this issue again.
5) Delete the original repository which should now have no jobs linked to it.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.