Re: [Veritas-bu] bptm: read error on media id AB1234, Cannot allocate memory
On Tue, 17 Apr 2007, d w wrote: > Justin, >I'm not sure what platform you are running on or what version of NetBackup > - but if this is a unix master or media server, you may want to increase the > shmmax on the machine. > > On Solaris: > # grep shmmax /etc/system > set shmsys:shminfo_shmmax=<#value> > > To set these parameters on solaris, simply edit the /etc/system file and > change the value - then reboot. Or if you're good on mdb, you could use that. > > > On HP: > > 11.23: > # kcusage -l shmmax > Parameter: shmmax > Usage: 17904720 > Setting:<#value> > Percentage: 1.7 > > 11.xx: > # kmtune | grep shmmax > shmmax 0X400 > # > > > On linux: > #sysctl -a > > look for kernel.shmmax = <#value> > > Below is the technote on how to set these parameters in Linux: > http://support.veritas.com/docs/263755 > > > Also check out your size and number data buffers. If they are too large - > that might also be the cause of the problem. See the following technote for > information on those settings: > http://support.veritas.com/docs/183702 > Hope that helps. > > > > > - > Ahhh...imagining that irresistible "new car" smell? > Check outnew cars at Yahoo! Autos. Thanks, looking into this. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bptm: read error on media id AB1234, Cannot allocate memory
Justin, I'm not sure what platform you are running on or what version of NetBackup - but if this is a unix master or media server, you may want to increase the shmmax on the machine. On Solaris: # grep shmmax /etc/system set shmsys:shminfo_shmmax=<#value> To set these parameters on solaris, simply edit the /etc/system file and change the value - then reboot. Or if you're good on mdb, you could use that. On HP: 11.23: # kcusage -l shmmax Parameter: shmmax Usage: 17904720 Setting:<#value> Percentage: 1.7 11.xx: # kmtune | grep shmmax shmmax 0X400 # On linux: #sysctl -a look for kernel.shmmax = <#value> Below is the technote on how to set these parameters in Linux: http://support.veritas.com/docs/263755 Also check out your size and number data buffers. If they are too large - that might also be the cause of the problem. See the following technote for information on those settings: http://support.veritas.com/docs/183702 Hope that helps. - Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos.___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bptm: read error on media id AB1234, Cannot allocate memory
On Tue, 17 Apr 2007, bob944 wrote: >> 04/16/2007 19:04:26 - Warning bptm (pid=4728) read error on media id >> AB1234, drive index 1 reading header block, Cannot allocate memory >> >> Anyone ever get this when trying to a restore? How did you fix it? > > What buffer size was used to record the backup, how many buffers are you > using for the restore, and does the media server have enough shared > memory to handle it? > > The bptm log should show all the buffer allocations and shared-memory > allocation. Does that show a problem? Do you have > NUMBER_DATA_BUFFERS_RESTORE set? Remember, the restore is going to need > the number_buffers times the size_buffers as they exist on tape. > > For that matter, can the media server's tape device driver handle the > buffer size? Untested restores after buffer size tuning, especially > with Windows drivers, run into this all the time--though I don't > remember the error message. Also, restoring a foreign tape which has > bufsize that was fine on the original environment can run into the same > thing--yet another good reason not to use "hey, what's a good > SIZE_DATA_BUFFERS to use for LTO3?" advice. > > Workarounds: > o shm settings > o driver update > o is there an environment in which you can duplicate the image to disk > or tape with favorable buffer settings, and restore from the copy? > o dump the tape and see what the files and records look like--perhaps > it was overwritten > The environment's media servers were removed and new ones were put into place, all of the *BUFFER* settings should remain the same as that part is automated. I will check the bptm log. This is a Linux host. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bptm: read error on media id AB1234, Cannot allocate memory
> 04/16/2007 19:04:26 - Warning bptm (pid=4728) read error on media id > AB1234, drive index 1 reading header block, Cannot allocate memory > > Anyone ever get this when trying to a restore? How did you fix it? What buffer size was used to record the backup, how many buffers are you using for the restore, and does the media server have enough shared memory to handle it? The bptm log should show all the buffer allocations and shared-memory allocation. Does that show a problem? Do you have NUMBER_DATA_BUFFERS_RESTORE set? Remember, the restore is going to need the number_buffers times the size_buffers as they exist on tape. For that matter, can the media server's tape device driver handle the buffer size? Untested restores after buffer size tuning, especially with Windows drivers, run into this all the time--though I don't remember the error message. Also, restoring a foreign tape which has bufsize that was fine on the original environment can run into the same thing--yet another good reason not to use "hey, what's a good SIZE_DATA_BUFFERS to use for LTO3?" advice. Workarounds: o shm settings o driver update o is there an environment in which you can duplicate the image to disk or tape with favorable buffer settings, and restore from the copy? o dump the tape and see what the files and records look like--perhaps it was overwritten ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] bptm: read error on media id AB1234, Cannot allocate memory
04/16/2007 19:04:26 - Warning bptm (pid=4728) read error on media id AB1234, drive index 1 reading header block, Cannot allocate memory Anyone ever get this when trying to a restore? How did you fix it? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
