12-05-2014 12:11 AM
VM backup failure with error code 12. There was an ongoing issue due to disk lock as all of them were unlocked by linux team. but among all those servers a server is still failing with error code 12. A snapshot job is started and then a backup job. within few seconds they both gets failed.
12/05/2014 02:01:11 - Info nbjm (pid=10211) starting backup job (jobid=5399626) for client lpwebejb120, policy PROD_VMWARE_VW_Adhoc, schedule Differential-Inc
12/05/2014 02:01:11 - estimated 0 kbytes needed
12/05/2014 02:01:11 - Info nbjm (pid=10211) started backup (backupid=lpwebejb120_1417766471) job for client lpwebejb120, policy PROD_VMWARE_VW_Adhoc, schedule Differential-Inc on storage unit STU_DDR1_DALMEDIA4
12/05/2014 02:01:12 - started process bpbrm (pid=6496)
12/05/2014 02:01:12 - Error bpbrm (pid=6496) Unsupported storage server type (DataDomain) - disabling Client Direct
12/05/2014 02:01:12 - Info bpbrm (pid=6496) lpwebejb120 is the host to backup data from
12/05/2014 02:01:12 - Info bpbrm (pid=6496) reading file list for client
12/05/2014 02:01:12 - Info bpbrm (pid=6496) starting bpbkar32 on client
12/05/2014 02:01:12 - connecting
12/05/2014 02:01:13 - connected; connect time: 0:00:00
12/05/2014 02:01:14 - Info bpbkar32 (pid=7460) Backup started
12/05/2014 02:01:14 - Info bpbkar32 (pid=7460) archive bit processing:<enabled>
12/05/2014 02:01:14 - Info bptm (pid=2412) start
12/05/2014 02:01:14 - Info bptm (pid=2412) using 262144 data buffer size
12/05/2014 02:01:14 - Info bptm (pid=2412) setting receive network buffer to 1049600 bytes
12/05/2014 02:01:14 - Info bptm (pid=2412) using 30 data buffers
12/05/2014 02:01:17 - Info bptm (pid=2412) start backup
12/05/2014 02:01:18 - begin writing
12/05/2014 02:03:16 - Error bpbrm (pid=6496) db_FLISTsend failed: file open failed (12)
12/05/2014 02:03:54 - Info bpbkar32 (pid=0) bpbkar waited 0 times for empty buffer, delayed 0 times.
12/05/2014 02:03:54 - Critical bpbrm (pid=6496) unexpected termination of client lpwebejb120
12/05/2014 02:03:54 - Info bpbkar32 (pid=0) done. status: 12: file open failed
12/05/2014 02:03:54 - end writing; write time: 0:02:36
file open failed (12)
Solved! Go to Solution.
12-05-2014 12:49 AM
You need to troubleshoot on the client that is still failing.
Ask the Linux admins to test a backup to /dev/null using tar on the client.
Alternatively, test filesystem read with NBU bpbkar command:
/usr/openv/netbackup/bin/bpbkar -nocont -dt 0 -nofileinfo -nokeepalives file system > /dev/null
Ensure bpbkar log folder exists with logging level at 1 or higher.
See:
Measuring disk performance with bpbkar
http://www.symantec.com/docs/HOWTO99824
12-05-2014 12:49 AM
You need to troubleshoot on the client that is still failing.
Ask the Linux admins to test a backup to /dev/null using tar on the client.
Alternatively, test filesystem read with NBU bpbkar command:
/usr/openv/netbackup/bin/bpbkar -nocont -dt 0 -nofileinfo -nokeepalives file system > /dev/null
Ensure bpbkar log folder exists with logging level at 1 or higher.
See:
Measuring disk performance with bpbkar
http://www.symantec.com/docs/HOWTO99824
12-05-2014 03:39 AM
I have asked linux team to run a backup to /dev/null . Hope this will confirm if issue is @client end or not.isnt it?
12-05-2014 03:57 AM
I am pretty sure it will.
01-12-2015 01:58 AM
Thanks, it worked. Not sure what exactly issue was but yes linux team did a task at their end and it worked successfully. Thanks.