Error upgrading from 9.5 to 10.0

[CelticDubstep]

Case ID: 04014473

I attempted to upgrade from 9.5 to 10.0 but the installation failed (error below) and now 9.5 has quit working. The Z drive was a iSCSI Data Store, but it was changed to an SMB share instead and the iSCSI Target was removed. I changed the SMB share to be primary and then removed the iSCSI Target in 9.5, so the only backup location was the SMB share, so I don't understand why I'm getting this error. Any suggestions?

Code: Select all

MSI (s) (1C:30) [10:47:47:619]: Note: 1: 1327 2: Z:\
Error 1327.Invalid Drive: Z:\
MSI (s) (1C:30) [10:48:11:556]: Product: Veeam Backup & Replication Server -- Error 1327.Invalid Drive: Z:\

MSI (s) (1C:30) [10:47:40:838]: PROPERTY CHANGE: Adding OLD_NFSDATASTORE property. Its value is 'Z:\ProgramData\Veeam\Backup\NfsDatastore'.
MSI (s) (1C:30) [10:47:40:838]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727 3: 2
MSI (s) (1C:30) [10:47:40:853]: PROPERTY CHANGE: Adding OLD_INSTALLDIR property. Its value is 'C:\Program Files\Veeam\Backup and Replication\Backup\'.
MSI (s) (1C:30) [10:47:40:853]: PROPERTY CHANGE: Adding OLD_PF_AD_NFSDATASTORE property. Its value is 'Z:\ProgramData\Veeam\Backup\NfsDatastore'.


***Veeam*** NFSRootFolder='Z:\ProgramData\Veeam\Backup\NfsDatastore'.
***Veeam*** Expanded NFSRootFolder='Z:\ProgramData\Veeam\Backup\NfsDatastore'.

MSI (s) (1C:30) [10:47:47:462]: PROPERTY CHANGE: Adding PF_AD_NFSDATASTORE property. Its value is 'Z:\ProgramData\Veeam\Backup\NfsDatastore'.
Action ended 10:47:47: SetNfsRootFolderOld. Return value 1.

[soncscy]

Heya Dubstep,

I think it's because you still have a path for the vPowerNFS pointing to the former drive.

https://helpcenter.veeam.com/docs/backu ... ml?ver=100

So I think that's what's throwing the issue here. I think this is set in the repository settings for the NFS location, and Veeam still expects that location to be there.

[CelticDubstep]

Thanks for your reply. There is nothing under "Backup Repositories" other than the CIFS share, so I'm not understanding where this error is coming from. I checked external as well, nothing there.

[CelticDubstep]

Actually, I think I might have just found it, but I can't verify as there are backups running. I'll post back later with an update. I ran into another issue today but unreleated to this topic... ran out of space on the backup server in our remote office, so ordered some hard drives today to increase it from 4 TB to 12 TB. Our main office has 24 TB, but the remote office has a much smaller file server (around 600 GB)

[JoelK]

You can modify the path in registry, then you can upgrade.

[EdgarRicharte]

Check "mount server" under each backup repo and make sure vPowerNFS it is pointed to a drive that exists.