FAQs for Salesforce

Updated

Does the Salesforce requirement for multi-factor authentication have any effect on Metallic?

The Salesforce requirement to use multi-factor authentication for all Salesforce user interface logins has no effect on Metallic, if the following are true:

In Metallic, use OAUTH authentication for your Salesforce organizations.

What are the approximate number of API calls that are made for data protection?

Interface

API call details

Bulk API

The total number of objects that support the Bulk API interface *3.

For each object, there is a Bulk query request + Bulk status check + Bulk result fetch.

SOAP API

The total number of objects + an API call for each 2000 records for objects that do not support the Bulk interface.

SOAP query request + (SOAP query more request)

REST API

The total number of blob objects.

Rest file download request + (If failure, +1 * no of retries) Metadata API = 1

If the API calls for the Salesforce organization reach 80% of the maximum API calls allowed by Salesforce, the following event is generated: [NOTIFY_WARNING] Low API calls remaining [XX], total [XX].

Does the Metallic interface support the Salesforce production and sandbox orgs?

Yes.

How do I find my Salesforce Token?

For additional information about Salesforce tokens, go to Reset Your Security Token on the Salesforce help website.

Why do I see a different application size from the Salesforce Usage Report?

For most objects, Salesforce calculates the data usage by multiplying the record size (2 KB) by the number of records. The Metallic software uses the actual physical size of the object so you may see a different size from Salesforce. For more information, go to the Salesforce help website, What are the various record sizes.

What kind of permissions are needed to perform backups and restores?

For information on the permissions needed to perform backup operations and restore operations, see Salesforce User Permissions. The following use cases are covered:

  • Backing up encrypted data

  • Backing up knowledge articles

  • Backing up private chatter messages and direct messages

Can a user who has limited permissions perform backups and restores?

Best Practice: The Salesforce user who performs the backup operations and the restore operations has a system administrator profile.

If you cannot provide a user who has a system administrator profile, you can create a profile in Salesforce that contains individual permissions. For information on the individual permissions needed, see KB article CLD0014.

Does the Metallic software back up Salesforce big objects?

No, big objects are not supported.

Does the Metallic software skip any objects in the backup?

Yes. The Metallic software skips some objects because of Salesforce API restrictions. For information, see Salesforce Objects That Are Not Included in Backups.

If an object query fails, the Metallic software skips that object and provides an event. The Metallic software also skips objects that require filters on queries.

If an object does not have any data, the Metallic software skips that object.

Does Metallic support Converted Lead Record restores?

No. Metallic does not support Converted Lead Record restores.

Why are content files not fully downloaded?

There is a Salesforce API issue that causes files that have a size that is in the hundreds of MB to not fully download. Jobs that involve these files will display an event that shows 'DISK_WRITE_INTEGRITY_CHECK_FAILED’ or a similar message.

Why don't I see the files under the ContentDocument, ContentNote and ContentBody objects?

All these objects refer to the Salesforce CRM content and will have corresponding versions in the ContentVersion object. To avoid downloading duplicate content, all CRM content files are downloaded from the ContentVersion object and shown under Files > ContentVersion.

Are Full Org Restores Supported?

Yes. Although, due to complexity or nature of Salesforce, some objects and records may not restore successfully. Reasons such as API limitations, data integrity and complexity in hierarchical relationships, and automation processes that utilize triggers, flows, and rules can block records from being restored.

For more information about reasons for why objects and records do not restore successfully, see Troubleshooting General Salesforce Errors and Troubleshooting Salesforce Restore Operations.