If you discover errors during a Salesforce backup or want to modify the default options before the first backup is completed, you can stop a running backup.
The common use cases for aborting a running backup include the following:
- An error in production data was discovered, and you don't want backup to proceed before this data error is fixed.
- The running backup slows down the execution of other jobs running concurrently, such as seeding and anonymization jobs, whose execution is more critical.
- When you create a new service, a backup automatically runs. In some cases, you want to modify the default backup options by optimizing the backup or adding exclusions before executing the first backup. Note that backing up files and attachments in the first backup takes longer than on subsequent backups.
- You performed critical changes on your instance after the backup started to run, and you want to run a more updated backup without having to wait for the current backup to complete.
An aborted backup changes the service status from Success (Green) to Warning (Yellow). After another backup completes, the status changes to Success (Green).
Note Only a Master Admin or a Business Unit Admin can abort backups. During the last stages of
the backup, it cannot be aborted.
- Abort a Running Backup in Backup & Recover for Salesforce
Stop a running Salesforce backup to fix an error in production data, to modify default backup options, or if the backup process slows down other critical jobs.