Cannot upgrade Veeam Mount Service from v11 to v12

[riahc3]

Hello

Everytime I try to upgrade the Veeam Mount Service from v11 to v12, the server crashes. Due to this, I cannot current use Veeam.

Logs dont indicate any error message. Ive tried running this as SYSTEM (the installer strangly asks for this) and obviously as admin. Non work.

How can I proceed?

[Mildur]

Hi John

Please open a case with our customer support and provide in the case the logs from this folder:
C:\ProgramData\Veeam\Setup\Temp
Don't forget to share the case number with us here.

Thanks,
Fabian

[riahc3]

Due to me having a NFR license, I believe I cannot open a case.

Code: Select all

[28.02.2020 21:02:24] <  4876> cli| LOG: Initializing log file ...
[28.02.2020 21:02:24] <  4876> ================================================================================
[28.02.2020 21:02:24] <  4876> VeeamFlrDrvInstaller.
[28.02.2020 21:02:24] <  4876> Host process path: C:\Windows\System32\MsiExec.exe.
[28.02.2020 21:02:24] <  4876> Process: 64 bit.
[28.02.2020 21:02:24] <  4876> VolumeCTUpdateOnly
[28.02.2020 21:02:24] <  4876>   Service [VeeamVolumeCT] [update]
[28.02.2020 21:02:24] <  4876>   Service was not installed.
[28.02.2020 21:02:24] <  4876> VolumeCTUpdateOnly ok.
[28.02.2020 21:02:24] <  4876> VeeamFlrDrvInstaller detached.
[28.02.2020 21:02:24] <  4876> ================================================================================
[28.02.2020 21:02:24] <  4876> 
[17.03.2021 21:02:54] <  2000> cli| LOG: Initializing log file ...
[17.03.2021 21:02:54] <  2000> ================================================================================
[17.03.2021 21:02:54] <  2000> VeeamFlrDrvInstaller.
[17.03.2021 21:02:54] <  2000> Host process path: C:\Windows\System32\MsiExec.exe.
[17.03.2021 21:02:54] <  2000> Process: 64 bit.
[17.03.2021 21:02:54] <  2000> VolumeCTUpdateOnly
[17.03.2021 21:02:54] <  2000>   Service [VeeamVolumeCT] [update]
[17.03.2021 21:02:54] <  2000>   Service was not installed.
[17.03.2021 21:02:54] <  2000> VolumeCTUpdateOnly ok.
[17.03.2021 21:02:54] <  2000> VeeamFlrDrvInstaller detached.
[17.03.2021 21:02:54] <  2000> ================================================================================
[17.03.2021 21:02:54] <  2000> 
[18.01.2022 21:04:28] <   576> cli| LOG: Initializing log file ...
[18.01.2022 21:04:28] <   576> ================================================================================
[18.01.2022 21:04:28] <   576> VeeamFlrDrvInstaller.
[18.01.2022 21:04:28] <   576> Host process path: C:\Windows\System32\MsiExec.exe.
[18.01.2022 21:04:28] <   576> Process: 64 bit.
[18.01.2022 21:04:28] <   576> VolumeCTUpdateOnly
[18.01.2022 21:04:28] <   576>   Service [VeeamVolumeCT] [update]
[18.01.2022 21:04:28] <   576>   Service was not installed.
[18.01.2022 21:04:28] <   576> VolumeCTUpdateOnly ok.
[18.01.2022 21:04:28] <   576> VeeamFlrDrvInstaller detached.
[18.01.2022 21:04:28] <   576> ================================================================================
[18.01.2022 21:04:28] <   576> 
[17.04.2022 17:24:49] <  8256> cli| LOG: Initializing log file ...
[17.04.2022 17:24:49] <  8256> ================================================================================
[17.04.2022 17:24:49] <  8256> VeeamFlrDrvInstaller.
[17.04.2022 17:24:49] <  8256> Host process path: C:\Windows\System32\MsiExec.exe.
[17.04.2022 17:24:49] <  8256> Process: 64 bit.
[17.04.2022 17:24:49] <  8256> VolumeCTUninstall
[17.04.2022 17:24:49] <  8256>   Service VeeamVolumeCT uninstall
[17.04.2022 17:24:49] <  8256>     Filter VeeamVolumeCT unregistry
[17.04.2022 17:24:49] <  8256>     Filter VeeamVolumeCT unregistry Failed.
[17.04.2022 17:24:49] <  8256> ERR |The system cannot find the file specified.
[17.04.2022 17:24:49] <  8256> >>  |Failed to read value [LowerFilters] from key [SYSTEM\CurrentControlSet\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f}]
[17.04.2022 17:24:49] <  8256> >>  |--tr:Error code: 0x00000002
[17.04.2022 17:24:49] <  8256> >>  |--tr:Failed to unregister filter
[17.04.2022 17:24:49] <  8256> >>  |An exception was thrown from thread [8256].
[17.04.2022 17:24:49] <  8256>     Unload VeeamVolumeCT
[17.04.2022 17:24:49] <  8256>       Service VeeamVolumeCT does not exist.
[17.04.2022 17:24:49] <  8256> VolumeCTUninstall ok.
[17.04.2022 17:24:49] <  8256> VeeamFlrDrvInstaller detached.
[17.04.2022 17:24:49] <  8256> ================================================================================
[17.04.2022 17:24:49] <  8256> 
[22.02.2023 21:04:54] <  1288> cli| LOG: Initializing log file ...
[22.02.2023 21:04:54] <  1288> ================================================================================
[22.02.2023 21:04:54] <  1288> VeeamFlrDrvInstaller.
[22.02.2023 21:04:54] <  1288> Host process path: C:\Windows\System32\MsiExec.exe.
[22.02.2023 21:04:54] <  1288> Process: 64 bit.
[22.02.2023 21:04:54] <  1288> VolumeCTUpdateOnly
[22.02.2023 21:04:54] <  1288>   Service [VeeamVolumeCT] [update]
[22.02.2023 21:04:54] <  1288>     Loading service VeeamVolumeCT
[22.02.2023 21:04:54] <  1288>       source inf: [C:\Program Files\Veeam\Endpoint Backup\CBTDriver\Win2016\\VeeamVolumeCT.inf]
[22.02.2023 21:04:54] <  1288>       source sys: [C:\Program Files\Veeam\Endpoint Backup\CBTDriver\Win2016\\VeeamVolumeCT.sys]
[22.02.2023 21:04:54] <  1288>       Destination .sys file already exist
[22.02.2023 21:04:54] <  1288>       Comparing file versions.
[22.02.2023 21:04:54] <  1288>       New file [C:\Program Files\Veeam\Endpoint Backup\CBTDriver\Win2016\\VeeamVolumeCT.sys].
[22.02.2023 21:04:54] <  1288>       Old file [C:\Windows\System32\drivers\VeeamVolumeCT.sys].
[22.02.2023 21:04:55] <  1288>       destination inf path [C:\Windows\INF\oem4.inf]
[22.02.2023 21:04:55] <  1288>       destination inf name [oem4.inf]
[22.02.2023 21:04:55] <  1288>       Driver version: 12.0.0.53
[22.02.2023 21:04:55] <  1288>       Service VeeamVolumeCT already registered at the SCM.
[22.02.2023 21:04:55] <  1288>       warning: VolumeUpdateVersionReFSv3Algorithm: step [1], error [2][00000002]
[22.02.2023 21:04:55] <  1288>       Option version ReFS v3 algorithm for detect offline changes updated to [3.9]
[22.02.2023 21:04:55] <  1288>     Volatile key [SOFTWARE\Veeam\Volatile] created.
[22.02.2023 21:04:55] <  1288> WARN|Reboot needed.
[22.02.2023 21:04:55] <  1288> VolumeCTUpdateOnly ok.
[22.02.2023 21:04:55] <  1288> VeeamFlrDrvInstaller detached.
[22.02.2023 21:04:55] <  1288> ================================================================================
[22.02.2023 21:04:55] <  1288> 

