Backup Job Types

When creating a backup policy, you configure the default backup schedule according to which Veeam Backup for Salesforce will back up the Salesforce organization. You can also enable custom schedules in the backup policy settings to additionally protect specific groups of objects. The configured schedules are further used by the product to create backup jobs of 3 different types:

• Data job — this job type is used to back up object data of the protected Salesforce organization. Data jobs run according to each configured backup schedule (both custom and default). To learn how to configure backup schedules, see Creating Backup Policies.
• Metadata job — this job type is used to back up metadata of the protected Salesforce organization. Metadata jobs run according to default backup schedules only.
• File job — this job type is used to back up files and attachments of the protected Salesforce organization. File jobs run according to default backup schedules and only if you enable backup of files and attachments in backup policy settings. To learn how to enable this functionality, see Creating Backup Policies.

Additionally, Veeam Backup for Salesforce periodically runs the following types of backup jobs:

• Validate job — this job type is used to compare backed-up data in the product database with data currently stored in Salesforce, that is, to detect hard-deleted items and mark them as deleted in the product database. Validate jobs automatically run weekly at the same time for each enabled backup policy. To learn how to enable backup policies, see Disabling and Enabling Backup Policies.
• Reload job — this job type is used to upload missing record fields and files to PostgreSQL databases and file repositories. Reload jobs are launched manually with no regard to backup schedules. To learn how to run a reload job, see Reloading Fields and Files.
• Encryption job — this job type is used to encrypt record fields and files of the protected Salesforce organization. Encryption jobs run according to the configured encryption settings — but only for those backup policies that have already been used to protect fields and files (meaning these items already have backups) and that previously had the encryption functionality disabled.

If you disable encryption for a backup policy, the next run of the encryption job will decrypt data that has been previously encrypted. To learn how to disable encryption, see Editing Backup Policies.