Use the Abort Backup feature when you want to stop a running Dynamics backup. If you discover errors during a backup or want to modify 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 the user does not want backup to proceed before this data error is fixed.
- The running backup may slow down the execution of other jobs running concurrently, such as seeding and anonymization jobs, whose execution is currently more critical to the user.
- When creating a new service, a backup will automatically run. In some cases, users would like to modify the default backup options by adding optimization and/or exclusions before executing the first backup. Backing up files and attachments in the first backup takes longer than on subsequent backups.
- The user performed critical changes on their instance after the backup has already started to run and wants to run a more updated backup without having to wait for the current backup to complete.
- An aborted backup will change the service status from Success (Green) to Warning (Yellow) status. Once another backup completes, the status will change 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.