Seeing a backup fail at the same point all the time

If I see liblocal failing at the same time as when error happens, I would suspect NW.  You can run save from CLI just to see if you get anything more.  I would also compare how much memory save command has consumed with time, especially nearing the expected break. 1+ TB save set is not small and I wonder if something in such size is breaking NW.  You may wish also to update to latest NW7 version on client side.

Hi Liam,

I first would make sure that the correct TCP/IP timers are in place.

Also check the client inactivity time out.

Anyway, having a crash I rather open a case with support, but agreed with Hrvoje, try first upgrading to the latest NW 7.x cumulative fix, as most likely the solution would be already included in the latest build.

Thank you,

Carlos

I would suggest:

1. Upgrade to the latest version of NetWorker 7.6.5 or 8.0/8.1.

If the issue persists,

2. This issue can be also caused by the confliction between NetWorker and another software especially anti-virus programs. Check whether there is any anti-virus program running on your computer. If so, temparily disable/remove it and then check the backup result.

Thanks Guys for responding.

I upgraded NW to 7.6.5.7 but still seeing the same problem.

Faulting

application save.exe, version 7.6.5.7, time stamp 0x5239057e, faulting module liblocal.dll, version 7.6.5.7, time stamp 0x5238fc54, exception code 0xc00000fd, fault offset 0x000000000006a8c7, process id 0x2940, application start time 0x01cee602839f1475

There are other similiar size volumes on this server which are backing up without issue.

Memory/CPU usage does not seem an issue.

There are no relevant enties in the NW log files on the server.

On the NW server the group is configured with an inactivity timeout of 0 & a file inactivity threshold of 0 also.

Thanks for taking the time to respond.

Can you try two tests:

- start save from client and see if it breaks at the same point

- if it breaks at the same point, start backup in debug mode only for that point

If this is taking to much time as you wish to have backups and not tests first, split manually this backup set into folders and do backup of each first.  One of them may fail and that one might be the same one (same point) where it was breaking before and then you can apply above tests to that isolated area.

IMHO, the picture seems to point to a file system problem. In this case, another NW client version will of course not help.

Thanks Guys for the suggestions.

Sorry for the delay in responding.

I broke down the savesets, performing a manual save on the directory where the bkup is failing.

The directory path of the last file backed up is listed below.

While I think it's a file system issue, I'm wondering would Networker have an issue nagivating such a large file system to backup a file.

Has anyone ever seen anything like this before ?

P:\Packaging\MMC\LEXsoft_Professional-3-1-0-0002\1.0\LEXsoft_Professional-3-1-0-0002\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_P

rofessional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXs

oft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2

\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\

EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3

.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\LEXsoft_Professional\3.1.0\EN\R2\Distribute.vbs

Tks,

Liam

It depends what API you use: Naming Files, Paths, and Namespaces (Windows)