Today when we try to update one of our Veeam v8 to v9, we get this issue, and the upgrade failed.
Checking the logs(C:\ProgramData\Veeam\Setup\Temp\CatalogSetup.log) from the upgrade I see that this is related to VBRCatalog that is/was pointing to this drive that no longer exists.
“MSI (s) (2C:9C)[22:04:17:969]: Note: 1: 2318 2:
MSI (s) (2C:9C) [22:04:17:969]: Executing op: FolderRemove(Folder=D:\VBRCatalog,Foreign=0)
MSI (s) (2C:9C) [22:04:17:969]: Note: 1: 1327 2: D:\
Warning 1327.Invalid Drive: D:\”
So we need to fix the catalog issue, before restarting the upgrade.
To fix this issue, we need to change the registry where the VBRCatalog is set. To do this, we do the following tasks:
1. Stop the Veeam Services
2. Check the permissions that are set on the folder
3. Unshare the folder and move it to a new location
4. Now share the folder and reset the permissions
5. Then navigate to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup Catalog
Find the string called CatalogPath, right-click it and choose modify
Under Value Data, edit the field to display the new location
Example: c:\VBRCatalog\ (be aware that you should select Disks with space to allocate and grow of the VBRCatalog). In our case, I create a new folder in the drive F:\VBRCatalog and then changed the registry with the path F:\VBRCatalog.
6. Restart the services mentioned above(should be Veeam Backup Service, but also Veeam Backup Catalog Data Service. Service is not in the start state because of this issue)
You can check here the Veeam KB1453 how to change the VBRCatolog.
Next, try the upgrade again, and it should pass this issue.
Note: Share this article, if you think is worth sharing.