Considerations and Limitations

When you plan your deployment of Veeam Backup for Salesforce, keep in mind the following limitations and considerations.

Supported Salesforce Offerings

  • Salesforce provides multiple offerings that are built on one Salesforce Platform — Sales Cloud, Service Cloud, Financial Cloud, Health Cloud and Education. Veeam Backup for Salesforce 3.0 supports backup of all data and objects available on the Salesforce Platform if these resources can be retrieved using the Salesforce API version 60 and earlier. This means that if an object or data cannot be obtained using standard Salesforce API requests, backup of these objects is not supported.

Salesforce Marketing Cloud is built on another platform and is not protected by the product.

  • Both Salesforce Classic and Lightning Experience interfaces are supported.
  • Salesforce sandbox organizations as well as Salesforce production organizations can be protected by Veeam Backup for Salesforce.
  • All Salesforce API-enabled editions are supported: Developer, Enterprise, Performance, Professional (API access must be enabled), Unlimited.

Backup and Restore

Important

For fields that already have backups, it is recommended that you do not change their types in Salesforce since this may cause backup failures.

Time Zone

The product Web UI uses the time zone of a machine from which you access Veeam Backup for Salesforce. However, the management server and databases use the UTC time zone for all operations.

Salesforce User

  • Set the English language in the locale and account language settings for the user in Salesforce. It is required for error handler to work properly.
  • Make sure that you have assigned the user all the required permissions. Note that if a Salesforce user of the protected organization does not have permissions required to back up specific files or object fields, Veeam Backup for Salesforce will not be able able to back up these files or fields. To work around the issue, reload object fields or files as described in section Reloading Fields and Files.  

Page updated 10/21/2024

Page content applies to build 3.0.0.1769