Upgraded test VBR to v13, failed.

[lando_uk]

Hi
I have a V12 VBR test server with no backups or hardly any config. It's purely for testing upgrades before i hit the prod.
A ran the upgrade, it took a while, got to step 7 but when it tried to restart the backup service but kept failing.
After a restart im now stuck with a v13 install that doesn't load the backup service, it just times out and eventually fails.

This EC2 server was very min spec v12, it was 2c 8GB - like i said it was purely for testing upgrades and patches and has been useful in that respect.

I read that the min requirements for v13 are now 8c, 16GB - Is this why the upgrade failed and the service no longer starts? I dont care about performance, but will v13 literally not work with under 8c now? It this is true, then surely a core count should be detected and displayed in the upgrade prerequirements check?

Im currently running the VeeamBackup&Replication_13.0.1.1071_patch_20251217 from the ISO, maybe it'll fix the broken upgrade - after that i'll increase the EC2 instance size to see if that works.
Failing that, it looks like i'll restore from snapshot back to v12 and re-think.
I didnt want to bother support with this, as it's purely test and I'm trying to fix it myself, or i'll just rollback eventually.

My prod is 4c,16gb. So will i need to change that to 8c before kicking off the upgrade?

Thanks

[lando_uk]

So i upped the instance size to t3a.2xlarge and it all now works.

Now my test server wil cost x4 the money to run, wonderful.

[Steve-nIP]

Try downsizing it after. My guess it's only the installer that checks.