Skip to main content

How to fix upgrade Veeam backup & Replication failed --Error 1327.Invalid Drive


CarySun
Forum|alt.badge.img+7

If it happened Error 1327.Invalid Drive when you try to upgrade the Veeam server, don’t panic. This is likely caused by a stale registry entry for the Veeam server. In my case, the Veeam server had an F drive but removed it a long time ago. My error message is Error 1327.Invalid Drive F: and the upgrade failed.

1.login to the Veeam management server.

2.Run regedit.

3.check the following registry path on the Veeam server. HKEY_LOCAL_MACHINE\Software\Veeam\Veeam Backup Catalog\ and HKEY_LOCAL_MACHINE\Software\Wor6432Node\Veeam, do either of these paths show the F drive? Likely it will be the VBR catalog folder in my case.

4.Right-click CatalogPath, select Modify.

5.Change the Value data from F:\VBRCatalog to C:\VBRCatalog, click OK.

6.Re-run upgrade again. The error message should be gone.

6 comments

coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • 4890 comments
  • October 11, 2023

Thanks for sharing @CarySun 


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 9535 comments
  • October 11, 2023

I love these little workarounds to fix things.  Great share Cary. πŸ‘πŸ»


marco_s
Forum|alt.badge.img+8
  • On the path to Greatness
  • 402 comments
  • October 12, 2023

Guest OS indexing is your favourite feature @CarySun πŸ˜


CarySun
Forum|alt.badge.img+7
  • Author
  • Veeam Vanguard
  • 206 comments
  • October 12, 2023

@marco_s Guest OS indexing will avoid this issue? How?


marco_s
Forum|alt.badge.img+8
  • On the path to Greatness
  • 402 comments
  • October 12, 2023

no, I meant that since guest os indexing uses catalog disk and yours was missing for a long time, maybe it's a feature you're not using and didn't notice before!


CarySun
Forum|alt.badge.img+7
  • Author
  • Veeam Vanguard
  • 206 comments
  • October 12, 2023

@marco_s gotcha!


Comment