RMAN Backup failing after backup "begin writing"
03/04/2013 05:02:50 - Info nbjm (pid=28573784) starting backup job (jobid=1002560) for client sapm6pdrv-nb, policy ORA_RMAN_GRV_M6P, schedule Default-Application-Backup
03/04/2013 05:02:50 - Info nbjm (pid=28573784) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1002560, request id:{AC5A40B6-84B2-11E2-B1C5-02AA35650000})
03/04/2013 05:02:50 - requesting resource nbu-media-grv-nb-hcart3-robot-tld-3
03/04/2013 05:02:50 - requesting resource sun107-nb.NBU_CLIENT.MAXJOBS.sapm6pdrv-nb
03/04/2013 05:02:50 - requesting resource sun107-nb.NBU_POLICY.MAXJOBS.ORA_RMAN_GRV_M6P
03/04/2013 05:02:50 - Waiting for scan drive stop STK.T10000A.015, Media server: nbu-media-grv-nb
03/04/2013 05:02:51 - granted resource sun107-nb.NBU_CLIENT.MAXJOBS.sapm6pdrv-nb
03/04/2013 05:02:51 - granted resource sun107-nb.NBU_POLICY.MAXJOBS.ORA_RMAN_GRV_M6P
03/04/2013 05:02:51 - granted resource I00184
03/04/2013 05:02:51 - granted resource STK.T10000A.015
03/04/2013 05:02:51 - granted resource nbu-media-grv-nb-hcart3-robot-tld-3
03/04/2013 05:02:52 - estimated 0 kbytes needed
03/04/2013 05:02:52 - Info nbjm (pid=28573784) started backup (backupid=sapm6pdrv-nb_1362391372) job for client sapm6pdrv-nb, policy ORA_RMAN_GRV_M6P, schedule Default-Application-Backup on storage unit nbu-media-grv-nb-hcart3-robot-tld-3
03/04/2013 05:02:55 - mounting I00184
03/04/2013 05:02:56 - Info bpbrm (pid=19923062) sapm6pdrv-nb is the host to backup data from
03/04/2013 05:02:56 - Info bpbrm (pid=19923062) telling media manager to start backup on client
03/04/2013 05:02:56 - Info bptm (pid=11206736) using 262144 data buffer size
03/04/2013 05:02:56 - Info bptm (pid=11206736) using 64 data buffers
03/04/2013 05:02:57 - Info bpbrm (pid=19923062) spawning a brm child process
03/04/2013 05:02:57 - Info bpbrm (pid=19923062) child pid: 16842958
03/04/2013 05:02:58 - Info bpbrm (pid=19923062) sending bpsched msg: CONNECTING TO CLIENT FOR sapm6pdrv-nb_1362391372
03/04/2013 05:02:58 - Info bpbrm (pid=19923062) listening for client connection
03/04/2013 05:02:58 - connecting
03/04/2013 05:03:05 - Info bpbrm (pid=19923062) INF - Client read timeout = 3000
03/04/2013 05:03:11 - Info bpbrm (pid=19923062) accepted connection from client
03/04/2013 05:03:11 - connected; connect time: 0:00:00
03/04/2013 05:03:30 - mounted I00184; mount time: 0:00:35
03/04/2013 05:03:31 - positioning I00184 to file 113
03/04/2013 05:03:42 - positioned I00184; position time: 0:00:11
03/04/2013 05:03:42 - begin writing
03/04/2013 05:18:16 - Error bpbrm (pid=16842958) client sapm6pdrv-nb EXIT STATUS = 6: the backup failed to back up the requested files
03/04/2013 05:18:16 - Info bpbkar (pid=0) done. status: 6
03/04/2013 05:18:16 - Info bpbrm (pid=19923062) sending message to media manager: STOP BACKUP sapm6pdrv-nb_1362391372
03/04/2013 05:18:17 - Info bpbrm (pid=19923062) media manager for backup id sapm6pdrv-nb_1362391372 exited with status 150: termination requested by administrator
03/04/2013 05:18:17 - end writing; write time: 0:14:35
the backup failed to back up the requested files (6)
The above tells us that the master is trying to connect to bpcd on the client (via vnetd).
We need to see incoming connection FROM 10.48.184.74.55164 TO 100.6.1.107.13724.
You can also check connectivity from Client to master as follows:
bpclntcmd -pn
Client should get response back from master server with client name that is known by master server.
Evidence of this connection request can also be seen in master's bprd log.