[riahc3]

Thats what the latest log file says in said folder.

[riahc3]

The VM in question is running Server 2019

[Mildur]

Due to me having a NFR license, I believe I cannot open a case.

You can, but support is provided on best effort. And please don't upload logs in the forum. The forum is run by product management. Not by our technical support team. We don't have the tools to analyze debug log files.
Our customer support team has this tools and is trained to use them.

We mention both points (support for NFR, log upload) in our forum rules:
Rules of posting errors and technical issues

Best,
Fabian

[riahc3]

When I attempt to open a ticket, it gives me a error that I need to upgrade my profile and I cannot open it.

So how do I open a ticket when I am getting a error????

[riahc3]

This is starting to get critical as Im now at least a week without backups....

How can I solve this?

Thank you

[Mildur]

Hi John

Support portal is not run by us. Are you using a mail address from a public mail hosting service? Or is it your business address?
If you have issues with your account, please try a case from type "General Inquiry" instead of technical issues.

Unfortunately as already stated, we cannot solve such technical issues over the forum. This is not a replacement for our customer support.
You can try to install the mount service manually with the msi file. But I don't guarantee that this will work. Make sure to have a backup of your machine before doing so.
"ISO:\Packages\VeeamMountService.msi"

Also disable your antivirus software running on this system. Just in case it blocks something. And if the server crashes, you can also start troubleshooting with Microsoft log files. BlueScreen? Analyze the minidump file windows can create.

