Veeam Backup for Salesforce 3.1.1
Release Notes
User Guide

Veeam Backup for Salesforce 3.1.1 Release Notes

This document provides last-minute information on Veeam Backup for Salesforce 3.1.1, including system requirements, installation, as well as relevant information on technical support, documentation, online resources and so on.

The release version of Veeam Backup for Salesforce 3.1.1 (3.1.1.2714) is available for download at https://www.veeam.com/backup-salesforce-download.html starting from February 12, 2025.

See next:

System Requirements

Salesforce

  • Salesforce Edition: Salesforce platform edition with API access. Applications that are integrated with Salesforce but not built on Salesforce platform are not supported, for example: Tableau, Slack, ExactTarget (Salesforce Marketing Cloud). The list of editions is posted in Salesforce documentation https://help.salesforce.com/s/articleView?id=000385436&type=1.
  • API version: By default, Veeam Backup for Salesforce 3.1.1 uses Salesforce API version 60.0. Any objects available in later API versions will not be discovered and protected by the product. Administrator can change the Salesforce API version as described in documentation by configuring Advanced Settings.

Management Server

Hardware

OS

The following 64-bit versions of operating systems are supported:

  • 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
  • Ubuntu 20.04.x LTS, 22.04.x LTS, 24.04.x LTS

Note: Ubuntu 24.04.x LTS is experimentally supported in Veeam Backup for Salesforce version 3.1.1 and later. For more information on experimental support, see https://www.veeam.com/kb2976.

Software

PostgreSQL Server

Hardware

  • CPU: modern multi-core x64 processor, 4 CPU cores (minimum).
  • Memory: 16 GB RAM (minimum). Consider allocating 16 GB RAM if the largest Salesforce object you have contains under 2M records, and 32 GB RAM or more if you have objects with over 20M records.
  • Disk: Flash/SSD-based storage system. Database server storage sizing must consider the volume of your Salesforce data storage, daily change rate and the rate of replication.
  • For more information on sizing recommendations, see https://helpcenter.veeam.com/docs/backup_salesforce/userguide/sizing_postgresql.html?ver=30.

Software

  • PostgreSQL 13.x, 14.x, 15.x (version 15.10 is included in the setup). Minimal supported version is PostgreSQL 13.

User Console

  • Web-based user interface requires the latest version of either Microsoft Edge, Mozilla Firefox, or Google Chrome.
  • Access to Salesforce via HTTPS is required to pass Salesforce authentication.

Known Issues and Limitations

The following is a list of issues known to exist at the time of the Veeam Backup for Salesforce 3.1.1:

General

  • With Salesforce SSO configured, due to specifics of how Salesforce token works, it is not recommended to use same Salesforce user to log into the application and to do the backup. Signing into the application with the Salesforce integration user account will cause the backup session token to expire after 5 logins. Backup jobs will fail with expired token message as the authorization token will be revoked by Salesforce.

Backup

  • Backup and restore is not available for these objects:

    • BigObject type
    • Idea and related objects
    • KnowledgeArticle type
  • Backup of inline images in rich text format field is possible only if the field is not configured for encryption.
  • If an organization has multiple objects with several rich text fields, application might require changes in the default settings for the time of initial backup. These settings are not available via “Advanced Settings” configuration, please contact Veeam support team for assistance.
  • Backup of inline images for ContentNote objects is not supported.
  • Data reload feature, which allows to update specific fields of an object or a specific file type in a backup, is not available for FeedItem.

Restore

  • FeedAttachment restore should be executed as part of FeedItem hierarchy restore. ContentVersion is restored only if its added as attachment, not as an inline image.
  • Restore of inline image for rich text format field, ContentNote, FeedItem and FeedComment is not available in v3.1.1. Coming soon.
  • In case of a field API name change, restore of a record version created prior the metadata change is not possible.
  • Cloning of restore jobs created in product versions before v3.0 is not supported.

Restore with Disable Automation Feature

  • Disable automation feature cannot modify metadata for managed packages thus cannot disable the triggering automation for the backup user. Other automations will be updated to exclude backup user from business rules.
  • Disabling of a flow will fail if the maximum versions limit is reached in Salesforce. Flow version limits are described here https://help.salesforce.com/s/articleView?id=sf.flow_considerations_limit.htm&type=5
  • Disabling of lookup filters and validation rules will fail if 10 or more filters are already defined in Salesforce.

Data Archival

  • Data archival is not supported for following objects:

    • All history objects
    • ContentNote
    • Profile
    • Organization
    • User
    • SelfServiceUser
    • RecordType
    • SObjects without “delete” API

Installing Veeam Backup for Salesforce

Installation instructions are similar to RPM-based and Debian-based packages. We recommend installing the product using the installation script that will do all the work for you. All steps are performed with privileged permissions using the sudo command.

  • Set the Linux system locale to en_US.UTF-8

RedHat/Oracle/Rocky Linux/AlmaLinux

sudo localectl set-locale LANG=en_US.UTF-8

