Veeam Backup for Salesforce 3.1.1 Changelog

[3.1.1] - 2025-02-12

Added

Implemented a process to monitor the initiation of jobs, allowing for the termination of any job that fails to start within 5 minutes.

Fixed

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.

[3.1.0] - 2024-12-10

Fixed

Ability to run multiple archiving jobs one after another without having to perform backups between them to avoid selecting the same records for archiving.

[3.1.0] - 2024-11-27

Added

Data masking templates for sandbox seeding.
Data masking patterns, regional settings and default suggested PII fields.
Metadata reload action to start a full backup of metadata.
Support of ContentDocumentLink reload as part of the files reload action.
Export records to CSV file during custom child hierarchy restore configuration.
Restore of contact record hierarchy is supported for Person Accounts.
Support for cyclic relationships during hierarchy restore.
Display of Salesforce data and file storage consumption from the organization.

Fixed

Restore of Tasks and Events to and organization with enabled “Shared Activities”.
Field value override is supported to multi-picklist fields.
Retention policy supports custom objects for the organization that was added 2nd, 3rd and so on, to the product.
Handling of formula bytes size limit during automation disable operation.
Quote Document restore does not result with duplicate ContentDocument.
Retention scheduler will start based on server time zone.
Support of New Zealand time zone for schedules.

[3.0.0] - 2024-09-18

Added

Salesforce API v60.0 is supported.
New data archival policies to archive data and files from Salesforce, and reduce storage consumption. Requires a Salesforce Advanced license type.
Data and files encryption on the fly during backup process. Encryption job to encrypt/decrypt existing data.
Built-in encryption key or AWS key management service (KMS) for data encryption.
Support for text (encrypted) Salesforce field type.
Support for private chatter messages.
Support for backup of embedded images in rich text Salesforce fields.
Optimized job scheduler that postpones the job start in case of low available memory.
Individually started and stopped backup sessions for data, files, and metadata backup.
Data reload action to start a full backup for an object or a set of fields which have inconsistent value due to formula change.
Improved backup engine for slow Salesforce connections.
30% faster data backup speed without enabled data encryption.
45% decrease in API consumption during backup.
Improved user permissions verification.
Granular object metadata restore for fields, validation rules and list views. Requires a new metadata backup or an object metadata change.
Full object data restore to a specific point in time.
Restore of existing Salesforce profiles to a previous version.
Enhanced hierarchy restore configuration.
Updated layout for record version and metadata version comparison.
Restore job allows to configure fields mapping for any object in the hierarchy, export and import the mapping as a CSV file.
Support for FeedItem attachments restore, excluding embedded images.
Restore session CSV export of ID mappings for all created and updated objects.
Restore session summary view and counts of restored records.
Restore will use existing standard pricebooks when restoring products to another Salesforce org.
Restore to another Salesforce organization will replace the record owner with the backup user, in case the original user cannot be located.
Export to CSV ID mappings of all records created by all restore jobs executed for the organization.
Revamped restore engine.
Data change alerts based on actual number of records and a percentage of records created, modified or deleted between backup sessions.
JSON-formatted audit log for SIEM integration.
All data search requests are logged in the audit log.
Internet proxy support.
PostgreSQL 15.8 is the default version during installation.
RockyLinux and AlmaLinux are supported.
Salesforce Platform users are now also counted towards the licensed users.

Fixed

Salesforce Flows are no longer skipped during incremental backup if required permissions provided.
Backup of sandboxes is not limited to licensed user limit, as long as there is at least one valid production org licensed.
SMTP server password length is extended to 255.
Notifications via proxy are supported.
Salesforce connection status is showing correct value in case of connection issues.
Old record ID can be mapped to another field.

[2.1.0] - 2023-11-27

Added

Server configuration script to verify and install potentially missing utilities.
Optimized Salesforce API requests.
Advanced settings to control default parameters for the records hierarchy restore.

Fixed

Removed functionality to set arbitrary ID mappings. You can only view and remove ID mappings now.
Default values for advanced settings are now correctly updated during the product update. This does not affect any user customizations.
Fields restore wizard is showing correct field values for the selected record version.
SMPT server can be configured without authentication and with only self-signed certificate.
Salesforce token is refreshed correctly with multiple Salesforce orgs on the same installation.

[2.0.0] - 2023-08-29

Added