Best,
Fabian

[riahc3]

Hello

I do not have a business email address.

I also attempted to install it manually, just like you indicated and still nothing.

I looked at the minidump file that Windows creates but do not see anything that calls my attention.

Just in case it isnt clear, this is what is popping up for me:

https://media.giphy.com/media/v1.Y2lkPT ... /giphy.gif

[riahc3]

The only other thing I can think of is a migration.

The target server runs the VM jobs and a data copy backup. If I create a new VM, will it be possible to continue the jobs, with its history and such?

[Mildur]

Thanks.
Opening a support case with us requires you to fill out this information.

Yes, you also start with a new server. Backup Chains will continue. You can use the configuration backup to migrate to a new backup server:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Please note, V11 configuration backups can only be imported to V12, if you use MSSQL as the configuration database in V12.
If you don't want to install a MSSQL yourself, your upgrade path looks like this:
1) Deploy new VM
2) Install V11a
3) restore configuration backup
4) Upgrade to V12

Best,
Fabian

[riahc3]

Is there a free domain is that supported? Like I mentioned, I do not have a business email.

Tried it in safe mode with no services loaded:

IRQL_NOT_LESS_OR_EQUAL

Your last points...I dont understand correctly...

I currently already have installed the central V12 with my backup jobs already set.

Im just having issues on a target server where backups are stored.

What I was gonna do is:

1) Install new VM
2) Set as a new repository this new VM
3) Point all my backups to this new repository

I am indeed using a MSSQL database. Entered in the credentials when upgrading.

[Mildur]

Hi John

I assumed, you are using a standalone server in this home lab.
If you only have issues with your repository server, then your plan sounds valid.
You can also move all of your backup files to the new repository VM and map your backup jobs.

Best,
Fabian

[riahc3]

OK, there is something else going on and I think its a bug on Veeam's side....

Installed a brand new fresh VM, from Microsoft's official ISO. Server 2022. Nothing else is on the server.

Tried to install Veeam Mount Service and it BSOD.

So this is on Veeam now, nothing to do with my virtual machine.

[riahc3]

Hi John

I assumed, you are using a standalone server in this home lab.
If you only have issues with your repository server, then your plan sounds valid.
You can also move all of your backup files to the new repository VM and map your backup jobs.

Best,
Fabian

This is a standalone VM server joined to my domain at home.

[riahc3]

OK, its a EXTREMELY strange bug...

On a ESXi hypervisor, I install it and works perfectly.

But

On the Hyper-V hypervisor, It BSODs.....

AFAIK, there is no sys requirements change on Veeam 12 for ESXi and Hyper-V

ESXi is 6.7 and Hyper-V is 2019

[riahc3]

Yeah there is some weird issue. Workaround:

1) Install a brand new Server 2022 VM on ESXi
2) Run and install the packages needed standalone (Veeam Agent, Veeam Backup Transport, Veeam Backup vPowerNFS, and Veeam Mount Service. Im missing the Veeam CBT Driver but I imagine its because there is no license installed. I HOPE that doesnt give a issue later on....)
3) Starwind V2V: ESXi to Hyper-V
4) Shutdown the ESXi VM
5) Boot up the Hyper-V VM

No BSOD at all. Services up and running.

This is a extremely sloppy job from Veeam. The obvious workaround when installing is to install the components then ask for a reboot instead of trying to install and start the driver/component/service/etc. Sometimes reboots NEED to be done. Its obvious that this supported scenario (OS are supported, etc) for some reason, BSODs and needs a reboot.