Skip to main content
Druva Documentation

Phoenix backup fails with PHOENIX54 error

This article applies to:

  • OS: WS 2008 R2, WS 2012/R2, WS 2016
  • Product edition: Phoenix

Problem description

File server backup fails with error PHOENIX54. The error is logged in the backup job logs.

Cause

Insufficient disk space on the respective drive to store shadow copies.

Traceback

Phoenix logs:

{snippet}
[2018-10-10 03:35:19,740] [DEBUG] SyncFile: reading Test/datafileset/backupdocument.BKP at offset: 2283798528, readsz: 524288, doneoff: 2159542272, uploaded = 2265776128
[2018-10-10 03:35:19,740] [ERROR] Could not fetch snapshot status. Vss Error: GetSnapshotProperties hr = 0x80042308L
....
..
[2018-10-10 03:37:00,937] [ERROR] Backup failed for share:X file:Test/datafileset/backupdocument.BKP  with error:Could not fetch status. (#100000036)
[2018-10-10 03:37:00,937] [ERROR] SyncFile had an exception. Calling file error helper
[2018-10-10 03:37:00,937] [ERROR] Error <class 'inSyncLib.inSyncError.SyncError'>:Could not fetch status. (#100000036). Traceback -Traceback (most recent call last):
File "roboSyncer.pyc", line 2146, in __syncfile
File "roboSyncer.pyc", line 1082, in sync
File "roboSyncer.pyc", line 1568, in dedupesync
File "roboSyncer.pyc", line 1593, in __dedupesync
File "roboSyncer.pyc", line 975, in readfile
File "roboSyncer.pyc", line 983, in doreadfile_trysnapshot
File "roboSyncer.pyc", line 1009, in doreadfile
File "roboSnapshot\roboSnapshot.pyc", line 597, in Status
SyncError: Could not fetch status. (#100000036)
{snippet}

Windows event logs:

Log Name: System
Source: volsnap
Date: 10/18/2018 3:06:27 PM
Event ID: 24
Task Category: None
Level: Warning
Description:
There was insufficient disk space on volume X: to grow the shadow copy storage for shadow copies of X:. As a result of this failure all shadow copies of volume X: are at risk of being deleted.

Log Name: System
Source: volsnap
Date: 10/18/2018 3:06:34 PM
Event ID: 35
Task Category: None
Level: Error
Description:
The shadow copies of volume X: were aborted because the shadow copy storage failed to grow.

Resolution

Perform the following steps from an elevated command prompt. Replace the drive letter in from the above 

  1. Delete old shadow copies from the concerned drive. 

    vssadmin Delete Shadows /All
  2. Increase the storage space for shadow copy for the concerned drive.

    vssadmin resize shadowstorage /for=X: /on=X: /maxsize=30%
  3. Redirect the shadow copies to another drive that has sufficient free space.

    vssadmin add shadowstorage /for=X: /on=X: /maxsize=30%

Replace the drive letter from the above commands as per the concerned drive in the environment.

Verification

Initiate a manual backup and verify whether it completes successfully. 

See also

For more information on VSS command, please refer Microsoft article  Vssadmin.