Status 11: System call failed

Article:TECH29809  |  Created: 2005-01-24  |  Updated: 2013-10-23  |  Article URL http://www.symantec.com/docs/TECH29809
Article Type
Technical Solution

Product(s)

Environment

Issue



Status 11: System call failed

Error



<4> V_VSP_CheckForError: INF - fpVSP_GetVolumeInformation.Exception (\\?\P36:): 112
<2> tar_base::V_vTarMsgW: ERR - Snapshot Error:0x00000070 (WIN32 112: There is not enough space on the disk. )
<2> tar_base::V_vTarMsgW: INF - EXIT STATUS 11: system call failed

Solution



Overview:  The backup failed because the server received a disk full error.  

Troubleshooting:
Please follow all steps within the VERITAS NetBackup (tm) Troubleshooting Guide or the NetBackup Troubleshooter within the Activity Monitor for this status code before continuing.

Please confirm hardware and software compatibility before continuing. A list of compatible hardware and software may be obtained within the NetBackup Release Notes or on the VERITAS Support Web site.

If the above does not resolve the issue, please continue.

1.  Status code 155 is caused by full disk condition.

Please look for the following log messages:

Master Log Files:  

All Log Entries report:
server01 server01 Error 13995 Backup from client server01: ERR - VSP Error:0x00000070 (WIN32 112: There is not enough space on the disk. )
server01 server01 Error 13995 Backup from client server01:EXIT STATUS 11: system call failed

Media Server Log Files:

Client Log Files:

bpbkar:
6:07:16.533 PM: [3944.5496] <2> tar_base::V_vTarMsgW: ERR - failure reading file: C:\Inetpub\wwwroot\projects\over_short\archive\040315\206.txt (WIN32 5: Access is denied. )
6:07:17.002 PM: [3944.5496] <4> V_VSP_CheckForError: INF - Error Checking for \\?\P36:
6:07:17.002 PM: [3944.5496] <4> V_VSP_CheckForError: INF - fpVSP_GetVolumeInformation.Exception (\\?\P36:): 112
6:07:17.002 PM: [3944.5496] <2> tar_base::V_vTarMsgW: ERR - Snapshot Error:0x00000070 (WIN32 112: There is not enough space on the disk. )
6:07:17.002 PM: [3944.5496] <4> V_VSP_DestroySnapshot: INF - SSM Request: 2 0 0 0
6:07:20.549 PM: [3944.5496] <4> V_VSP_DestroySnapshot: INF - SSM Reply: 0
6:07:20.549 PM: [3944.5496] <2> tar_base::V_vTarMsgW: ERR - Snapshot error while reading file: C:\Inetpub\wwwroot\projects\over_short\archive\040315\206.txt
6:07:20.549 PM: [3944.5496] <2> tar_base::V_vTarMsgW: FTL - Backup operation aborted!
6:07:20.565 PM: [3944.5496] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 11: system call failed

Resolution:

1.  Disable VERITAS Snapshot Provider on client

Configure using the NetBackup Administration Console:

1.  Open the NetBackup Administration Console
2.  Expand Host Properties and highlight Clients
3.  Double-click on the client name in the pane on the right-hand side of the console
4.  Select VSP and clear the Enable VSP during backups check box (Figure 1)

Figure 1
 

2. Status 11 can occur if there is a lack of free space on the client
Verify all drives on the client system have a significant amount of free space for the VERITAS Snapshot Provider cache files to generate.

3. Changing VERITAS Snapshot Provider Configuration to work in your environment
This is seen when VERITAS Snapshot Provider (VSP) is enabled and the cache size is set to 0. This allows VSP to determine the size of the cache file. On a client with multiple drives, consisting of one small drive and the others of varying larger sizes, the VSP volume may be placed on the smaller drive and grow to fill up the free space that is available on that drive. This will cause the status 11 error to occur.

To resolve this error, determine the amount of free space on the smallest drive. Then set the Initial cache size and Maximum cache size to that value. This can be done through the GUI (Figure 1) or through the registry (Figure 2).  

Alternatively, the location of the VSP cache file can be set to a larger drive with more free space (Figure 3).

NOTE:  If the larger drive being specified for the cache file is also being backed up using VSP, it will not be used for the other drive's cache file. The default behavior of VSP is Individual drive snapshots. This states that the cache file will be placed on the same volume that is being snapped, i.e. C: to C: and D: to D: etc. In addition, drive free space changes will affect the amount of space available and this consideration should be taken into account before making setting changes.  

Configure using the NetBackup Administration Console:

1.  Open the NetBackup Administration Console
2.  Expand Host Properties and highlight Clients
3.  Double-click on the client name in the pane on the right-hand side of the console
4.  Select the VSP tab and set the Initial cache size and Maximum cache size values (Figure 1)

Figure 1
   


Configure using the Windows registry on the client:

1.  Click Start | Run and type regedt32 and select OK
2.  Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config
3.  Set the VSP_Cache_Size_Init and VSP_Cache_Size_Max to the desired decimal value (Figure 2)


Figure 2
   


Choose to place the cache file on another volume, if that volume is not being currently backed up (Figure 3).

Figure 3
 





Legacy ID



264916


Article URL http://www.symantec.com/docs/TECH29809


Terms of use for this information are found in Legal Notices