Cartridge LTO 4 always frozen when using LTO 5 robot
Hi Guys,
i have a problem that i can't solved. i have 2 type robot machine, LTO 4 and LTO 5, but last month, my LTO 4 was failure and cannot be used anymore. so the company decided to use only LTO5 robot for any backup to tape. i have read that LTO 4 can be used for read and write in LTO5 machine, so i try to do backup my file to tape LTO4 using LTO5 robotic.
But, when i try to do backup, the job was failed because something that i don't understand, and when i see in my NetBackup 6.5, in media menu, all of my media that used to backup job is frozen. I have no idea to solve it, would you please to help me guys?
Thanks before.
03 Feb 17 14:56:49 - requesting resource netbkp-hcart-robot-tld-1 03 Feb 17 14:56:49 - requesting resource netbkp.NBU_CLIENT.MAXJOBS.em-int 03 Feb 17 14:56:49 - requesting resource netbkp.NBU_POLICY.MAXJOBS.Orcl-EPM-dbfnon1 03 Feb 17 14:56:50 - Error nbjm (pid=19821) NBU status: 96, EMM status: No media is available 03 Feb 17 15:06:50 - job 28428 was restarted as job 28428 unable to allocate new media for backup, storage unit has none available (96)
root@netbkp # ./nbemmcmd -listmedia -mediaid M018L4 NBEMMCMD, Version:6.5.6 ==================================================================== Media GUID: 4e026ace-e8a0-11e6-8000-8201d5312ddb Media ID: M018L4 Partner: - Media Type: HCART Volume Group: 000_00001_TLD Application: Netbackup Media Flags: 1 Description: Added by Media Manager Barcode: EPM018L4 Partner Barcode: -------- Last Write Host: NONE Created: 02/01/2017 10:03 Time Assigned: - First Mount: 02/01/2017 10:44 Last Mount: 02/02/2017 15:45 Volume Expiration: - Data Expiration: - Last Written: - Last Read: - Robot Type: TLD Robot Control Host: netbkp Robot Number: 1 Slot: 18 Side/Face: - Cleanings Remaining: - Number of Mounts: 3 Maximum Mounts Allowed: 0 Media Status: ACTIVE Kilobytes: 0 Images: 0 Valid Images: 0 Retention Period: - Number of Restores: 0 Optical Header Size Bytes: 0 Optical Sector Size Bytes: 0 Optical Partition Size Bytes: 0 Last Header Offset: 0 Adamm Guid: 00000000-0000-0000-0000-000000000000 Rsm Guid: 00000000-0000-0000-0000-000000000000 Origin Host: NONE Master Host: netbkp Server Group: Upgrade Conflicts Flag: Pool Number: 9 Volume Pool: Oracle-Kept_AtDC Previous Pool Name: - Vault Flags: - Vault Container: - Vault Name: - Vault Slot: - Session ID: - Date Vaulted: - Return Date: - ==================================================================== Command completed successfully.
bpexpdate only deletes information from NBU catalog. It does not format or do anything to the media. In other words, old backup data and the previous internal label is not wiped or overwritten. When the tape is about to be re-used, only backup data is overwritten, not the internal label.
When NBU sees another internal label that does not match the media-id, if freezes the media. This is perfectly normal as it may be media from another environment with valid data and someone has stuck another label on the tape.See Option 2 in my previous post:
Relabel the LTO4 media to match current Media ID Generation behaviour:
Unfreeze media, then use Label option to overwrite internal label. De-select 'Verify label' tick-box.