Error Code 96 always encountered

[edgie]

Hi, just like to seek for your help regarding our probelm. We don't have successful backup in one of our policy previously using LTO3 tape. We encountered err 96, so we decided to replace the media to LTO4 and run in compress.  The data we need to backup is 1.5++ Tera that's why we decided to use LTO4 compress.

The backup did run but upon reaching 800gig to 900gig the error always occurs.

Kindly help... many thanks.

OS ver >> Windows Server 2008 R2 Enterprise

NBU ver >> 7.1

Job detailed status:

7/3/2013 6:15:08 PM - Info nbjm(pid=4880) starting backup job (jobid=10200) for client LN_APD_A01, policy LN_APD_A01, schedule FD03  
7/3/2013 6:15:08 PM - Info nbjm(pid=4880) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=10200, request id:{33CE683F-7995-4EBD-8390-2A0D6E684D6B})  
7/3/2013 6:15:08 PM - requesting resource sv5219-hcart-robot-tld-0
7/3/2013 6:15:08 PM - requesting resource sv5219.NBU_CLIENT.MAXJOBS.LN_APD_A01
7/3/2013 6:15:08 PM - requesting resource sv5219.NBU_POLICY.MAXJOBS.LN_APD_A01
7/3/2013 6:15:08 PM - granted resource sv5219.NBU_CLIENT.MAXJOBS.LN_APD_A01
7/3/2013 6:15:08 PM - granted resource sv5219.NBU_POLICY.MAXJOBS.LN_APD_A01
7/3/2013 6:15:08 PM - granted resource L3FD23
7/3/2013 6:15:08 PM - granted resource IBM.ULT3580-HH4.000
7/3/2013 6:15:08 PM - granted resource sv5219-hcart-robot-tld-0
7/3/2013 6:15:09 PM - estimated 0 Kbytes needed
7/3/2013 6:15:09 PM - Info nbjm(pid=4880) started backup job for client LN_APD_A01, policy LN_APD_A01, schedule FD03 on storage unit sv5219-hcart-robot-tld-0
7/3/2013 6:15:09 PM - started process bpbrm (5196)
7/3/2013 6:15:12 PM - Info bpbrm(pid=5196) LN_APD_A01 is the host to backup data from     
7/3/2013 6:15:12 PM - Info bpbrm(pid=5196) reading file list from client        
7/3/2013 6:15:12 PM - connecting
7/3/2013 6:15:18 PM - Info bpbrm(pid=5196) starting bpbkar32 on client         
7/3/2013 6:15:18 PM - connected; connect time: 00:00:06
7/3/2013 6:15:20 PM - Info bpbkar32(pid=0) Backup started           
7/3/2013 6:15:20 PM - Info bptm(pid=5956) start            
7/3/2013 6:15:20 PM - Info bptm(pid=5956) using 65536 data buffer size        
7/3/2013 6:15:20 PM - Info bptm(pid=5956) setting receive network buffer to 263168 bytes      
7/3/2013 6:15:20 PM - Info bptm(pid=5956) using 30 data buffers         
7/3/2013 6:15:20 PM - Info bptm(pid=5956) start backup           
7/3/2013 6:15:20 PM - Info bptm(pid=5956) backup child process is pid 2932.6600       
7/3/2013 6:15:20 PM - Info bptm(pid=5956) Waiting for mount of media id L3FD23 (copy 1) on server sv5219.
7/3/2013 6:15:20 PM - Info bptm(pid=2932) start            
7/3/2013 6:15:20 PM - mounting L3FD23
7/3/2013 6:15:56 PM - Info bptm(pid=5956) media id L3FD23 mounted on drive index 0, drivepath {4,0,2,0}, drivename IBM.ULT3580-HH4.000, copy 1
7/3/2013 6:15:56 PM - mounted; mount time: 00:00:36
7/3/2013 6:15:56 PM - positioning L3FD23 to file 1
7/3/2013 6:16:01 PM - positioned L3FD23; position time: 00:00:05
7/3/2013 6:16:01 PM - begin writing
7/3/2013 7:28:22 PM - Error bpbrm(pid=5196) from client LN_APD_A01: ERR - failure reading file: Lotus Notes:\D:\Notes\Data\corp\SUNLIFE\IICDocumentation.nsf (WIN32 1: Incorrect function. )
7/3/2013 8:09:34 PM - Error bpbrm(pid=5196) from client LN_APD_A01: ERR - failure reading file: Lotus Notes:\D:\Notes\Data\local\ACT\HKActDB.nsf (WIN32 1: Incorrect function. )
7/3/2013 9:58:12 PM - Error bpbrm(pid=5196) from client LN_APD_A01: ERR - failure reading file: Lotus Notes:\D:\Notes\Data\local\SLGFI\SLG-PDD.nsf (WIN32 1: Incorrect function. )
7/3/2013 11:38:37 PM - Error bpbrm(pid=5196) from client LN_APD_A01: ERR - failure reading file: Lotus Notes:\D:\Notes\Data\local\SYS-QAS\PH PDD.nsf (WIN32 1: Incorrect function. )
7/4/2013 12:44:16 AM - current media L3FD23 complete, requesting next resource Any
7/4/2013 12:45:01 AM - Info bptm(pid=5956) EXITING with status 96 <----------        
7/4/2013 12:45:10 AM - end writing; write time: 06:29:09
unable to allocate new media for backup, storage unit has none available(96)

Also attached the result of nbemmcmd -listmedia -mediaid L3FD23 command.

[Marianne · Accepted solution]

Hopefully you have bptm log folder enabled on the backup server?

If not create the folder under netbackup\logs and increase bptm logging level under Host Properties to 5.

Please post bptm log file (copy to bptm.txt) as File attachment after next failure. 

You should always ensure that you have more than on tape available for backups - not a good idea to only have one tape available. If tape driver reports EOM (or end-of-logical media), NBU will mark the tape as full and request a new tape. If no new tape is available, the entire backup will be discarded and reported as failed.

One more thing:

LTO4 capacity is listed as 800/1600GB.

Your capacity planning should always take native capacity into account - 800GB.

Amount of compression depends on compressibility of data as well as transfer rate.
My experience has been that hardware compression will be disabled if transfer rate is low in an attempt to keep tape drive streaming.

So, your solution is: have sufficient tapes available for backups.
For 1.6TB, have a minumum of 2-3 tapes available in the Volume Pool.

PS: Not a good idea to have Mon, Tues, Wed, etc pools.
Media Management will become a nightmare.

Have as little as possible Volume Pools and allow NBU to manage media.
 

[edgie]

Hi Marianne,

I think I have to go with what you've said

"So, your solution is: have sufficient tapes available for backups.
For 1.6TB, have a minumum of 2-3 tapes available in the Volume Pool.

PS: Not a good idea to have Mon, Tues, Wed, etc pools.
Media Management will become a nightmare."

I will just request for additional backup tapes.

Thanks a lot for the advise.