Keep getting backup failed status 13 with WFOB even when child jobs show 0

[bilson111]

Hello

I am having a problem with a backup using Windows Open File backup option on a Windows 2003 x86 SP2 with Netbackup 7.1 client. Master server is 7.1.0.4 on 2008R2. My policy backs up C:\, Shadow copy, and system state). VSS for C drive is set to use D:\ (with size unlimited, plenty of space on D:\) due to fairly small system partition. All child jobs complete with status 0 in activity monitor, I still get an email with Error status 13 - file read failed. Under Reports>Problems, I consistently get: socket read failed: errno = 104 - Connection reset by peer. source: bpbrm, for each backup attempt.

Bpbkar logs don't show anything strange and ends up with 0. bpfis log consistently has lines like those below and 156 status. In windows all vss writers show stable.

12:21:57.475 [2672.3012] <32> onlfi_thaw: FTL - VfMS error 5; see following messages:
12:21:57.475 [2672.3012] <32> onlfi_thaw: FTL - File open failed
12:21:57.475 [2672.3012] <32> onlfi_thaw: FTL - do_reaccess: cannot open reaccess file C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.fs1.coxtarget.com_1371140509.1.0.fiid
 

I attached the bpfis log portion from the last differential run I attempted and policy. Bpbkar log is huge (266MB) due to my numerous reruns I guess.

Not sure what to try next.

[Dyneshia]

Patch the client to 7.1.0.4

Next, I see from the bpfis :

12:21:57.475 [2672.3012] <4> bpfis main: INF - snapshot creation failed, status 156
12:21:57.475 [2672.3012] <2> onlfi_thaw: INF - fim=auto
12:21:57.475 [2672.3012] <2> onlfi_thaw: INF - fim=Hyper-V
12:21:57.475 [2672.3012] <2> onlfi_thaw: INF - fim=VSS
12:21:57.475 [2672.3012] <4> onlfi_thaw: INF - Thawing System State:\ using snapshot method VSS.
12:21:57.475 [2672.3012] <8> onlfi_thaw: WRN - System State:\ is not frozen
12:21:57.475 [2672.3012] <4> onlfi_thaw: INF - Thawing C:\ using snapshot method VSS.
12:21:57.475 [2672.3012] <8> onlfi_thaw: WRN - C:\ is not frozen
12:21:57.475 [2672.3012] <2> onlfi_thaw: INF - fim=VMware
12:21:57.475 [2672.3012] <2> onlfi_thaw: INF - fim=NAS_Snapshot
12:21:57.475 [2672.3012] <2> onlfi_thaw: INF - fim=VSS_Writer
12:21:57.475 [2672.3012] <8> bpfis Exit: WRN - snapshot delete returned status 20

Are there any errors in the application event viewer ?

Has this worked before ?

[bilson111]

I forgot to add something. This server had client version of 7.5.0.5 (previously it was being backed up by another master server running 7.5.0.5 as well. At some point backup got moved to our primary master which is still on 7.1.0.4. and it seemed to work fine despite the version mismatch, until about 5 days ago when it started erroring out with 13. Server was pretty low on memory and pretty much unresponsive so it was rebooted.

Today, when I was researching this particular error message, I saw a post here that socket read error can be caused by a version mismatch, so I uninstalled client verison 7.5.0.5 and reverted back to 7.1 in hopes of fixing the problem but it did not help. One thing to not is between the uninstall and reinstall of the older client I have not rebooted the server - it stores metaframe profile folders and the restart window is pretty small and only on Sunday, most likely. Is there any chance 7.1.0.4 would do anything for this problem?

=======================

There are no errors in the Application log, or the system log.

Yes, it was working. Shadow copy was disabled on C though and some of the backups were completing with status of 1.

[Dyneshia]

Ok...So... Currnlety the master server is 7.1.0.4 and the client is at 7.1 correct ? Or is the client 7.1.0.4 ?

[bilson111]

Client is 7.1

I also changed client attribute Snapshot Usage to Global drive snapshot - still 13, and one status message with - 1.

Another run with Snapshot Error control changed to Disable Snaptshot & continue - 13 again.

According to a post here, deleting C:\Program Files\VERITAS\NetBackup\online_util\fi_cntl folder allowed backup to complete with no errors. Is this folder safe to delete? Here's the link to the post.

http://www.symantec.com/connect/forums/backup-failed-due-snapshot-error

[Dyneshia]

It is safe , please see : https://www-secure.symantec.com/connect/forums/ficntl-what-it

I would still patch the client to 7.1.0.4 as I remember an issue with status 13 at ealier releases.