Salesforce Backup Considerations

Note This content relates to Salesforce Backup. Read about Backup & Recover in Own from Salesforce.

Salesforce Backup doesn’t support certain objects.

• Objects that the Bulk API doesn't support
• Records stored in big objects
• Standard objects that don’t contain the CreatedDate, LastModifiedDate, and SystemModstamp system fields, and the LoginDate field

  If you have all required permissions and access levels enabled for an object, but the backup log status shows NOT_VISIBLE, the object is likely missing one or more of these required fields.

• Light Application objects

Keep these other considerations in mind.

• When a record is updated, the original record ID is maintained. Only the changed fields are restored.
• When a record is deleted, a new record ID is created to restore that record.
• When restoring records, if Person Accounts is enabled in your org and a person account is related to a business account, the connective AccountContact relation record isn’t restored.
• If a custom object is part of a managed package that’s not site-wide, integration users must have the license for the object.
• Data is encrypted using TLS 1.3 or higher in transit and using AES-256 at rest.
• Backup and restore operations involve the integration user. If your backup policy includes fields encrypted with Classic Encryption, make sure that the integration user has the View Encrypted Data permission. If the View Encrypted Data permission isn't enabled, those fields’ contents aren’t accessible to the backup service. Their data isn’t backed up and can't be restored.
• Salesforce doesn't show the data consumption of security products to customers. To view your product's data consumption, contact Salesforce Support.