Summary
Block backup fails during data transfer with aborted message
Symptoms
Backup logs shows the following error:Wed Sep 07 00:05:07 2016 SNBSVH_234J Task 13 has transfered 54 GB
Wed Sep 07 00:10:12 2016 SNBSVH_234J Task 13 has transfered 57.9 GB
Wed Sep 07 00:12:03 2016 SNBNCJ_103E Task 13 NDMP_LOG: id(0), type(NDMP_LOG_ERROR), text(process was aborted)
Wed Sep 07 00:12:03 2016 SNBSVH_969E Transfer backup(/vol/SV_CMNDBS01_02/[CMNDBS01-02]BEX_CMDBS01-02@{A0CABC40}) failed with exception: NDMPSessionException(0, transferBackup exception: <EXCEPTION CATEGORY="BEXEXCEPTION"><CODE>501</CODE></EXCEPTION>)
Wed Sep 07 00:12:03 2016 SNBSVH_245J Task 13 remaining retry count: 5
The system event logs at the time show an error in Volsnap:
9/7/2016,12:10:42 AM,BexWinCj,Information,Shell ,19,N/A,CMNDBS02,IRP_MN_SURPRISE_REMOVAL received for \Device\HarddiskVolumeShadowCopy21
9/7/2016,12:10:42 AM,VolSnap,Error,None,25,N/A,CMNDBS02,The shadow copies of volume E: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
9/6/2016,10:30:55 PM,BexWinCj,Information,Shell ,3,N/A,CMNDBS01,Journal bitmap succesfully flushed for the Volume \Device\HarddiskVolume2.
Resolution
| The solution is to configure VSS to write the shadow copies of the problem drive to a different drive which has more available space and less load during the backup. The ideal situation would be to have a separate drive dedicated to shadow copies that is not being backed up and is also not the drive containing the paging file. If this is not possible, specifying a separate drive that contains the paging file is typically still better than storing the shadow copies on the drive being backed up. |