Datto Windows Agent: A Backup Is Currently in Progress

Topic

When you try to start a backup for a system protected by the Datto Windows Agent, you receive the error, "A backup is already in progress."

Environment

  • Datto Windows Agent

Description

The error can show as a curl error 400 like in the example below, or similarly.

CRITICAL BACKUP FAILURE: ABA1009 CURL ERROR:
HTTPS://x.x.x.x:25568/BACKUP: HTTP CODE: 400 (BAD REQUEST)
RESPONSE: 'A BACKUP IS CURRENTLY IN PROGRESS.' – BACKUP ATTEMPT 2 OF 2

This error occurs when the server thinks a backup is currently underway, thus preventing a new backup from starting. When it happens, you can see the issue in the agent logs.

Viewing the agent logs in the device UI

  1. Click Protect, and then click Show Backup Logs for the appropriate agent.

  1. Select Show Agent Logs from the expanded page.


  1. You will see output similar to the following:

Thu 10/08/17 9:57:08 am - Backup failed. Informing writers of unsuccessful backup.
Thu 10/08/17 9:57:08 am - Backup exception: Could not setup volume snapshot set.
Thu 10/08/17 9:57:08 am - Query snapshots: 0 existing snapshots.
Thu 10/08/17 9:57:08 am - Snapshot failed. Error: 21 - Could not datto configure snapshot set.
Thu 10/08/17 9:57:03 am - Snapshot - Type: VSS
Thu 10/08/17 9:57:03 am - Query snapshots: 0 existing snapshots.
Thu 10/08/17 9:56:55 am - A backup is currently in progress.
Thu 10/08/17 9:56:53 am - A backup is currently in progress.
Thu 10/08/17 9:55:23 am - Command run exited with code. 0
Thu 10/08/17 9:48:25 am - A backup is currently in progress.
Thu 10/08/17 9:48:23 am - A backup is currently in progress.
Thu 10/08/17 9:48:00 am - A backup is currently in progress.
Thu 10/08/17 9:47:57 am - A backup is currently in progress.
Thu 10/08/17 9:44:08 am - A backup is currently in progress.
Thu 10/08/17 9:44:06 am - A backup is currently in progress.

Resolution

Restarting the service can often resolve the issue. Follow the below steps on restarting the Datto Windows Agent service(s) based on the agent version below:

DWA 3.0 and newer

  1. Open a run window on the protected machine and go to services.msc
  2. Right-click on Datto Backup Agent Service and click Stop to stop the service.
  3. Right-click again on Datto Backup Agent Service and click Start to restart the service.

For DWA versions prior to 3.0

If you have an older version of DWA, we recommend updating if possible. Versions prior to 3.0 have two services that will need to be stopped, then restarted.

  1. Open a run window on the protected machine and go to services.msc
  2. Right-click on Datto Backup Agent Service and click Stop to stop the service.
  3. Right-click again on Datto Backup Agent Service and click Start to restart the service
  4. Right-click on Datto Provider and click Stop to stop the service.
  5. Right-click again on Datto Provider and click Start to restart the service.

NOTE  We recommend stopping then starting the service rather than just restarting, as using the Restart option may not always work reliably.

If the Issue Continues:

  • Stop the services above for the agent.
  • In File Explorer, browse to:
    C:\Windows\system32\config\systemprofile\AppData\Local\Datto\Datto Windows Agent\agent.sqlite
  • Rename the .sqlite file to agent.sqlite.old,
  • Restart the services
  • Run Repair Agent Communications from the Datto device UI (Protect > Configure Agent Settings > Repair Agent Communications) and attempt a backup.

If you have attempted all of the above-listed troubleshooting steps, but you are still unable to perform a backup, contact Datto Technical Support for assistance.