Performing Salesforce Full Backups

You can perform a full backup of the Salesforce data.

A full backup is the most comprehensive backup and is the baseline for incremental backups. For more information on full backups, see Full Backups.

For information on objects that the backup does not include, see Salesforce Objects That Are Not Included in Backups.

Before You Begin

• Verify that the Salesforce user who performs the backup operations has the required permissions. For a list of the required permissions, see Salesforce User Permissions.

• To include the metadata in the backup, configure the subclient to include the metadata. For more information, see Backing Up Salesforce Metadata.

• Plan your advanced settings. The options are described for the following advanced settings:

  • Job Priorities and Priority Precedence - Online Help - Startup

  • Job Controller - Online Help - Job Retry

  • Advanced Backup/Archive Options (Media)

  • Advanced Backup Options (Data Path)

  • Vault Tracker Feature - Online Help

  • Alerts and Notifications - Online Help

Procedure

1. From the CommCell Browser, expand Client Computers > client > Cloud Apps > instance.

2. Right-click the subclient, and then click Backup.

3. The Backup Options dialog box appears.

4. Select the backup type and job initiation:

   1. In the Backup Type section, select Full.

   2. In the Job Initiation section, specify whether to run the backup now or if it will be scheduled.

      For information about configuring a backup schedule, see Schedule Backups.

5. Optional: To set advanced backup options, click Advanced.

6. Click OK.

Result

Do not change the arrangement of the text on this page. This embed is varianted and the formatting on the parent pages in the variants will not be what you expect.

To avoid exceeding the Salesforce API size limit, a backup job runs until the number of files backed up reaches over 50 percent of the total API calls allowed for the day. Then, the backup job is suspended, but is automatically resumed the next day. This behavior continues until all of the files in the job are backed up.

Events are generated in the following cases:

• An object fails or skips because of one of the following reasons:

  • The object is restricted by the Salesforce API.

  • The object takes too much time to back up and produces a QUERY_TIMEOUT error, or a similar error.

  • The object requires one or more filters on the query.

  • The object does not have any data to backup.

• The file does not download because the file does not exist at the time of the download.

• The file is partially downloaded due to the Salesforce API size limit or due to file corruption, and so on.

Related Topics

Job Controller

Job History