BUG REPORT: A UNC backup of a shared folder from a Windows 2008 R2 client fails with Status Code 13.

  • Modified Date:
  • Article ID:000012977


A backup of a UNC (Universal Naming Convention) path of a NetApp NDMP filer fails with a Status Code 13 (file read failed) in NetBackup 7.0.1.

The process bpbkar32.exe faults on Windows 2008 R2 Servers.


The backup and archive process (bpbkar32.exe) is faulting on the system causing the backup to fail.


The work around procedure is to disable NetBackup Fast I/O (NTIO) by setting the registry to UseNTIO=0.

NOTE: NetBackup 7.5 will generate the following registry key by default during installation on Windows.

Disabling Fast I/O forces SYMANTEC NetBackup (tm) to use the built-in Windows BackupRead API (Microsoft published API) as opposed to using the NetBackup version of the BackupRead() API.

See Microsoft article for details: BackupRead Function:


To disable Fast I/O:

1. Click Start and Run, type regedit, and click OK

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

2. Browse to HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config

3. In the Config registry key, create a new key called NTIO

4. In the NTIO registry key, create a REG_DWORD value, give it the name UseNTIO, and the value 0 (zero)

Note: Fast I/O is enabled by default.  Setting the UseNTIO registry key set to zero (0) disables Fast I/O.

To enable NTIO set the registry key to one (1) or remove the key.

Applies To

NetApp NDMP:  Data Ontap 7.3.5.

Master Server: Netbackup 7.0.1

Client: Windows 2008 R2 x64

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)