Extending support of the Salesforce platform, including Salesforce Government and Education Clouds, Field Service, Person Accounts, and managed packages.
Sandbox Seeding. The new restore wizard allows you to specify the source and the target Salesforce Org, and seed data to a new sandbox with several clicks. Fields override option helps to replace sensitive field values with a predefined dummy value before insert.
Salesforce is a new identity provider that is available for single sign-on configuration.
Browse data view is a new fast way to investigate the backup on a particular date.
Enhanced domains support is added to backup policy and connected app settings.
Audit log is created for all sensitive operations.
Salesforce API v57 is supported.
Modern Authentication for Microsoft 365 email alerts has been implemented.
Localization for the management web UI has been added. Japanese language is now available.
Ubuntu distribution for versions 20.04 LTS and 22.04 LTS is now supported.
Smaller memory footprint allows protecting more Salesforce orgs with one deployment.
Salesforce SSO allows adding users of any Salesforce instance and granting them restore operator roles only to specific companies and Salesforce instances. Administrators can also limit single sign-on to a specific Salesforce domain.
Set alternate keys for objects to avoid running into duplication errors during restores.
Set object IDs mapping manually between Salesforce ID in the backup and the target Salesforce org.
Hierarchy restore has more controls over what needs to be updated and when the traversing of the hierarchy tree needs to stop.
Metadata comparison and download for components with multiple files is now presented for all files included in the component.
Predefined filters are configured for certain objects, that cannot be restored to Salesforce.
Data filter validations and usability have been improved in restore wizards and browse page, when you need to specify several picklist values, or have a list of Salesforce IDs to filter on.
Billions of records can be protected with the refined backup engine. Backup performance and Bulk API consumption have been improved. Administrators of large Salesforce deployments can distribute objects within the backup policy to several schedules and achieve the target recovery point objectives.
Error handling and reporting have been improved. In file backup jobs, reporting of problematic IDs is added for cases when files cannot be retrieved from Salesforce and interaction with Salesforce support is required. Such IDs will be automatically added to exclusion lists after several backup cycles.
Validation data jobs will identify and mark any hard-deleted records, and create future tasks to re-process any discrepancies for the backed up date intervals.
File backup and restore extended for additional content types such as FeedAttachment, ContentNote and ServiceReport.
File backup permissions check will help administrators to validate missing permission ‘Query All Files’ which silently prevents backing up all files on the Salesforce org.
Backup schedules now include time zones and backup window setting.
Advanced Settings provide default values that administrators can override to custom values, and revert to defaults later.
Salesforce API version is now a configurable parameter within the advanced application settings. Administrators at their own discretion can decide on hopping to a newer API version at any time without waiting for Veeam to release a product update.
Memory settings for backup, restore and backend services can be customized separately. Depending on the profile of the protected environment and restored data, higher initial or maximum parameters can be set.
Backup location on the file system for all files and metadata can be customized.
Log retention settings are now configurable from the web user interface. Administrators can customize different retention timeframes for restore, backup or management server log files.
Requirement for a specific locale version on the management server.
Security enhancements.

Fixed

Salesforce API version support.
Silently missing files due to absent ‘Query All Files’ permission.
Tables and fields with names longer than 63 characters could not be created in PostgreSQL.
Large files restore for files up to 2GB.
New field types: custom address, custom geolocation.

[1.0.1] - 2023-02-14

Fixed

Incremental backup cycle may process more records than required.
Reports and dashboards metadata needs to be modified before it can be restored.
Database schema changes for long object names.
Backup session log to support billions of fetched records.

[1.0.0] - 2022-10-27

Added

