media manager - system error occurred (174)

1 sept. 2019 18:03:09 - Info nbjm (pid=5140) starting backup job (jobid=121048) for client 10.0.100.212, policy P_DB_SQL_NEW, schedule Full
11 sept. 2019 18:03:09 - Info nbjm (pid=5140) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=121048, request id:{6E79351E-7088-401E-BD20-5ADDC0E1A733})
11 sept. 2019 18:03:09 - requesting resource sauv01py112-hcart-robot-tld-0
11 sept. 2019 18:03:09 - requesting resource sauv01py112.snmvt.intra.NBU_CLIENT.MAXJOBS.10.0.100.212
11 sept. 2019 18:03:09 - awaiting resource sauv01py112-hcart-robot-tld-0. No drives are available.
11 sept. 2019 18:04:43 - granted resource sauv01py112.snmvt.intra.NBU_CLIENT.MAXJOBS.10.0.100.212
11 sept. 2019 18:04:43 - granted resource 0009L4
11 sept. 2019 18:04:43 - granted resource IBM.ULT3580-TD4.001
11 sept. 2019 18:04:43 - granted resource sauv01py112-hcart-robot-tld-0
11 sept. 2019 18:04:44 - estimated 0 kbytes needed
11 sept. 2019 18:04:44 - Info nbjm (pid=5140) started backup (backupid=srv-nav2009.snmvt.intra_1568221483) job for client 10.0.100.212, policy P_DB_SQL_NEW, schedule Full on storage unit sauv01py112-hcart-robot-tld-0
11 sept. 2019 18:04:44 - started process bpbrm (pid=10608)
11 sept. 2019 18:04:46 - Info bpbrm (pid=10608) 10.0.100.212 is the host to backup data from
11 sept. 2019 18:04:46 - Info bpbrm (pid=10608) reading file list for client
11 sept. 2019 18:04:47 - connecting
11 sept. 2019 18:04:49 - Info bpbrm (pid=10608) listening for client connection
11 sept. 2019 18:04:56 - Info bpbrm (pid=10608) INF - Client read timeout = 3600
11 sept. 2019 18:04:56 - Info bpbrm (pid=10608) accepted connection from client
11 sept. 2019 18:04:56 - connected; connect time: 0:00:00
11 sept. 2019 18:04:57 - Info dbclient (pid=5160) Backup started
11 sept. 2019 18:04:57 - Info bptm (pid=7512) start
11 sept. 2019 18:04:57 - Info bptm (pid=7512) using 65536 data buffer size
11 sept. 2019 18:04:59 - Info bptm (pid=7512) setting receive network buffer to 263168 bytes
11 sept. 2019 18:04:59 - Info bptm (pid=7512) using 30 data buffers
11 sept. 2019 18:05:00 - Info bptm (pid=7512) start backup
11 sept. 2019 18:05:00 - Info bptm (pid=7512) backup child process is pid 11884.11268
11 sept. 2019 18:05:00 - Info bptm (pid=7512) Waiting for mount of media id 0009L4 (copy 1) on server sauv01py112.snmvt.intra.
11 sept. 2019 18:05:00 - Info bptm (pid=11884) start
11 sept. 2019 18:05:00 - mounting 0009L4
11 sept. 2019 18:05:49 - Info bptm (pid=7512) media id 0009L4 mounted on drive index 1, drivepath {3,0,0,0}, drivename IBM.ULT3580-TD4.001, copy 1
11 sept. 2019 18:05:49 - mounted 0009L4; mount time: 0:00:49
11 sept. 2019 18:05:50 - positioning 0009L4 to file 20
11 sept. 2019 18:06:41 - positioned 0009L4; position time: 0:00:51
11 sept. 2019 18:06:41 - begin writing
11 sept. 2019 18:06:42 - Info dbclient (pid=5160) dbclient(pid=5160) wrote first buffer(size=65536)
11 sept. 2019 18:20:37 - Info dbclient (pid=5160) done. status: 6
11 sept. 2019 18:20:42 - Critical bptm (pid=11884) attempted to write 7 gigabytes, 1971067252 bytes, it is not a multiple of 512
11 sept. 2019 18:20:42 - Info bptm (pid=7512) waited for full buffer 22703 times, delayed 47829 times
11 sept. 2019 18:21:50 - Info bptm (pid=7512) EXITING with status 174 <----------
11 sept. 2019 18:21:54 - Info dbclient (pid=5160) done. status: 174: media manager - system error occurred
11 sept. 2019 18:21:54 - end writing; write time: 0:15:13
media manager - system error occurred (174)
hello all

so the troublesouting of this later is to change drive ?? are you agree?

Tags (2)
1 Reply

Re: media manager - system error occurred (174)

Who on earth can say whether a tape drive needs changing based upon a snipet from an activity monitor job log.

Why don't you try googling for :

critical bptm attempted to write it is not a multiple of 512

...which throws up some interesting posts.

Then, why don't you filter and follow those articles first for yourself, and then come back to us with your own findings if / when you get stuck.