So I spent a lot of time and did multiple Veeam database edits with DBeaver in order to get this working again. IMHO the whole implemented rotated drive logic is a serious problem - Veeam relies on a specific drive letter first, but then, if the drive letter changes (which can obviously happen anytime on Windows), at some point everything gets out of control and we get different paths in the database that don't match anymore, the "new" wrong drive letter even gets hardcoded into the repo settings. The "Unable to substract path ... Roots are different" starts to pop up not only in the job logs but also in error dialog boxes everywhere in the interface and there is nothing the user can do. This problem then prevents us from stopping the job, deleting the job, even deleting orphaned backups and also from deleting the "bad" repository. After a lot of trial and error I could disable the job through a database edit (see post I linked to above), so at least it did not block other jobs anymore. But this did not solve the problem at all, as I could still not remove the job or the repository - the "Unable to substract path ... Roots are different" chicken-egg problem I described above still occurred everywhere.
Finally, after more trial and error, I ended up doing a full text database search (thanks to DBeaver) for the incorrect path F:\Backups. Only a replace with the original O:\Backups path in each and every place in the DB made things consistent again so I could finally remove the problematic job and repository.
Not sure what is wrong with 12.1 update, but it also had damaged some of my Veeam Agent Free job entries in the database, I also had to manually fix this according to KB4421.
None of these problems could be solved without being able to edit the database, which a user should normally never touch. Also not sure if I should describe my solution to support, as they did not even understand my problem, so I post it here, maybe it will help someone.
Finally, after more trial and error, I ended up doing a full text database search (thanks to DBeaver) for the incorrect path F:\Backups. Only a replace with the original O:\Backups path in each and every place in the DB made things consistent again so I could finally remove the problematic job and repository.
Not sure what is wrong with 12.1 update, but it also had damaged some of my Veeam Agent Free job entries in the database, I also had to manually fix this according to KB4421.
None of these problems could be solved without being able to edit the database, which a user should normally never touch. Also not sure if I should describe my solution to support, as they did not even understand my problem, so I post it here, maybe it will help someone.
Statistics: Posted by Anguel — Feb 24, 2024 4:47 pm
