Forum Discussion

Pratique's avatar
Pratique
Level 4
13 years ago

Full backup failing with 24

We have full backups failing for G and H drive with error 24 while the differential backups complete for the same drives

The other drives are successfully getting backed up. Could anyone suggest, what needs to be done here?

Sep 8, 2011 1:33:21 AM - requesting resource X42k406_LTO3
Sep 8, 2011 1:33:21 AM - requesting resource x42k405.NBU_CLIENT.MAXJOBS.de01dtmapp001v-bu
Sep 8, 2011 1:33:21 AM - requesting resource x42k405.NBU_POLICY.MAXJOBS.Windows
Sep 8, 2011 1:33:21 AM - granted resource  x42k405.NBU_CLIENT.MAXJOBS.de01dtmapp001v-bu
Sep 8, 2011 1:33:21 AM - granted resource  x42k405.NBU_POLICY.MAXJOBS.Windows
Sep 8, 2011 1:33:21 AM - granted resource  MT0762
Sep 8, 2011 1:33:21 AM - granted resource  IBM_LTO3_LIB01_FR10
Sep 8, 2011 1:33:21 AM - granted resource  X42k406_LTO3
Sep 8, 2011 1:33:22 AM - estimated 0 kbytes needed
Sep 8, 2011 1:33:30 AM - connecting
Sep 8, 2011 1:33:31 AM - connected; connect time: 0:00:00
Sep 8, 2011 1:33:31 AM - begin writing
Sep 8, 2011 4:19:31 AM - current media MT0762 complete, requesting next media Any
Sep 8, 2011 4:19:31 AM - current media -- complete, awaiting next media Any. Waiting for resources.
          Reason: Drives are in use, Media server: x42k406,
          Robot Type(Number): TLD(0), Media ID: N/A, Drive Name: N/A,
          Volume Pool: NetBackup, Storage Unit: X42k406_LTO3, Drive Scan Host: N/A,
          Disk Pool: N/A, Disk Volume: N/A
Sep 8, 2011 4:19:47 AM - Critical bpbrm (pid=28916) from client de01dtmapp001v-bu: FTL - socket write failed
Sep 8, 2011 4:19:47 AM - Error bpbrm (pid=28916) could not send server status message
Sep 8, 2011 4:20:00 AM - end writing; write time: 2:46:29
socket write failed  (24)

 

Though we have enough media, don't know why it requests for media.

17 Replies