Veeam Backup for Salesforce 2.1.1 Release Notes
This document provides last-minute information on Veeam Backup for Salesforce 2.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 2.1.1 (2.1.1.4793) is available for download at Downloads: Previous Versions 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 2.1.1 uses Salesforce API version 57.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
- CPU: modern multi-core x64 processor, 4 CPU cores (minimum).
- Memory: 8 GB RAM (minimum). With multiple protected organizations, consider adding 1GB per each protected Salesforce organization.
- Disk: 100 GB (minimum), excluding files and logs storage space.
OS
The following 64-bit versions of operating systems are supported:
- CentOS 7
- RedHat Linux 7, 8
- Oracle Linux 7, 8
- AlmaLinux 8.8 (Experimental support)
- Rocky Linux 8.8 (Experimental support)
- Ubuntu 20.04 LTS, 22.04 LTS
Software
- Linux system locale must be set to
en_US.UTF-8
. - Nginx repository needs to be configured.
- Consider using dedicated partition for files storage, mounted to
/opt/vbsf/data
. - Consider using dedicated partition for logs, mounted to
/var/log/vbsf
. - For more information on sizing recommendations, see https://helpcenter.veeam.com/docs/vbsf/userguide/sys_requirements.html?ver=20.
- For more information on open ports configuration, see https://helpcenter.veeam.com/docs/vbsf/userguide/ports.html?ver=20.
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 take into account 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/vbsf/userguide/sizing_postgresql.html?ver=20.
Software
- PostgreSQL 13-14. Minimal supported version is PostgreSQL 12
- PostgreSQL 15 (Experimental support)
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 2.1.1:
General
- User Interface access with Chromium or Firefox on Linux is not supported.
- With Salesforce SSO configured, 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
- Encrypted fields are not backed up:
- field type: Text (Encrypted)
Restore
- FeedAttachment restore is possible as part of FeedItem hierarchy restore. ContentVersion must be present in Salesforce before you restore a FeedAttachment. When deleted, you can restore the ContentVersion using the file restore wizard.
- Restoring to another Salesforce organization requires the User record ID to be present in the target organization.
Restore with Disable Automation Feature
- The Disable Automation feature will update all triggered automation, such as triggers, flows, workflows, validation rules, lookup filters to exclude the configured Salesforce user from those business rules. Components of managed packages cannot be modified and will not be updated.
- 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 filters are already defined in Salesforce.
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/Centos/AlmaLinux/Rocky Linux
Ubuntu
- Download the quick installation script
sudo curl https://repository.veeam.com/yum/el/vbsf-install-script.sh --output ./vbsf-install-script.sh |
- Run the script
- 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/vbsf/userguide/deployment.html?ver=20.
Uninstalling Veeam Backup for Salesforce
- Uninstall the product package
RedHat/Oracle/Centos/AlmaLinux/Rocky Linux
Ubuntu
- 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 2.1.1 supports automated in-place upgrade from previous versions, which preserves all configuration and settings. Upgrading from any pre-release or Beta version is not supported.
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.
Use the following checklist to ensure that your infrastructure is ready for Veeam Backup for Salesforce upgrade.
- Make sure that management server meets minimal system requirements.
- Make sure that your PostgreSQL server meets minimal system requirements.
- Default file storage location has changed to
/opt/vbsf/data
. For existing installations, this setting will not be applied. 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.
- Salesforce API setting will be updated to the new supported version automatically. All other advanced settings will not be changed during the upgrade process.
- A new encryption key will be added to the installation folder. This product key encrypts all secrets in the database. Make sure that you do not lose this key, otherwise, the product will require reconfiguration.
- 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.
- Restore job drafts from version 1.0 for file restore jobs will become obsolete and must be deleted.
- The new
backend.domain
setting is automatically set to the default IP of the management server. The Azure AppRegistration Redirect URI endpoint list needs to be adjusted to list thebackend.domain
value.
To upgrade Veeam Backup for Salesforce, do the following:
- Disable backup policies
- Make sure there are no running backup policies
- Make sure there are no running restore jobs
- Perform the upgrade using Veeam Updater
- To perform upgrade manually with the Linux package manager, run the command:
RedHat/Oracle/Centos
Ubuntu
- You may consider manually moving backed-up files to the new location and changing the default file location setting in Advanced Settings.
- 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.
- In case Single Sign-On with Azure AD was configured, the configuration change is required on both the product and Azure AD side:
- In the product, log in with the local administrator account, go to Configuration > Advanced Settings and edit the
backend.domain
parameter to match the domain name of the management server. - In Azure, go to the App Registration > Authentication section and modify the Redirect URI to match the domain name of the management server.
- In the product, log in with the local administrator account, go to Configuration > Advanced Settings and edit the
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 per User that corresponds to an active Salesforce user with the Salesforce license type. 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.
Technical Documentation References
If you have any questions about Veeam Backup for AWS, you may use the following resources:
- Product webpage: https://www.veeam.com/backup-salesforce.html
- User guides: https://www.veeam.com/documentation-guides-datasheets.html
- Community forums: https://forums.veeam.com/
- Changelog: https://helpcenter.veeam.com/rn/veeam_backup_salesforce_2_1_changelog.html
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.