#Configure Backup Settings

To configure backup settings for data backup, click the More commands button in the upper-right corner of the organization tile on the Backup page, and then click Configure backup settings from the drop-down list. If you have audit log backup enabled for the organization, select Data backup. Then you can turn on/off the toggle next to the organization name to enable/disable the data backup for the organization. Once the backup is enabled, you can configure the backup scope and backup frequency of the organization.

*Note: If a backup job is already running for the organization, the scheduled backup job will be automatically skipped.

#Configure the Backup Scope

To configure the backup scope, complete the following steps:

1. In the Backup scope section under the Backup data tab, turn on/off the toggles to configure if you want to back up the *Feed (for example: Account Feed; Contact Feed; Case Feed) and *Share (for example: Account Share; Contact Share; Case Share) objects of the organization. Note that if you back up these objects, the backup performance may be affected, and they will take up extra storage space.

2. Turn on/off the toggle to configure if you want to back up event logs. After turning on the toggle, you can select to back up Daily event logs or Hourly event logs.

3. Turn on the toggle to Exclude specific object types from backup and select the objects you do not want to protect from the Objects drop-down list.

4. Turn on the toggle to Exclude specific metadata types from backup and select the metadata types you do not want to protect from the Metadata type drop-down list.

5. Click Save to save the configurations, or click Cancel to close the panel without saving any changes.

#Configure the Backup Frequency

To configure the backup frequency, complete the following steps:

1. In the Frequency section under the Backup data tab, select a number from the How many backup jobs would you like to run per day? drop-down list. AvePoint Cloud Backup for Salesforce® will automatically provide the job schedule according to the frequency you selected.

   You can change the start time for the first backup job. The rest of the schedules will be automatically calculated and displayed.

2. Click Save to save the configurations, or click Cancel to close the panel without saving any changes.

#Enable Continuous Data Protection

If you want to retrieve data more frequently for mission-critical and rapidly-changing objects, you can contact the AvePoint support team to enable the Continuous data protection for the organization, and complete the steps below:

1. Click Continuous data protection tab in the Configure data backup settings panel.

2. Turn on the Enable continuous data protection toggle, and configure the following settings:

   • Objects – Select the objects from the drop-down list.

     Note that you must ensure that Change Data Capture is enabled for the objects you selected. You can navigate to Setup > Integrations > Change Data Capture in Salesforce to add the required objects.

   • When would you like to start the first job? – Select the time you want to start the first job.

   • Interval – The default interval is set to 1 hour. If you want to update the interval, contact AvePoint support.

3. Once completed, click Save. The continuous data protection job will start collecting event logs after a full or incremental backup, based on the configured start time and interval.

#Limitations

The continuous data protection function has the following limitations:

• Salesforce has a limitation on collecting the event logs. For the maximum number of Change Data Capture allocations by different licenses type, refer to .

• Files objects, such as ContentDocument, are not supported for continuous data protection. Refer to for a list of supported objects.

• Salesforce may generate , which cannot log record changes, instead of Change event resulting from some errors. Detected gap events will trigger automatic reprocessing of affected records within the current continuous data protection job, which may consume additional APIs.