Upgrade v6 to v6.1 Infinite loop of reboots

[tfloor]

Hi,

I just upgraded our windows 2008 R2 physical Server from veeam v6 to v6.1
After the upgrade the installer asks for reboot, so i did.
It know goes to "APPLYING COMPUTER SETTINGS".. wait some time and the reboot , again , again and again.

Any idea?

I had rebooted the server just before the upgrade without any problems.

Regards,

Tristan

[UPDATE] This issue is caused due to not following the upgrade procedure listed in the Release Notes document, specifically at the part that requires you to upgrade the Enterprise Manager server first, before upgrading actual backup servers. Only happens when both backup server and Enterprise Management server are installed on the same computer.

[tfloor]

Going back to "last known good configuration" gives me my server back in a controlled state

[Vitaliy S.]

Hi Tristan,

Can you please contact our support team and let them have a look at this issue live? Also can you please set Veeam services to Manual startup type, verify that your machine boots normally and then start Veeam services?

Thanks!

[htwnrva]

Same problem here with a physical 2008 R2 box. I'll open a case also. I had to last known good configuration it also however is that going to have a negative effect on the application we just installed?

[Gostev]

Might be due to some 3rd party software incompatibility, as obviously we only test upgrade on clean installs. Kindly please open support case to let us research this more closely. As far as I can judge from social media, upgrades are reported to be successful so far, but any similar issue reported more than once already worth being closely research.

[wvd]

Same here after upgrade. Virtual 2008 R2. Veeam monitor is installed on same box and it is also a domain controller. (homelab)

[Gostev]

So, I've been told that the most likely reason for this is not following the upgrade procedure listed in the Release Notes document, specifically at the part that requires you to upgrade the Enterprise Manager server first, before upgrading actual backup servers.

I will not have any further details until I talk to R&D tomorrow morning. If you had run into this issue, please open a support case and we will get back to you with the best resolution once we have the resolution validated.

Unverified workaround:
1. Boot into safe mode
2. Disable the Veeam catalog service
3. Boot back into normal mode
4. Upgrade Enterprise Manager to 6.1
5. Enable the Veeam catalog service.

[htwnrva]

I would be guilty of not upgrading enterprise manager first, also of not readying those notes too carefully

[Jfmoots]

This happened to me and the above unverified workaround worked like a charm.

[tfloor]

I was not able to go to safe mode. This one also reboots
I don't have upgraded enterprise manager first haha hmmm
And I also have veeam one installed on that physical server.
Glad to hear I'm not the only one. I will go today further with my server and do a health check.

Regards
Tristan

[dellock6]

I forgot too to upgrade Enteprise Manager first, but the Veeam Server upgrade was successful anyway, the only problem was the report of the old enterprise manager obviously stating this night we had 0 jobs. I upgraded Enteprise Manager this morning and it connected without a problem to the Veeam Server, showing also the jobs from Veeam Server 6.1

Luca.

[NightBird]

I was not able to go to safe mode. This one also reboots
I don't have upgraded enterprise manager first haha hmmm
And I also have veeam one installed on that physical server.
Glad to hear I'm not the only one. I will go today further with my server and do a health check.

Regards
Tristan

Same problem here.
I have to boot in recovery mode and load the registry hive to disable the Veeam services.

Boris

[tfloor]

Whoei, that's a lot more than i had todo.
I'm wondering if this was a suspected result if you don't upgrade veeam backup enterprise manager first.
Most of the time windows is clever enough to pass the services if it fail.

[jfrmilner]

Same problem here.
I have to boot in recovery mode and load the registry hive to disable the Veeam services.

Boris

Like NightBird my installation kept rebooting even in safemode.

Steps to resolve (for me)
1. Change SCSI to LSI SAS if you are running Paravirtual as WinRE is unable to mount the disk (you could also use a driver disk if you have one handy).
2. Boot from Windows 2008 R2 DVD
3. Select Repair
4. Load recovery tools
5. Launch regedit and open the system hive *:\Windows\System32\Config\system
6. Navigate to CurrentControlSet001\Services\
7. Set the Start type of all the Veeam services to 4 (Disabled)
8. Shutdown and restore SCSI to Paravirtual
9. Start VM and install Enterprise Manager, it'll complain at the end of the installation about the services, at this point I restored them all back to automatic.
10. Done. Remember to RTFRN!

Hope this helps someone.

Regards,

jfrmilner

[stormlight]

Is there a way to see if you have enterprise management server installed? I can't remember if we installed it.

[Vitaliy S.]

Since this issue only happens when you have both Veeam backup server and Enterprise Manager deployed on the same machine, you can just check EM presence using "Add or remove programs" on your backup server.

[KevinBeaumont]

Folks

Just for info, I had this exact problem on our Veeam physical backup server (Win Server 2003 R2) - but we hadn't upgraded to 6.1. Fun! Not sure of cause yet. I googled the symptoms and ended up at this forum - the "Last known good configuration" suggestion worked fine, server is back now. It's entirely possible it isn't Veeam related.