Licensing. The product is licensed per User which is an active Salesforce User license reported by the Salesforce platform. 100% of active Salesforce Users must be licensed in order to back up a Salesforce org. Veeam Backup for Salesforce is currently using a stand-alone license and not a part of the Veeam Universal License.
Community edition license. The Community Edition license for 50 users is built into the product. It allows protecting a Salesforce organization with up to 50 active users. That means if you have 2 Salesforce orgs with 20 Users, you can protect both with one Community edition license.
Paid subscription licenses can be installed into the product. During installation, the license must be activated against Veeam Licensing Servers that will validate, meter and update the license as needed.
Evaluation and NFR licenses can be installed into the product. During installation, the license must be activated against Veeam Licensing Servers that will validate, meter and update the license as needed.
License usage reporting is enforced in the product. This is a requirement especially for paid licenses that must be reported back to Salesforce company.
Flexible backup policies to protect Salesforce data, metadata and files. Policies include main schedule for data, files and metadata backup, as well as additional custom schedules per Salesforce object. Schedules are defined individually for each protected Salesforce Org.
First configuration wizard to simplify the built-in user creation, DB connection and set up of the first backup policy. The first policy is created without file backup enabled.
Incremental Changes. After the initial full data sync, the backup policy will only collect incremental changes and this allows the backup to complete much faster.
Optimal API Usage. Backup service is smart enough to detect when to use bulk API vs rest API or SOAP. Depending on type of the object and the increment size, the optimal API will be used.
Custom schedules per object. You can choose to protect objects at a different schedule than the main schedule of the backup policy, or exclude objects from backup completely.
Built-in schedules: Hourly, Daily and Weekly. Schedules start at the top of the hour on the defined date/time.
Create own schedules that can run once or recurrently at defined minute, hour, day, days of week.
Detection of new fields for existing objects. New fields can be automatically protected by the policy, when enabled.
Detection of new objects. New objects can be automatically protected by the policy according to the main schedule, when enabled.
Data retention jobs for objects, attachments, files and content versions. Old versions or deleted items will be removed from the disk and database by the scheduled daily job.
API usage threshold. Avoid hitting the bulk API limit or the daily API limit by specifying the maximum API consumption threshold in percent (%) of total available limit for the org.
Running backup policies can be stopped gracefully or forcefully. Graceful stop will wait for all started batches and objects to complete.
Restore records, files and metadata. Easy-to-use wizard to browse and restore data back to the original Salesforce organization.
Restore field values. Mass restore selected fields for thousands of records.
Data filtering in restore wizards. Data search filters will help to pinpoint the records and select them for restore. You can cherry-pick records or select all that match your filters. If you have a csv list with record IDs, you can specify the values as a filtering condition.
Restore records hierarchy. Drill down and select specific child hierarchy branches and at a depth you need to restore, or leave it undefined and restore the entire records tree as it was in the corresponding backup. You can even restore parent records and relationships.
Restore versions. During restore, you can choose the version you would like to restore from. Each record in your restore job can have its own restore point and you are able to visually see the differences between record versions to make sure you are selecting the correct one for the restore.
Restore profiles. Salesforce user profiles are not described by a single metadata type but contain a collection of settings across the configuration - tab visibility, custom object access, field access, etc. Veeam Backup for Salesforce greatly simplifies protection of profiles by creating a synthesized backup package that you can restore with a few clicks. As you restore profiles, this package is deployed and all dependent elements are restored.
Restore records with attachments and content documents in one job. In restore wizard you can specify additional filters for the files that need to be excluded from the restore.
Safeguard restores with limits. Use advanced settings to limit how many records can be submitted for a restore job.
Overwrite field values on restore. Define custom values or use the pattern %value% to overwrite what is being restored to Salesforce.
Map fields on restore. In that mode the value from the field from the backup will be written to the specified field in Salesforce.
Overwrite or skip values. You can instruct the restore job to skip records with IDs that exist in Salesforce or overwrite those records with backup data. Additional option is to overwrite data with NULLs if this is the value in the backup.
Export to CSV record details for restored objects and specified hierarchy.
Salesforce organizations. To protect multiple Salesforce organizations, simply add and configure new backup policies.
Companies. Salesforce organizations are added to Companies which then can be used to segregate users, roles, alerts and views inside the application.
Users and roles. Initially there is only one user for the application, the built-in admin user. To add more users and leverage different application roles, you need to configure the Azure AD connection, enable the single sing-on with Azure AD and provision users or groups to the application roles. There are 4 roles available - Administrator, Backup Operator, Restore Operator and Viewer. You can assign those roles per Company or Salesforce organization.
Single Sign-on. You can integrate with Azure Active Directory via the App Registration and provision users and groups to application roles. This will enable the single sign-on with Azure AD.
Email and Slack alerts can be sent on backup policy status, restore policy status, license check, file repository storage space and connection status for Salesforce organizations and databases. Backup policy and restore job alerts are configured for selected user roles and can be limited to a number of Salesforce organizations, or companies, or sent to all roles in all organizations.
Data accessibility. The data is stored in open formats - the metadata and binary data is stored on the disk as files, while Salesforce records are stored in a PostgreSQL database. You can always query this data, make replicas for other use cases, implement the backup copy jobs and immutable storage of this data with help of Veeam Backup & Replication.
Connected app tokens change is possible. Changing the tokens will render all existing connections to Salesforce invalid. Manual re-authorization will be required for each connected Salesforce org.
Changing backup database connection is limited to changing the username and password only.
Changing configuration database connection is limited to changing the username and password only.
Logs for a specified timeframe can be downloaded in About section.
Per job run logs can be downloaded at the session details screen.
Built-in administrator password reset script is located in the application folder.