Video Screencast Help

Flashbackup failing with system call failed 11

Created: 17 Mar 2013 • Updated: 25 Mar 2013 | 2 comments
This issue has been solved. See solution.


We are facing issue regarding flashbackup.

Flashbackup has faling with status 11 system call failed.

03/18/2013 06:58:56 - Error bpbrm (pid=59604) from client hbcoldnew2: ERR - FIML_start on <ntfs>\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy429 failed VFM error = 2059
03/18/2013 06:59:04 - Error bpbrm (pid=59604) could not send server status message
03/18/2013 07:03:43 - end writing; write time: 5:27:09
system call failed (11)


Master :- Sun OS 10

Client/Media :- Windows 2003/08

NBU :- 6.5.4.



Operating Systems:

Comments 2 CommentsJump to latest comment

RamNagalla's picture


check this below tech note, if it relates to your issue..

 VFM error = 2059


The root cause of this problem is that VSS ran in to an IO limit of the volume.  It cannot grow the shadow copy fast enough to keep up with the backup.

It is possible to configure VSS settings on Windows to have the shadow copy (containing the snapshot) created on a different volume than the one you want to backup. 

Allocate a very fast lun to the server as the temp area to host the VSS shadow copy.  For your 2 TB backup, I would suggest using a 500 GB volume until you can find out the consistent amount of space the shadow copy requires during backups.