Forum Discussion

rookie11's avatar
rookie11
Moderator
15 years ago
Solved

error code (10) allocation failed

Hi

master NBU 6.5 OS 5.10

media + client NBU 6.5 OS window 2008

all drives are up but backup job fails with error code 10

extract from bptm logs:

 10:31:54.040 [6272.4452] <4> bptm: emmserver_name = asp.com
10:31:54.040 [6272.4452] <4> bptm: emmserver_port = 1556
10:31:54.056 [6272.4452] <2> Orb::init: initializing ORB Default_CLIENT_Orb with: dbstunitq -ORBSvcConfDirective "-ORBDottedDecimalAddresses 0"

10:31:54.087 [6272.4452] <2> init_cache: vnet_hosts.c.990: host_cache_size: 200 0x000000c8
10:31:54.087 [6272.4452] <2> init_cache: vnet_hosts.c.991: cache_time: 3600 0x00000e10
10:31:54.087 [6272.4452] <2> init_cache: vnet_hosts.c.1003: host_failed_cache_size: 40 0x00000028
10:31:54.087 [6272.4452] <2> init_cache: vnet_hosts.c.1004: cache_time: 3600 0x00000e10
10:31:56.443 [6272.4452] <2> init_cache: vnet_hosts.c.990: host_cache_size: 200 0x000000c8
10:31:56.443 [6272.4452] <2> init_cache: vnet_hosts.c.991: cache_time: 3600 0x00000e10
10:31:56.443 [6272.4452] <2> init_cache: vnet_hosts.c.1003: host_failed_cache_size: 40 0x00000028
10:31:56.443 [6272.4452] <2> init_cache: vnet_hosts.c.1004: cache_time: 3600 0x00000e10
10:31:58.783 [6272.4452] <2> send_brm_msg: PID of bpxm = 6272
10:31:58.783 [6272.4452] <2> nbjm_media_request: Passing job control to NBJM, type UNLOAD/6
10:31:58.783 [6272.4452] <2> nbjm_media_request: old_media_id = NULL, media_id = GZ1562
10:31:58.783 [6272.4452] <2> Orb::init: Created anon service name: NB_6272_1720731354(Orb.cpp:585)
10:31:58.783 [6272.4452] <2> Orb::init: endpointvalue is : pbxiop://1556:NB_6272_1720731354(Orb.cpp:603)
10:31:58.783 [6272.4452] <2> Orb::init: initializing ORB Default_DAEMON_Orb with: Unknown -ORBSvcConfDirective "-ORBDottedDecimalAddresses 0"

10:44:39.786 [2476.5776] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1289679736 -jm
10:44:39.786 [2476.5776] <2> main: Sending [EXIT STATUS 0] to NBJM
10:44:39.786 [2476.5776] <2> bptm: EXITING with status 0 <----------
10:47:52.014 [4624.5388] <2> Media_signal_poll: Terminate detected (MultiResReq.cpp:2192)
10:47:52.014 [4624.5388] <2> RequestInitialResources: Cancellation requested
10:47:52.014 [4624.5388] <16> RequestInitialResources: MultiResReq.cpp:2268 resource request failed [150]
10:47:52.014 [4624.5388] <2> RequestInitialResources: Requesting cancellation from jobmgr
10:47:52.014 [4624.5388] <2> RequestInitialResources: returning
10:47:52.014 [4624.5388] <4> nbjm_media_request: Error from RequestMultipleResources, Master asprd111.aldc.att.com, error 150, resourceAllocated 0
10:47:52.014 [4624.5388] <4> nbjm_media_request: Shutdown requested
10:47:52.014 [4624.5388] <2> send_MDS_msg: MEDIA_DONE 0 -1289679684 0 *NULL* 0 0
10:47:52.014 [4624.5388] <2> packageBptmResourceDoneMsg: msg (MEDIA_DONE 0 -1289679684 0 *NULL* 0 0 )
10:47:52.014 [4624.5388] <2> packageBptmResourceDoneMsg: returns 7
10:47:52.014 [4624.5388] <2> JobInst::sendIrmMsg: returning
10:47:52.014 [4624.5388] <2> send_MDS_msg: Error from sendIrmMsg, Master asp.com, type 11, returned error -1
10:47:52.014 [4624.5388] <2> mm_terminate: EXITING with status 150

 

plz help

  • You won't believe this - got exactly the same error today...

    We added two new Windows media servers - identical specs.  Master (Solaris 10) and media servers (W2008 X64) all on NBU 7. Trying to do backups of itself as a test. One media server works fine, the other one fails with Status 10. We checked Performance meters - memory and cpu stays flat-lined at just above 0...

    I found this post: https://www-secure.symantec.com/connect/forums/ftl-couldnt-allocation-memory-status-10-allocation-failed

    that refers to this TN: http://www.symantec.com/docs/TECH29294

    I thought - we've got nothing to lose; let's create NOSHM.

    Guess what?? Backup goes through successful!!!

     

    rookie11 - If your media server is also the client, please try to create an empty file (with no extention) called NOSHM under ...\Veritas\NetBackup.

2 Replies

  • NetBackup status code: 10

    Message: allocation failed

    Explanation: The system memory allocation fails because of insufficient system memory available.

    A possible cause is that the system is overloaded with too many processes and not enough physical or virtual memory. Recommended action: Free up memory by terminating any unneeded processes that consume memory. Add more swap space or physical memory.

  • You won't believe this - got exactly the same error today...

    We added two new Windows media servers - identical specs.  Master (Solaris 10) and media servers (W2008 X64) all on NBU 7. Trying to do backups of itself as a test. One media server works fine, the other one fails with Status 10. We checked Performance meters - memory and cpu stays flat-lined at just above 0...

    I found this post: https://www-secure.symantec.com/connect/forums/ftl-couldnt-allocation-memory-status-10-allocation-failed

    that refers to this TN: http://www.symantec.com/docs/TECH29294

    I thought - we've got nothing to lose; let's create NOSHM.

    Guess what?? Backup goes through successful!!!

     

    rookie11 - If your media server is also the client, please try to create an empty file (with no extention) called NOSHM under ...\Veritas\NetBackup.