Quantcast
Channel: Symantec Connect - Backup and Recovery
Viewing all articles
Browse latest Browse all 1524

to many data blocks written

$
0
0
I need a solution

Hi dear all,

after upgrade to 7.7.2, four media servers backup failed with status 84, media write error. backup types are application backup with RMAN, one channel in some archive/Level0 backups get error 84.

this is full detail:

05/07/2016 19:58:40 - Info nbjm (pid=3123) starting backup job (jobid=432802) for client fm-db2, policy FM-T6K-PH-ORA-ARC-fm-db2, schedule monthly
05/07/2016 19:58:40 - Info nbjm (pid=3123) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=432802, request id:{608605DC-1468-11E6-9F05-859882152612})
05/07/2016 19:58:40 - requesting resource fm-db2-hcart3-Qi6K-tld-2
05/07/2016 19:58:40 - requesting resource mstr-nbkp-srv.NBU_CLIENT.MAXJOBS.fm-db2
05/07/2016 19:58:40 - requesting resource mstr-nbkp-srv.NBU_POLICY.MAXJOBS.FM-T6K-PH-ORA-ARC-fm-db2
05/07/2016 19:58:41 - Waiting for scan drive stop HP.ULTRIUM6-SCSI.032, Media server: fm-db2
05/07/2016 19:58:41 - granted resource  mstr-nbkp-srv.NBU_CLIENT.MAXJOBS.fm-db2
05/07/2016 19:58:41 - granted resource  mstr-nbkp-srv.NBU_POLICY.MAXJOBS.FM-T6K-PH-ORA-ARC-fm-db2
05/07/2016 19:58:41 - granted resource  L60029
05/07/2016 19:58:41 - granted resource  HP.ULTRIUM6-SCSI.032
05/07/2016 19:58:41 - granted resource  fm-db2-hcart3-Qi6K-tld-2
05/07/2016 19:58:54 - estimated 0 kbytes needed
05/07/2016 19:58:54 - Info nbjm (pid=3123) started backup (backupid=fm-db2_1462634934) job for client fm-db2, policy FM-T6K-PH-ORA-ARC-fm-db2, schedule monthly on storage unit fm-db2-hcart3-Qi6K-tld-2
05/07/2016 19:58:55 - started process bpbrm (pid=36869)
05/07/2016 19:58:55 - connecting
05/07/2016 19:58:56 - connected; connect time: 0:00:00
05/07/2016 19:59:36 - mounting L60029
05/07/2016 20:00:44 - Info bpbrm (pid=36869) fm-db2 is the host to backup data from
05/07/2016 20:00:44 - Info bpbrm (pid=36869) reading file list from client
05/07/2016 20:00:44 - Info bpbrm (pid=36869) listening for client connection
05/07/2016 20:00:45 - Info bpbrm (pid=36869) INF - Client read timeout = 3000
05/07/2016 20:00:45 - Info bpbrm (pid=36869) accepted connection from client
05/07/2016 20:00:46 - Info bphdb (pid=36750) Backup started
05/07/2016 20:00:46 - Info bpbrm (pid=36869) bptm pid: 36876
05/07/2016 20:00:46 - Info bptm (pid=36876) start
05/07/2016 20:01:26 - Info bptm (pid=36876) using 65536 data buffer size
05/07/2016 20:01:26 - Info bptm (pid=36876) using 30 data buffers
05/07/2016 20:01:26 - Info bptm (pid=36876) start backup
05/07/2016 20:01:26 - Info bptm (pid=36876) Waiting for mount of media id L60029 (copy 1) on server fm-db2.
05/07/2016 20:01:32 - mounted L60029; mount time: 0:01:56
05/07/2016 20:01:32 - positioning L60029 to file 7
05/07/2016 20:02:05 - positioned L60029; position time: 0:00:33
05/07/2016 20:02:05 - begin writing
05/07/2016 20:03:22 - Info bptm (pid=36876) media id L60029 mounted on drive index 35, drivepath /dev/rmt/53cbn, drivename HP.ULTRIUM6-SCSI.032, copy 1
05/07/2016 20:04:00 - Info bphdb (pid=36750) dbclient(pid=36750) wrote first buffer(size=262144)
05/07/2016 20:06:51 - end writing; write time: 0:04:46
05/07/2016 20:08:28 - Info bphdb (pid=36750) dbclient waited 7347 times for empty buffer, delayed 7347 times
05/07/2016 20:08:28 - Info bphdb (pid=36750) done. status: 0
05/07/2016 20:08:28 - Info bptm (pid=36876) waited for full buffer 4015 times, delayed 8130 times
05/07/2016 20:08:37 - Error bptm (pid=36876) FREEZING media id L60029, too many data blocks written, check tape/driver block size configuration
05/07/2016 20:08:37 - Info bptm (pid=36876) EXITING with status 84 <----------
05/07/2016 20:08:40 - Info bphdb (pid=36750) done. status: 84: media write error
media write error  (84)

thanks

0

Viewing all articles
Browse latest Browse all 1524

Trending Articles