Loading...
Loading...
After Veeam Backup for Salesforce is upgraded from version 2.1.1 or earlier to version 3.2.1 or later, the vbsf-backend service fails to start. The state of the service can be confirmed with the following command:
This issue occurs because Veeam Backup for Salesforce 3.2.1 requires OpenJDK 21, while version 2.1.1 and earlier required OpenJDK 11. The OpenJDK 21 package is installed automatically as a dependency of the vbsf-backend package. The upgrade does not, however, change which Java version is active on the server. If OpenJDK 11 was previously set as the active version through the Linux alternatives mechanism, it remains active after the upgrade. Because the vbsf-backend service starts Java through the generic /usr/bin/java path, OpenJDK 11 continues to be used after the upgrade. OpenJDK 11 is not compatible with Veeam Backup for Salesforce 3.2.1 or later, so the service fails to start. Only upgrades from version 2.1.1 or earlier are affected. Upgrades from version 3.0.0 or later are not affected, as those versions do not use OpenJDK 11.
Servers Shared with Other Java Applications OpenJDK 11 is not removed during the upgrade and may remain installed for other purposes on the same server. Setting the active Java version changes which version /usr/bin/java points to system-wide. Before this change is applied in production, confirm that it does not conflict with other Java-dependent applications running on the same server.
Related Documentation Veeam Backup for Salesforce User Guide > Upgrading Veeam Backup for Salesforce Veeam Backup for Salesforce User Guide > System Requirements
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.