Incremental backup failing only for D: drive in status code 42/24. Full backup is completing successfully.

[Saravananpl]

Inputs:

• The backup comleting successfully for other drives namely C: and Shadow Copy Components:\
• Client machine runs on Win2003 and NBU version is 7.5.0.5
• Master and Media server runs on Linux and NBU version is 7.5.0.5

[RamNagalla]

what is the backup Size of the D Drive?

what the read timeout that is set on the media server? did you try with 2700 

post the failed job detail status..

[Stumpr2]

C: and Shadow are good
D: FULL backup is good
D: incremental fails w/timeout

So what is difference between how a full backup runs and how an incremental backup runs?
Maybe the applications/services during the day/time that the schedule runs the backups?

As Nagalla requested...post the details :)

[quebek]

What is in bpcd, bpfis, bpbackup, bpbkar logs created on client for failed jobs?!

[Shaf]

Check Drive D is mounted during backup, and check the permission level of D drive

[Shaf]

and also check you have enough space on D drive,

should not run out of space..

[Marianne]

Check D-drive for fragmentation.

Large drive with heavy fragmentation may cause timeout while 'walking' the filesystem looking for changed files.

Please post all text in Job Details for failed job and ensure all of the following log folders exist:

On media server: bptm and bpbrm

On client: bpbkar and bpfis

[Stumpr2]

Notice how Marianne and others posted to check out the D drive first? That is exactly what I would do first. Check all the properties including shadow copy configuration and fragmentation.
If that dont work:
I also would copy the existing policy into a new one, remove all other clients and only list the D drive with multistreaming enabled. First backup is full but after that incremental backups can run. Nice thing about own policy helps with smaller logfiles and the multistreaming helps point to which folder a problem may be in.

Footwork like this may help you fix the problem and if not then also provide us with logs/details that are easier to sort through.

[Saravananpl]

The update is as follows:

• Increased the read timeout on media server to 2700 and attached the job detailed status
• Created the bpbkar, bpcd, bpfis and bpbackup logs with high verbosity
• The D: drive has 3+ Gig free space out of 150 Gig disk

I will upload the log files after next backup run.

[Stumpr2]

The D drive is using 147GB and only 3 GB is available?

Microsoft recommends the snapshot 'Use limit' be configured for roughly 10% of occupied space. For example, if the D:\ drive has 147GB of data on it, the 'Use limit' should be set to 15 GB.

but you only have 3 GB available....

Perhaps this is why the full run OK because there are fewer active files during the full backup window as opposed to the incremental backup window?

[Marianne]

It's been a week...

Have you been able to check the D-drive for fragmentation yet?

And Bob's post about free space on the drive?

We see that no data is received from the client in almost 1 hour:

11/8/2013 8:10:27 PM - begin writing
11/8/2013 9:04:10 PM - Error bptm(pid=10189) system call failed - Connection reset by peer (at child.c.1298)   

This means that all troubleshooting should be done on the client.

Do you have logs yet?

[Stumpr2]

...and another week. Has this issue been solved?