It now works, but was not happy after upgrading to v13

[e.rottier]

Hi,

The upgrade from v11 to v12 went fine. No issues and everything worked flawlessly.
The upgrade to v13 however, did not go as well.

I wanted to let Veeam know what went wrong for me. Maybe someone else could use some of the solutions as well.
All issues are mostly resolved one way or another.

• I had to remove my Veeam-configuration-backup-to-tape system (repo->file->tape);
  • I've made a separate post about it here Veeam config to tape;
• Then two (out of four) application-aware VM backups failed;
  • I've fixed this by manually installing the Guest Agent on those servers.
• The Linux Volume level backup failed;
  • Had to re-implement kb4732 (rebuild the veeamsnap module).
• All OLVM VMs backup failed;
  • Temporary fix was to allow all ports, after which it suddenly worked again, although there are no new ports required in v13... (we have an ACL inplace between backup server and targets). I still need to find out which port I need to allow - on my todo list.
• I have made Powershell scripts to e-mail me which tapes to take out, these failed as well.
  • When manually running the script, I get "The Powershell module Veeam.Backup.Powershell won't load. This may be due to corruption or not installed. Quitting." Nice and descriptive, right? I needed Reddit to tell me it was because it required Powershell 7! This fixed it. (run with 'pwsh' instead of 'powershell' in Task Scheduler) It's not mentioned in any (upgrade)documentation as far as I can search.

Besides how well or not I've implemented everything, I would've expected a smoother experience to be honest.

Regards.

[e.rottier]

Backup to tape is now also fixed. I had to register the B&R server as a File Server under Inventory -> Unstructured Data.
After that I could browse again to the repository as a file source.

Warning -> opinion incoming!
One thing I forgot to mention. I really dislike the new GUI icons. They are too thin and thus hard too see. I cannot imagine the designer asking someone whose sight is impaired if this is a good design. Because it isn't IMO. The lines are too thin which makes all icons useless for button identification, which I did kinda use them for.
Please take a new look at the design from the perspective of people with sight problems. At least give me an option to revert to the old icons.
The Midnight Green theme does help me personally, so there's that!

[e.rottier]

I think I also found a bug in either the documentation or the software.

I've found out why my worker -> Backup server communication was an issue. It suddenly uses a different port then v12.

I've made a support ticket and a post about this here: Wrong port for OLVM worker communication in v13

[robnicholsonmalt]

Another other experiences... tempted to wait a while before upgrading clients. Does this version backup Windows 11 25H2 without warning?

[e.rottier]

Hi Rob,

We have no clients in our network that we can reach through zero-trust. Besides that, we hold no actual (work-related) data on the devices for security reasons.
So, luckily I guess, I don't have (or better: can't have) that issue.

Regards.

[Steve-nIP]

Warning -> opinion incoming!
One thing I forgot to mention. I really dislike the new GUI icons. They are too thin and thus hard too see.

The line art and lack of colour makes everything look too similar, I would agree that it's harder on the eyes. Of course, it's an opinion, but others have shared it. I'm honestly not sure what was wrong with the look before. It's backup software, you don't need to have graphic designers fiddling with it just because.

[GaborCs]

Hi,

almost the same situation was our side,
lot of things needed to manually fixed,
not just VBR but ONE too

got another company with v12 which needds to be v13,
I plan to uninstall v12, and a clean install of v13, and after that restore the config - is this can be successful?

[AnubhavSh]

"I plan to uninstall v12, and a clean install of v13, and after that restore the config - is this can be successful?"

Yes, that's a good approach but please ensure your configuration has been tested in the past. I suggest, build a new isolated VM and to do a test restore of Veeam configuration.
Being a major release with some bugs, better to test the functionality before doing on production.

[e.rottier]

An update.

==============
Powershell script:
I just found out that a Powershell changelog exists.
https://helpcenter.veeam.com/docs/vbr/p ... tml?ver=13

It is said here that Powershell V7.1 is required. I really would've like this piece of info to be in the main documentation. You cannot expect non-dedicated backup admins to read every little bit of sub-part documentation.

PRO-TIP: (cost me an hour or two to find out)
If you use the like-operator in your script, this worked without an explicit wildcard in PS v5.
In PS v7 you are required to specify a wildcard. I used " where {$_.Location -like "Slot" ". I had to change this to " where {$_.Location -like "Slot *" "

==============
Worker port:
Long story short, they've changed internal components and changed the OLVM worker port to be in line with other plugins like Proxmox and Nutanix. Veeam support told me this is a documentation error, but I disagree.
I had this port closed and everything worked just fine. After updating I suddenly needed port TCP 19000 to be opened. This was NOT in their changelog!
I've linked the post before I made for this issue, click here for my post about this issue.