cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup job fails with with status 174

t_jadliwala
Level 4
Partner Accredited
I m using san transport mode to run the backup job. The backup job fails on solaris client. THe job is targetted to netbackup appliance 5230. This job fails frequently however when i retry this job it runs fine. Any idea what is causing the job to fail. 1/11/2014 1:00:18 AM - Info nbjm(pid=23898) starting backup job (jobid=568959) for client doma, policy MAIN-SOLARIS-T1-DOMA, schedule Daily 11/11/2014 1:00:18 AM - Info nbjm(pid=23898) requesting STANDARD_RESOURCE resources from for backup job (jobid=568959, request id:{F55B960E-6924-11E4-BDB9-6B23B904EDE2}) 11/11/2014 1:00:18 AM - requesting resource NBU-APP-Main-media-3-STU 11/11/2014 1:00:18 AM - requesting resource nb-mast.NsBU_CLIENT.MAXJOBS.doma 11/11/2014 1:00:18 AM - requesting resource nb-mast.NBU_POLICY.MAXJOBS.MAIN-SOLARIS-T1-DOMA 11/11/2014 1:00:18 AM - Info nbrb(pid=23697) Limit has been reached for the logical resource nb-mast.NBU_POLICY.MAXJOBS.MAIN-SOLARIS-T1-DOMA 11/11/2014 1:33:37 AM - Info bpbrm(pid=2426) doma is the host to backup data from 11/11/2014 1:33:37 AM - Info bpbrm(pid=2426) reading file list from client 11/11/2014 1:33:37 AM - granted resource nb-mast.NBU_CLIENT.MAXJOBS.doma 11/11/2014 1:33:37 AM - granted resource nb-mast.NBU_POLICY.MAXJOBS.MAIN-SOLARIS-T1-DOMA 11/11/2014 1:33:37 AM - granted resource MediaID=@aaaas;DiskVolume=PureDiskVolume;DiskPool=dp_disk_main-media-3;Path=PureDiskVolume;StorageServer=main-media-3;MediaServer=main-media-2 11/11/2014 1:33:37 AM - granted resource NBU-APP-Main-media-3-STU 11/11/2014 1:33:37 AM - granted resource TRANSPORT 11/11/2014 1:33:37 AM - estimated 286064870 Kbytes needed 11/11/2014 1:33:37 AM - Info nbjm(pid=23898) started backup (backupid=doma_1415658817) job for client doma, policy MAIN-SOLARIS-T1-DOMA, schedule Daily on storage unit NBU-APP-Main-media-3-STU 11/11/2014 1:33:37 AM - started process bpbrm (2426) 11/11/2014 1:33:37 AM - connecting 11/11/2014 1:33:38 AM - Info bpbrm(pid=2426) starting bpbkar on client 11/11/2014 1:33:38 AM - connected; connect time: 00:00:01 11/11/2014 1:33:39 AM - Info bpbkar(pid=20133) Backup started 11/11/2014 1:33:39 AM - Info bpbrm(pid=2426) bptm pid: 2437 11/11/2014 1:33:39 AM - Info bptm(pid=2437) start 11/11/2014 1:33:39 AM - Info bptm(pid=2437) using 262144 data buffer size 11/11/2014 1:33:39 AM - Info bptm(pid=2437) using 16 data buffers 11/11/2014 1:33:39 AM - Info bptm(pid=2437) USING 262144 data buffer size for FT 11/11/2014 1:33:40 AM - Info bptm(pid=2437) start backup 11/11/2014 1:33:40 AM - Opening Fibre Transport Connection, Backup Id: doma_1415658817 11/11/2014 1:33:41 AM - begin writing 11/11/2014 1:33:45 AM - Error bpbrm(pid=2426) from client doma: ERR - bpbkar exiting because backup is aborting 11/11/2014 1:33:45 AM - Critical bptm(pid=2437) data buffers out of sequence, expected number 1185, received 1188 11/11/2014 1:33:49 AM - Info bptm(pid=2437) EXITING with status 174 <---------- 11/11/2014 1:33:49 AM - Info main-media-2(pid=2437) StorageServer=PureDisk:main-media-3; Report=PDDO Stats for (main-media-3): scanned: 303107 KB, CR sent: 1 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache hits: 37 (1.6%) 11/11/2014 1:33:49 AM - Info bpbkar(pid=20133) done. status: 174: media manager - system error occurred 11/11/2014 1:33:49 AM - end writing; write time: 00:00:08 media manager - system error occurred(174)
1 REPLY 1

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

Take a look at this note http://www.symantec.com/docs/TECH147561