03-20-2020 05:44 AM
Hello,
I have the next error;(96) unable to allocate new media for backup, storage unit has none available
I have a one volumen active for pool semanal.
Regards
03-20-2020 06:34 AM
@robertoaxity
Please run available_media from cmd and output to .txt file.
Upload the txt file here.
e.g.
Assuming that you have C:\Temp folder:
<install-path>\veritas\netbackup\bin\goodies > available_media > C:\Temp\media.txt
03-20-2020 06:49 AM
Hello Marianne;
Thanks for your help me, i attached the txt
Regards
03-20-2020 07:09 AM
I see that there are 3 tapes in the robot that are 'available' in this pool:
Pool_semanal pool
EKH271 HCART3 NONE - - - - - AVAILABLE
EKH277 HCART3 NONE - - - - - AVAILABLE
H084L4 HCART3 TLD 0 5 - - - AVAILABLE
PCH078 HCART3 TLD 0 7 - - - AVAILABLE
PCH088 HCART3 TLD 0 6 - - - AVAILABLE
PCH091 HCART3 NONE - - - - - AVAILABLE
PCH093 HCART3 NONE - - - - - AVAILABLE
PCH099 HCART3 NONE - - - - - AVAILABLE
Please check output of this command to see why NBU is not considering these tapes:
vmquery -m H084L4
Do the same for PCH078 and PCH088.
As a matter of interest, Why is there an L4 label on H084L4? What drive type do you have?
If you can. please also put the rest of the AVAILABLE tapes back in the robot.
03-20-2020 11:11 AM
Marianne;
Attached vmquery, the library only have 8 slot.
Regards
03-20-2020 01:17 PM
03-22-2020 04:13 PM
OK, risking treading on Mariannes toes ...
Here are the common reasons (welll all I can think of) of the reasons for status 96.
1. Media has a expiration date set (seen in vmquery -m <Medicaid>
PCH088 media type: 1/2" cartridge tape 3 (24) barcode: PCH088L4 media description: Added by Media Manager volume pool: Pool_semanal (8) robot type: TLD - Tape Library DLT (8) robot number: 0 robot slot: 6 robot control host: SCSRVMA volume group: 000_00000_TLD vault name: --- vault sent date: --- vault return date: --- vault slot: --- vault session id: --- vault container id: - created: Fri 27 Jul 2018 02:08:44 PM BOT assigned: Thu 19 Mar 2020 09:43:33 AM BOT last mounted: Fri 20 Mar 2020 12:49:28 AM BOT first mount: Sat 25 Aug 2018 05:21:21 PM BOT expiration date: --- number of mounts: 150 max mounts allowed: --- status: 0x0
For this one tape shown above ' expiration date' is not set - so this is not the reason. You need to check the other tapes.
2. Max mounts is set ... on the tape above, you can see max mounts in not set, so this is fine, you need to check the other tapes.
3. The tape density is hcart3, does this match the drive type and the storage unit density / drive density. The tape and drive density must match.
4. Retention level ... By default, NBU will not write backups that have a different retention time to the same tape (it is not recommended to change this, you will use a lot more media). For example, if you have backups on a tape that have a 2 week expire time, you cannot write a backup that has a retention that is not 2 weeks.
NBU uses retention levels, so 2 weeks might be mapped to ret level 3, 1 month might be mapped to ret level 6. (They are changeable, apart from 9 which is always infinity, and I think 25, which is expire immediately). These can be seen with bpretlevel command of lookin in Host Properties > Master sever > Retention in the GUI.
available_media shows the retention level for each tape, which reflects the retention level of the backups written to that tape. If there are no tapes available that have the retention level of the backups you are trying to write, you will get status 96.
03-22-2020 11:14 PM
Hi Martin
3. The tape density is hcart3, does this match the drive type and the storage unit density / drive density. The tape and drive density must match.
The screenshot posted on Friday shows that the drive type is LTO6, density hcart3.
Media is also hcart3, but it has L4 label.
If these are LTO4 tapes, they cannot be used for backups in LTO6 drive.
03-23-2020 12:22 AM
Hi Marianne,
Apologies, I was struggling to look at all the details as was busy with something else, hence just posted the common causes with some explanation with the intention that maybe Robert could make some checks.
I would agree tha this usually comes down to density or retention level.
03-23-2020 04:59 AM
Marianne,
About LTO4 i dont change the tapes, i think the person who changes the tapes was wrong.
Regards
03-23-2020 05:16 AM
Okay, so the label on the tape is not a problem - the tape is getting used for backups.
When did you run available_media?
On Friday 20 March you posted available_media output that showed PCH088 as AVAILABLE, but bpmedialist showed that the same tape was used for backups on Thursday 19 March and that the tape is FULL.
Are you still experiencing status 96?
Then please run available_media again and post the new output.
It does not help if we look at old output.
03-23-2020 06:00 AM
Marianne,
Yes the error persist,
I attached the available file.
Regards
03-23-2020 06:13 AM
There is only one 'available' tape in the robot. NBU should use it for next backup that needs a tape in Pool_semanal pool : PCH078
Please eject some of the FULL tapes and put the AVAILABLE tapes in the robot.
Pool_semanal pool
EKH271 HCART3 NONE - - - - - AVAILABLE
EKH277 HCART3 NONE - - - - - AVAILABLE
EKH278 HCART3 NONE - - - - - AVAILABLE
H064L4 HCART3 NONE - - - - - AVAILABLE
PCH091 HCART3 NONE - - - - - AVAILABLE
PCH093 HCART3 NONE - - - - - AVAILABLE
PCH099 HCART3 NONE - - - - - AVAILABLE
If NBU is still not using PCH078, then please post output of vmquery and bpmedialist for this tape.
(vmquery -m PCH078
bpmedialist -m PCH078)
or else one command that will give us combination of both :
nbemmcmd -listmedia -mediaid PCH078
03-23-2020 06:52 AM
Marianne,
unfortunately due to the covid-19 we cannot change tapes until further notice, so thanks for your help, when i can change the tapes i'll let you know.
Regards
03-23-2020 07:04 AM
Just as long as you notify your management that no duplications will be possible and that disk storage will probably fill up because of this.
Wishing you all the best!
PS: The screen shot of media id PCH078 is not helping...