Veeam Backup for Salesforce • Re: Auto Upgrade to V2 with no warning

So going back to my first question, I feel after every version change the command 'dnf versionlock"vbsf*"'

has anyone observed this behavior?

Yes, I have seen this as well and this is a result of a limitation of versionlock. When you versionlock "vbsf*", it doesn't set an entry for "vbsf*", it expands out everything that matches it and versionlocks that. Once the new version of vbsf is installed, it (obviously) won't be in the versionlock list from before, and the old version was removed so that won't be in the list either, leaving no vbsf entry in versionlock. So I agree with you: it seems like Veeam needs to add a new 'dnf versionlock vbsf*' to the end of every upgrade process to ensure that the new version gets locked properly.

Statistics: Posted by RubinCompServ — Sep 17, 2025 1:40 pm

---