Ubuntu

sudo locale-gen en_US.UTF-8

sudo localectl set-locale LANG=en_US.UTF-8

sudo update-locale

  1. Download the quick installation script

sudo curl https://repository.veeam.com/yum/el/vbsf-install-script.sh --output ./vbsf-install-script.sh

  1. Run the script

sudo bash ./vbsf-install-script.sh

  1. When the configuration process completes, open the generated URL in your browser and finish the initial setup wizard.

Alternatively, you can install the product using step-by-step instructions described in documentation https://helpcenter.veeam.com/docs/backup_salesforce/userguide/deployment.html?ver=30.

Important: During installation, an encryption product key is created and stored in the installation folder: /opt/vbsf/vbsf-backend/config/product.key. This product key encrypts all secrets in the database and protects organization specific encryption key used by built-in data enctyption. Make sure that you do not lose this key, otherwise, the product will require reconfiguration and encrypted data will be lost. Veeam will not be able to help you decrypt the data.

Uninstalling Veeam Backup for Salesforce

  • If backed-up data is encrypted using built-in encryption, make sure to keep copy of the product encryption key before uninstalling Veeam Backup for Salesforce.
  • Uninstall the product package

RedHat/Oracle/Rocky Linux/AlmaLinux

sudo yum remove vbsf

Ubuntu

sudo apt remove vbsf

  • Package manager will not remove the data repository located in /opt/vbsf/data. You will need to delete this folder manually.
  • Package removal will not delete any databases as well. You will need to delete the backup databases manually.

Upgrading Veeam Backup for Salesforce

Veeam Backup for Salesforce 3.1 supports automated in-place upgrade from previous versions, which preserves all configuration and settings. Automated upgrade is not supported for installations running on Centos or PostgreSQL 12, upgrade should be done manually.

Upgrading from any pre-release or Beta version is not supported unless advised by Veeam Support team.

Check for the new product version using the Configuration > About > Check for Updates link. Follow the link to launch Veeam Updater, select the most recent build and start the upgrade. Veeam Updater will first upgrade to version 9.x and then the product upgrade can be continued.

Upgrade Preparation Checklist

Use the following checklist to ensure that your infrastructure is ready for Veeam Backup for Salesforce in-place upgrade.

  • Make sure that management server meets minimal system requirements.
  • Make sure that your PostgreSQL server meets minimal system requirements. PostgreSQL 12.x customers need to upgrade their PostgreSQL version to any supported version first. Version 15.10 is recommended.
  • It is recommended to create a VM or disk snapshot for the database server before applying the update.

Product Upgrade Steps

To upgrade Veeam Backup for Salesforce, do the following:

  • Make sure there are no running backup policies
  • Make sure there are no running data archival policies
  • Make sure there are no running restore jobs
  • Disable backup policies
  • Disable data archival policies
  • Perform the upgrade using Veeam Updater at Configuration > About > Check for Updates

    • To perform upgrade manually for installations running on Centos or PostgreSQL 12 see instructions below.
  • Enable backup policies. Database migration jobs will be executed after the upgrade during the first backup policy run. The backup process will not start until the migrations are done. As soon as the migrations complete, backup policies will run as usual.

Additional Information

  • Default file storage location is /opt/vbsf/data. Administrators can configure a new location in Advanced Settings. When changing the default file storage location, you must manually move any existing repositories to the new location before you enable backup policies.
  • Default Salesforce API setting will be updated to Salesforce API v60. Any custom configuration for other advanced settings will not be changed during the upgrade process.
  • If you are upgrading product from version prior to v3.0, then Salesforce API v60 will bring new set of objects and fields for existing objects which will result in larger incremental backup after the upgrade.
  • If you had a custom build with internet proxy support, you will need to re-configure proxy.settings in Configuration > About > Advanced Settings before enabling backup policy.
  • Once upgraded, the first run of backup policies will start database migration procedures. These procedures will block any changes to the backup database and backup policies may report the Failed status. Once migration is finished, backup policies will start working as normal. Restarting the application during database migrations will result in corrupted installation and backup repository.
  • Salesforce text (encrypted) fields are added to the list of exceptions for the backup policy when upgrading product from v2.x to v3.1. If required, policy can be updated to include those fields in the backup. Backup User should have permission to view encrypted data. When upgrading from v1.x to v3.1, fields are included in the backup policy automatically.
  • For upgraded product installations, metadata items such as fields, validation rules and list view, can be restored independently from Custom Object only after object was modified. Restore point created as a result will be the first available restore point for such metadata items. In the new installations feature is available right away.
  • To download images for rich text format field for existing backups, it is required to use reload object action for the corresponding object.
  • Once product upgrade is completed, it is recommended to run backup policy, and only then do any restore and data archival operations.

Upgrading Veeam Backup for Salesforce Running on Centos

