Skip to main content
Druva Documentation

Backup job stuck at 0 percent due to Delayed write failed or Disk is full

 

Problem description

This article applies to the File server, NAS, SQL, and Hyper-V backups.  A backup job might get stuck at 0% with the following errors:

  • Delayed write failed
  • Disk is full

Cause

This error occurs in the following cases:

  • The backup crosses it’s queued phase and is in the running state.
  • Disk space is unavailable on the Windows drives.

As there is no space for the OS to operate, you might get File system errors while writing data to a disk.

Traceback

  1. Download the Phoenix Logs.
  2. Extract the logs. Access the PhoenixScanner_<Drive letter>.log to determine if the following excerpt is present in the log.
    • Phoenix log shows 
      • level=error ts=2019-05-21T13:07:28.6022888-04:00 filename=statemap_helper.go:222 message="Error inserting into smap"
      • level=error ts=2019-05-21T13:07:28.605289-04:00 stack="database or disk is full\\ngoroutine 152 [running]:\nruntime/debug.Stack(0xc005fb30a0, 0xc005f5f6e0
    • Event Viewer shows
      • Event ID: 50
      • Description: {Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere

Resolution

  1. Free up sufficient space on the Windows Drives. 

    Note: Windows recommends you to leave a minimum of 7-10% free space on each drive so that Windows can defragment them.

  2. Stop backups for the server until space is created.
    1. Disable backups for the backup sets from the Phoenix Management Console. Or
    2. Stop the Druva Phoenix service from the server for which backup failed.