Release Information for Veeam Backup for Salesforce 3 Cumulative Patches

Please confirm that you are running Veeam Backup for Salesforce 3.1 (build 3.1.1.2714) or earlier before upgrading. You can find the currently installed build number in the Configuration > About section.

After the upgrade, the Veeam Backup for Salesforce build number will be 3.1.2.3133.

Veeam Backup for Salesforce 3.1.2 (3.1.2.3133)

This release includes the following features and improvements:

• Support for Salesforce API version 63.0.
• PostgreSQL 15.11 is set as the default version during installation.
• Support for restoring activated Contract and Order records.
• Logic was added to allow the restoration of records with inactive parent BusinessHours.
• The case sensitivity of an alternative key configured for record restore is now defined based on the case sensitivity of the corresponding field in Salesforce.
• Rules for searching existing records by alternative key have been updated to allow a non-unique “DeveloperName” value for the "RecordType" object.
• The default alternative key for User record restore has been changed to the Username field.
• Option to deactivate login using local admin credentials if SSO login is enabled.
• ContentDocumentLink was not restored during sObject record restore if the corresponding ContentDocument existed in the target org.
• Metadata restore: The preview of the Apex class displayed only the “cls-meta.xml” file content, not the “.cls” file.
• PriceBookEntry records could be duplicated during restore if several Product2 records of the same Order referenced it.
• The product attempted to update the OwnerID of a record with a null value if the User creation failed during restore to another Org.
• Access to smtp.office365.com is now allowed for email notification configuration.
• An out-of-memory error could occur when upgrading the product with a large git repository from version 2.x to 3.x.
• An unmanaged trigger was not deactivated during restoration if a space character was missing between the list of triggering events and the trigger body.
• Permissions validation in records restore functionality was not working for the objects "Pricebook2" and "PermissionSetTabSettings".
• Backup of Professional Orgs failed due to the required "Author Apex" permission, which is unavailable in such Orgs.

Veeam Backup for Salesforce 3.1.1 (3.1.1.2714)

This release includes the following features and improvements:

• Implemented a process to monitor the initiation of jobs, allowing for the termination of any job that fails to start within 5 minutes.
• Resolved an issue where the retention job erroneously removed record versions based on the date of the initial backup, rather than the date of subsequent changes. Which resulted in fewer available restore points.
• Corrected a problem where the backup job did not display an error message and remained in the "Starting" status when it failed to create a folder in the file storage.
• Fixed a failure in metadata backup for Salesforce Professional Edition with the API enabled, which occurred while attempting to back up permissions for a non-existent field.
• Addressed an issue where the file backup failed during the attempt to download an embedded image due to a broken link.
• Fixed a problem where after adding the missing permissions to read an object, the backup still could not access the object because the metadata was not updated on the product side.
• Identified and resolved conflicting indexes caused by migration in the configuration database.
• Restore of AccountContactRelation record for organizations that allow a contact to be related to multiple accounts.

Veeam Backup for Salesforce 3.1 P20241210 (3.1.0.2378)

This release includes the following features and improvements:

• Ability to run multiple archiving jobs one after another without having to perform backups between them to avoid selecting the same records for archiving.
• Updated PostgreSQL version included in the setup by default to 15.10.

Veeam Backup for Salesforce 3.1 (3.1.0.2298)

This release includes the following features and improvements:

• Data masking feature that empowers users to safeguard sensitive and personally identifiable information when restoring data to a sandbox
• Metadata reload job to start a full backup of metadata
• Support of child hierarchy restore for contacts of Salesforce organization with enabled «Person Accounts».
• Other improvements in backup, restore, data archival, and usability