This is an overview of steps required to upgrade the product. It is made with an assumption that new version 3.1.1 will be installed on a separate server with supported OS, and both product configuration and backup databases should be preserved and used for the new installation. For detailed steps see: https://www.veeam.com/kb4664

  • Prepare source enviroment for migration:

    • Disable backup policies.
    • Make sure there are no running backup policies.
    • Make sure there are no running restore jobs.
    • Stop backend service.
  • Install Veeam Backup for Salesforce v3.1.1 on target enviroment following the instruction above.

    • Save, but do not yet open the generated URL of the initial setup wizard.
    • Stop backend service.
    • Delete https.properties from new invironment.
    • Replace product encryption key created for v3.1.1 installation with a product key from source installation, to avoid re-authorising all connections after migration. Required for customers migrating from the product version 2.x.
    • Import or connect existing configuration and backup databases to a new installation.
  • Move folder with backed-up files and metadata to the new installation.
  • Update Salesforce Connected App with Callback URL of the new installation.
  • Finish v3.1.1 installation configuration:

    • Start backend service.
    • Run initial setup wizard using URL generated during v3 installation. Make sure to provide connection details of migrated configuration database.
    • Update migrated configuration of the product with address of new management server. Log in with the local administrator account, go to Configuration > About > Advanced Settings and edit the backend.domain parameter to match the domain name of the new installation.
    • Verify and update, if needed, connection details for each backup database at Configuration > Salesforce > Databases.
    • Enable backup policies.
    • Once upgraded, the first run of backup policies will start database migration procedures. These procedures will block any changes to the backup database and backup policies may report the Failed status. Once migration is finished, backup policies will start working as normal. Restarting the application during database migrations will result in corrupted installation and backup repository.
  • In case Single Sign-On with Microsoft Entra ID was configured, the configuration change is required on the Microsoft Entra ID side:

    • In Microsoft Entra ID, go to the App Registration > Authentication section and modify the Redirect URI to match the domain name of the management server.

Upgrading Veeam Backup for Salesforce Running on PostgreSQL 12

Before starting with product upgrade, wheather automated upgrade for supported OS or manual for Centos, required to upgrade ProstgreSQL to at least version 13. If configuration and backup databases are located on different servers, then both servers should be upgraded to supported PostgreSQL version. This is an overview of required steps. For details see: https://www.veeam.com/kb4665

  • Prepare an enviroment for upgrade:

    • Disable backup policies.
    • Make sure there are no running backup policies.
    • Make sure there are no running restore jobs.
    • Stop backend service.
  • Upgrade PostgreSQL. For more information see: https://www.postgresql.org/docs/12/upgrading.html
  • If operating system upgrade is not required, start backend service.
  • Verify and update, if needed, connection details for each backup database at Configuration > Salesforce > Databases.
  • Enable backup policies.

Licensing

Veeam Backup for Salesforce is using a standalone license and it is not part of the Veeam Universal License. Veeam Backup for Salesforce is licensed with Standard User or Platform User Salesforce license. 100% of active users must be licensed.

Identity, Chatter, Community and other types of Salesforce user licenses are not counted for the product license.

Free Community edition license for 50 Users is built into the product. It allows protecting Salesforce organizations with up to 50 active users. That is, if you have 2 Salesforce organizations with 20 Users, you can protect both with one Community edition license.

Subscription, Evaluation and NFR licenses are supported by the product. Product requires connection to Veeam License Services to activate, validate and update the license, and meter license usage. Product will stop operating within 30 days if the license verification cannot be completed.

Two package options are available for the product license:

  • Foundation license package (available for the Community Edition and Subscription license types) allows to perform backup and restore operations.
  • Advanced license package (available for the Evaluation, NFR and Subscription license types) includes backup, restore and data archival.

Technical Documentation References

If you have any questions about Veeam Backup for Salesforce, you may use the following resources:

Technical Support

Veeam offers email and phone technical support for customers on maintenance and during the official evaluation period. For better experience, please provide the following when contacting our technical support:

  • Version information for the product and all infrastructure components.
  • Error message and/or accurate description of the problem you are having.
  • Log files. To export the log files, select Configuration > About > Support and follow the wizard to export the relevant set of log files.

To submit your support ticket or obtain additional information, please visit www.veeam.com/support.html.

Contacting Veeam Software

At Veeam Software, we pay close attention to comments from our customers — we make it our mission to listen to your input, and to build our products with your suggestions in mind. We encourage all customers to join Veeam R&D forums and share their feedback directly with the Product Management team.

Should you have a technical or licensing issue or question, please feel free to contact our Customer Support organization directly. We have qualified technical and customer support staff available 24 hours a day, 7 days a week who will help you with any inquiry that you may have.

Customer Support

For the most up to date information about our support practices, business hours and contact details, please visit www.veeam.com/support.html. You can also use this page to submit a support ticket and download the support policy guide.

Company Contacts

For the most up to date information about company contacts and office locations, please visit www.veeam.com/contacts.

Document updated 2/25/2025

Document content applies to build 3.1.1.2714

View all results across Veeam
Back to document search