08-21-2015 01:07 AM
I backup many clients all have a similar config. They use Client side de dup and backup up to a centralised puredisk pool.
Two clients are giving me the same error and I am having a lot of trouble backing them up.
They are windows 2008 clients.
The error I always get is bpbkar waited for empty buffers xxx times, delayed xxxtimes. Then the job fails with a 14 file write failed error.
I backup 328 clients all others are fine.
Master Server and client version is 7.1.0.4.
Can anyone help?
Solved! Go to Solution.
08-26-2015 07:42 AM
Still memory issue on the client.
The touch files on the media server is just making the media server wait longer before giving up.
08-21-2015 03:56 AM
Please paste complete job details and bpbkar from the affected client with verbosity 5.
08-21-2015 04:44 AM
These 2 clients, what are their differences with other clients?
Less memory? Too many applications running - higher load? Note that client dedup requires the client to perform the dedup so the client needs to meet certain "standard".
Check this out: https://www-secure.symantec.com/connect/forums/host-requirements-client-side-deduplication
08-21-2015 05:06 AM
Post versions
08-21-2015 06:15 AM
They are all on 7.1.04, all have same memory and build as working clients.
08-21-2015 06:28 AM
Please post job details and clients' bpbkar logs as requested earlier.
08-21-2015 06:43 AM
Log file attached
08-21-2015 06:50 AM
We are still missing Job details.....
08-21-2015 06:56 AM
Older version were known to have issues like that if you enabled checkpoint restarts.
08-24-2015 03:30 AM
Removed checkpoints - still failing - job details and bpbkar log attached.
08-24-2015 03:52 AM
Is there a firewall between the client and media and/or master server?
Check that ports 10082 and 10102 are open in both directions.
Also verify that Windows firewall on client is turned off.
You will also need bptm log on media server since we see in Job details that bptm process is reporting error 2060017 and 2060005.
08-24-2015 05:58 AM
How does the backup go if you disable the client side dedupe?
08-24-2015 06:29 AM
Those ports are closed from client - but they are closed for all clients and the other 300 don't have any issues. Will disbale client side de dup now and try another backup.
I have done this in the past and it's been painfully slow mind.
Disabling client side de dup led to both backups failing very quickly with a socket write failed 24 error. At least with the client side de dup enabled I did get to write some data.
08-24-2015 06:33 AM
For Netbackup to be able to backup the client with client side dedupe, these ports are required.
For testing you can open the ports for some time and try a backup with client side dedupe enable.
08-24-2015 06:38 AM
Ports ports 10082 and 10102 must be open in both directions for Client dedupe.
If the other clients are working fine, then there is either no firewall or dedupe is done on the media server.
08-24-2015 07:09 AM
Doesn't explain how i will get a few thousands of files and kilobytes written to pool - if ports needed for backup were closed wouldn't write at all.
08-24-2015 07:25 AM
Media server dedupe does not need the ports open.
Only client-side.
08-24-2015 07:30 AM
sorry ports are open I had a typo in media server name when I was telnet - tested again and I can telnet on ports
08-24-2015 10:00 AM
Can u please post the tests your ran to check if the port is open or not?
We are expecting it to be open bidirectional between client and media server.
08-26-2015 04:17 AM
I telnet from media server to client and vice versa ports are open and I can write data to pool but backup always fails with a 14 file write failed error on both clients.
Always witing for empty buffers message in job details.