Views
1

Your rating
Rate update installation process

Log in to rate this update.
Login

Risk factor
No ratings yet. Be the first to rate this update.

Smooth installs 0%
Minor issues 0%
Major issues 0%

Update Summary

Veeam Backup for Salesforce 3.2.0 (3.2.0.3957) was released on 2026-04-16. The notes mainly cover system requirements, download availability, and known backup/restore limitations.

Update Details

Security

  • With Salesforce SSO, using the same Salesforce user for the application and backups is not recommended because the backup session token can expire after 5 logins and jobs may fail when Salesforce revokes the authorization token.
  • Disable automation cannot modify metadata for managed packages, so triggering automation for the backup user may not be fully excluded from business rules.

Known Issues

  • Backup and restore are not available for BigObject, Idea-related objects, and KnowledgeArticle objects.
  • Inline images in rich text fields are backed up only when the field is not encrypted.
  • Initial backup settings may need manual adjustment for organizations with multiple objects and several rich text fields; Veeam support may be required.
  • Inline images for ContentNote objects are not supported for backup.
  • Data reload is not available for FeedItem.
  • FeedAttachment restore must be performed as part of FeedItem hierarchy restore.
  • ContentVersion is restored only when attached as a file, not as an inline image.
  • Restore of inline images for rich text fields, ContentNote, FeedItem, and FeedComment is not available in v3.2.0.
  • If an API name changes, restoring a record version created before the metadata change is not possible.
  • Cloning restore jobs created before v3.0 is not supported.
  • Restore of files larger than 2 GB is not supported due to Salesforce API limitations.
  • Disabling a flow may fail if the maximum version limit is reached in Salesforce.
  • Disabling lookup filters and validation rules may fail if 10 or more filters are already defined.
  • Data archival is not supported for history objects, ContentNote, Profile, Organization, User, SelfServiceUser, RecordType, or SObjects without a delete API.

Hints

  • Release version 3.2.0.3957 is available for download starting 2026-04-16.
  • Default Salesforce API version is 66.0; objects introduced in later API versions will not be discovered or protected unless the API version is changed in Advanced Settings.
  • Supported management server OSes include RedHat Linux 8.x/9.x, Oracle Linux 8.x/9.x, AlmaLinux 8.8-8.10/9.x, Rocky Linux 8.8-8.10/9.x, and Ubuntu 22.04.x LTS/24.04.x LTS.
  • Oracle JDK 17 is required, and the Linux locale must be set to en_US.UTF-8.
  • PostgreSQL 14.x or 15.x is supported; version 15.11 is included in the setup.
  • The PostgreSQL contrib package is required only when using custom.relationships or nested.custom.relationships features.
  • Recommended mount points are /opt/vbsf/data for file storage and /var/log/vbsf for logs.
  • Salesforce access over HTTPS is required for authentication.

Links

Product Information

Vendor: Veeam Backup

Product: Veem

Version: 3.2.0.3957

Release date: Apr 16, 2026