Welcome to your hub for enterprise data protection discussions. Learn more about recent changes to the VOX Community here.
Forum Widgets
Recent Discussions
status: 96: unable to allocate new media for backup
Hi, my backups are failing with the following error. Jun 11, 2025 5:01:02 PM - requesting resource LCM_HONETBKUPSRV-hcart3-robot-tld-0 Jun 11, 2025 5:01:02 PM - granted resource LCM_HONETBKUPSRV-hcart3-robot-tld-0 Jun 11, 2025 5:01:02 PM - started process RUNCMD (pid=1447098) Jun 11, 2025 5:01:02 PM - begin Duplicate Jun 11, 2025 5:01:03 PM - Info bpduplicate (pid=1447098) window close behavior: Suspend Jun 11, 2025 5:01:03 PM - Info bpduplicate (pid=1447098) The data-in-transit encryption (DTE) is enabled, as the DTE mode of the backup image is set to 'On' Jun 11, 2025 5:01:03 PM - Info bptm (pid=1447102) start Jun 11, 2025 5:01:03 PM - Info bptm (pid=1447102) Encrypting data-in-transit Jun 11, 2025 5:01:03 PM - started process bptm (pid=1447102) Jun 11, 2025 5:01:03 PM - Info bptm (pid=1447102) start backup Jun 11, 2025 5:01:03 PM - Info bpdm (pid=1447106) started Jun 11, 2025 5:01:03 PM - Info bpdm (pid=1447106) Encrypting data-in-transit Jun 11, 2025 5:01:03 PM - started process bpdm (pid=1447106) Jun 11, 2025 5:01:03 PM - Info bpdm (pid=1447106) reading backup image Jun 11, 2025 5:01:03 PM - Info bpdm (pid=1447106) using 30 data buffers Jun 11, 2025 5:01:03 PM - Info bpdm (pid=1447106) requesting nbjm for media Jun 11, 2025 5:01:03 PM - Info bptm (pid=1447102) Waiting for mount of media id K686L6 (copy 2) on server HONETBKUPSRV. Jun 11, 2025 5:01:03 PM - started process bptm (pid=1447102) Jun 11, 2025 5:01:03 PM - mounting K686L6 Jun 11, 2025 5:01:03 PM - Info bptm (pid=1447102) INF - Waiting for mount of media id K686L6 on server HONETBKUPSRV for writing. Jun 11, 2025 5:01:03 PM - requesting resource HONETBKUPSRV-hcart3-robot-tld-0 Jun 11, 2025 5:01:03 PM - requesting resource @aaaad Jun 11, 2025 5:01:03 PM - reserving resource @aaaad Jun 11, 2025 5:01:03 PM - resource @aaaad reserved Jun 11, 2025 5:01:03 PM - granted resource K686L6 Jun 11, 2025 5:01:03 PM - granted resource IBM.ULT3580-HH6.000 Jun 11, 2025 5:01:03 PM - granted resource HONETBKUPSRV-hcart3-robot-tld-0 Jun 11, 2025 5:01:03 PM - granted resource MediaID=@aaaad;DiskVolume=honetbkup;DiskPool=DataDomian;Path=honetbkup;StorageServer=172.16.11.5;MediaServer=HONETBKUPSRV Jun 11, 2025 5:01:03 PM - ended process 0 (pid=1447098) Jun 11, 2025 5:01:05 PM - begin reading Jun 11, 2025 5:01:52 PM - Info bptm (pid=1447102) media id K686L6 mounted on drive index 0, drivepath /dev/tape/by-path/pci-0000:01:00.0-fc-0x2002000e11167dfd-lun-0-nst, drivename IBM.ULT3580-HH6.000, copy 2 Jun 11, 2025 5:01:52 PM - Error bptm (pid=1447102) incorrect media found in drive index 0, expected K686L6, found TNK686, FREEZING K686L6 Jun 11, 2025 5:01:52 PM - current media K686L6 complete, requesting next media __ANY__ Jun 11, 2025 5:02:49 PM - Info bptm (pid=1447102) Waiting for mount of media id 1AOLL6 (copy 2) on server HONETBKUPSRV. Jun 11, 2025 5:02:49 PM - started process bptm (pid=1447102) Jun 11, 2025 5:02:49 PM - mounting 1AOLL6 Jun 11, 2025 5:02:49 PM - Info bptm (pid=1447102) INF - Waiting for mount of media id 1AOLL6 on server HONETBKUPSRV for writing. Jun 11, 2025 5:02:49 PM - granted resource 1AOLL6 Jun 11, 2025 5:02:49 PM - granted resource IBM.ULT3580-HH6.000 Jun 11, 2025 5:02:49 PM - granted resource HONETBKUPSRV-hcart3-robot-tld-0 Jun 11, 2025 5:03:41 PM - Info bptm (pid=1447102) media id 1AOLL6 mounted on drive index 0, drivepath /dev/tape/by-path/pci-0000:01:00.0-fc-0x2002000e11167dfd-lun-0-nst, drivename IBM.ULT3580-HH6.000, copy 2 Jun 11, 2025 5:03:41 PM - Error bptm (pid=1447102) incorrect media found in drive index 0, expected 1AOLL6, found 311AOL, FREEZING 1AOLL6 Jun 11, 2025 5:03:41 PM - current media 1AOLL6 complete, requesting next media __ANY__ Jun 11, 2025 5:04:36 PM - Error nbjm (pid=1442986) NetBackup status: 96, EMM status: No media is available Jun 11, 2025 5:04:36 PM - Info bptm (pid=1447102) EXITING with status 96 <---------- Jun 11, 2025 5:04:36 PM - Error nbjm (pid=1442980) NetBackup status: 96, EMM status: No media is available Jun 11, 2025 5:04:38 PM - Error bpdm (pid=1447106) media manager terminated by parent process Jun 11, 2025 5:04:43 PM - Error bpduplicate (pid=1447098) host HONETBKUPSRV backup id HOACSSRV19.IFL.NET_1749642400 read failed, media manager killed by signal (82). Jun 11, 2025 5:04:43 PM - Error bpduplicate (pid=1447098) host HONETBKUPSRV backupid HOACSSRV19.IFL.NET_1749642400 write failed, unable to allocate new media for backup, storage unit has none available (96). Jun 11, 2025 5:04:43 PM - Error bpduplicate (pid=1447098) Duplicate of backupid HOACSSRV19.IFL.NET_1749642400 failed, unable to allocate new media for backup, storage unit has none available (96). Jun 11, 2025 5:04:43 PM - Error bpduplicate (pid=1447098) Status = no images were successfully processed. Jun 11, 2025 5:04:43 PM - end Duplicate; elapsed time 0:03:41 Jun 11, 2025 5:04:43 PM - Error nbpem (pid=1443028) duplicate exited with status 191 (no images were successfully processed) no images were successfully processed(191) I have found an article related to this problem: https://www.veritas.com/support/en_US/article.100023592 According to this article I am changing the Max Mounts and Expiration Date of the Media ID but it is not changing.
Event Viewer Shows Errors TLD(0) io_open: using ndmp and Unload requested, but no unload
Hello Everyone, I got some peculiar issue with my Netbackup and this is getting worsen everyday. We have Netbackup 7.7.3 with Windows 2008 R2 64bit, using Storagetek SL500 Tape library with LTO4 Drives. This issue is the tpautoconf -report_disc shows missing device once in a every hour and again that will vanish on its own. The event viewer shows multiple errors like TLD(0) [16804] Unload requested, but no unload, drive x (xxxx 6) and TLD(0) io_open: using ndmp, this is happening for all the drives which are zoned in SAN switch. All the backups write and all the drives suddenly shows as down or down-tld. We have replaced the faulty drives, robotic arm, HBA card, Mutliple time zoning has been created at SAN switch. Network team confirmed that no issue at Network switch. Cables have been swapped but stil issue remains same. Even the NIC cards are also replaced. OS has no issues except with the Netbackup. KMA device hardware has been replaced and stil the issue remains same. I opened the case with Veritas however they say that the issue is at Hardware level, but still at what level the hardware is faulty we need to know to replace that part. Whenever we reboot tape library or power cycle the backups will run for a day or two and again the issue occurs. I am clueless at this point what else could be the issue. Your help will be greatly appreciated.
Image cleanup doesn't delete files
Hi, We have a problem with the Image Cleanup jobs. Each time it completes with the status "1: (1) The requested operation was partially successful." Detailed status has string "Warning bpdbm (pid=17018) nbdelete failed with status (12)" NetBackup doesn't delete files from staging folders anymore. bpdbm log file doesn't give me useful information. The only thing I see there that I think is related is: "<2> process_request: request complete: exit status 12 file open failed; query type: 72 (Q_IMAGE_DELETE)" High watermark 1%, low watermark 0% NetBackup is 10.3.0.1 All image files have ownership root:root. I tried to change user's ownership to a special account I set to run NetBackup, it didn't help. Also as far as I undersand NetBackup writes data to tapes, but just cannot clean the staging folders for some reasons. Will it be a bad idea to delete the files manually? Thank you.
Backup of SAP HANA with multitenant database container with netbackup.
Hi, I have one query? We have netbackup 7.7.2 and SAP HANA with multitenant database container. For one instance we have to do following configurations on SAP HANA studio: Create hdbbackint soft link from /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint to /usr/openv/NetBackup/bin/hdbbackint_script for every database instance. The parameter file (initSAP.utl) must be specified for data in the SAP HANA database instance configuration. To specify the parameter file, go to Instance->Configuration-> global.ini > data_backup_parameter_file. The parameter file (initSAP.utl) must be specified for logs in the SAP HANA database instance configuration. To specify backup using the parameter file, go to Instance->Configuration->global.ini-> log_backup_parameter_file. To specify backup using the backint file, go to Instance->Configuration->global.ini-> log_backup_using_backint->SYSTEM = true. My problem is that how to configure backup for multitenant database container (For multiple Instance ) We have cluster "Dev" with multitenant database container having 3 instance "Dev" "Quality" and "SystemDB" The problem is that DBA is telling that create hdbbackint soft link from /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint to /usr/openv/NetBackup/bin/hdbbackint_script . DBA inform us that,It is not possible due to Database instances in SAP HANA database will be in hidden mode. So we cannot create the links. Requesting you to help me in this. Server Details: Master Server. Client/Master = Master NetBackup Client Platform = PC-x64, WindowsXP NetBackup Client Protocol Level = 7.7.2 Product = NetBackup Version Name = 7.7 Version Number = 770000 NetBackup Installation Path = D:\Program Files\Veritas\NetBackup\bin Client OS/Release = Windows2008 6 SAP HANA Client . Client/Master = Client of IRBIDCQCSER001.irb.local NetBackup Client Platform = Linux, SuSE3.0.76 NetBackup Client Protocol Level = 7.7.2 Product = NetBackup Version Name = 7.7 Version Number = 770000 NetBackup Installation Path = /usr/openv/netbackup/bin Client OS/Release = Linux 3.0.101-0.47.67-default
Another duplication Question for Netbackup
Netbackup 10.5 Windows environment one primary server as master/media All Tapes are LTO6 (about 350 Archive Tapes with expiration set to Infinity most in the same volume pool but we do have tapes a few different volume pools). Currently Two Libraries - Scalar Quantum i500 robot type TLD (six fiber lto6 IBM tape drives in one library & four fiber Lto6 IBM drives in the other i500) SNIP of the LTO6 library Storage Units): We are obtaining quotes for a Quantum i6 robot type TLD containing LTO9 fibre IBM tape drives. (I know LtO9 drives cant READ or WRITE LTO6 tapes) This is my thinking and I need to know if Im on the right page sort of speak before we spend money on a tape generation that cant read or write our current tapes. Plan is to still continue to have the two i500 LTO6 libraries online when the new i6 LTO9 Library is bought and put online in the same netbackup primary master/media environment. Therefore we would have the two i500 LTO6 libraries and a brand new i6 LTO9 library As you see in the above snip the storage units are seen as a whole and not by drives (whether thats possible to see it by drives or not?). For example - currently daily backups/fulls are set to either use one library or the other library and also some policies have a storage unit group which it can use either library. I checked the compatibility doc/pdf and it appear a Quantum i6 with LTO9 IBM drives are compatible with Netbackup 10.5. Question Can I perform duplication via Netbackup Admin Console using the CATALOG | Action = Duplicate, and go from a LTO6 Archive tape (expiration date = infinity) that would be located in our LTO6 i500 quantum library and DUPLICATE the Image(s) to a LTO9 tape / drive in the new i6 quantum library we plan on buying containing LTO9 tape drives.? Once in the "Setup Duplication Variables" dialog box, the STORAGE UNIT (below SNIP) should be the library Im duplicating to or the destination - correct? - which would be the new LTO9 library. Is this doable /correct? Please advise SNIP: ALSO - For duplication does the new LTO9 tapes media type/density need to match the LTO6 or does that not matter? Im always a little confused here. Im thinking it should match. Thanks - BC
How to set notification about infected backups?
Hi All, I have implemented regular scanning of backup images. If the scan status is "Infected" I want to send a notification by e-mail. The notification could be scripted using REST API for sure. However is there any other option utilizing WebUI, Java GUI or Alta View? Thank you, LubosCatalog Backup & Decomissioning NetBackup Servers
We have an old Netbackup 7.1.0.4 master server and 2 media servers. The last backup and catalog backup performed using these servers was in late 2023. The hardware is EOL and needs to be decommissioned. How do we preserve the Netbackup catalog and databases just in case we would ever to need to recover data from previous databases without keeping the servers around. Is there a best practice or suggestions on how to accomplish this? Is it possible to copy off the catalog/databases to a storage array for use later in case a recovery is needed? Any thoughts or suggestions on keeping the data without keeping the servers around would be greatly appreciated. Thanks - JohnNetbackup 10.5 FETB Licensing enforcement
Hi I have a couple of questions regarding NetBackup 10.5/11 licensing. We’re currently running NetBackup 10.2 and are considering an upgrade to 10.5.1/11. I understand that perpetual licenses are still offered on a per front-end terabyte basis. Could you anyone please clarify if Veritas (or Cohesity, if applicable) will continue to offer perpetual licenses? Additionally, I've heard from a reseller that in NetBackup 10.5 onwards, if you exceed your licensed capacity, new backup jobs may be halted, even though existing backups remain available. Given that backup selections in NetBackup are mostly dynamic and can change from day to day also there is a possibility to suddenly have alot more TBs of data, I'm particularly concerned about how this enforcement mechanism works. If this claim is accurate, is there a grace period before backup operations stop, and how much time is typically provided to acquire additional licenses? Your insights would be incredibly helpful as we plan our upgrade strategy. Best regards, Mehrdad
Some media server has been "offline" with not reachable by master (6)
We have a small NBU 8.2 domain environment with one master, four media servers and also share one TL with 2 SSO TDs. All of them work fine except for one media server is offline with not reachable by master (6) via nbemmcmd listhosts. This problematic media server can be activated/online only for nearly 5 minutes every time, then it would be offline again. Notes: there is almost no any more errors/warnings in all the relevant logfiles including VxUL logs. # # # nbemmcmd -listhosts -display_server -machinename erp-fzyf -machinetype media -verbose|grep State MachineState = not reachable by master (6) # # # nbemmcmd -updatehost -machinename erp-fzyf -machinetype media -machinestateop set_master_server_connectivity -masterserver erpbak NBEMMCMD, Version: 8.2 Command completed successfully. # # # nbemmcmd -listhosts -display_server -machinename erp-fzyf -machinetype media -verbose|grep State MachineState = active for tape and disk jobs (14) # # # nbemmcmd -listhosts -display_server -machinename erp-fzyf -machinetype media -verbose|grep State MachineState = active for tape and disk jobs (14) # # # nbemmcmd -listhosts -display_server -machinename erp-fzyf -machinetype media -verbose|grep State MachineState = not reachable by master (6) # # This problematic media server appears with the machinestateopcode = <9> every 10 minutes. Notes: the other good media servers have no one such opcode 9 entry within the OID 144 ! # # vxlogview -p 51216 -o 144 -d all -t 06:00:00 > /tmp/nb_144.txt # # # grep erp-fzyf /tmp/nb_144.txt|grep -Ei "\<9\>"|tail 06/05/2025 14:57:26.478 [Debug] NB 51216 da 144 PID:738 TID:139688411072256 File ID:111 [No context] 1 [DeviceAllocatorImpl::updateMachineState] - MachineName = < erp-fzyf >, NetBackupVersion = < 0 >, MachineStateOpCode = < 9 > 06/05/2025 15:07:26.444 [Debug] NB 51216 da 144 PID:738 TID:139688404768512 File ID:111 [No context] 1 [DeviceAllocatorImpl::updateMachineState] - MachineName = < erp-fzyf >, NetBackupVersion = < 0 >, MachineStateOpCode = < 9 > 06/05/2025 15:17:26.554 [Debug] NB 51216 da 144 PID:738 TID:139688404768512 File ID:111 [No context] 1 [DeviceAllocatorImpl::updateMachineState] - MachineName = < erp-fzyf >, NetBackupVersion = < 0 >, MachineStateOpCode = < 9 > 06/05/2025 15:27:26.453 [Debug] NB 51216 da 144 PID:738 TID:139688404768512 File ID:111 [No context] 1 [DeviceAllocatorImpl::updateMachineState] - MachineName = < erp-fzyf >, NetBackupVersion = < 0 >, MachineStateOpCode = < 9 > 06/05/2025 15:37:26.474 [Debug] NB 51216 da 144 PID:738 TID:139688411072256 File ID:111 [No context] 1 [DeviceAllocatorImpl::updateMachineState] - MachineName = < erp-fzyf >, NetBackupVersion = < 0 >, MachineStateOpCode = < 9 > 06/05/2025 15:47:26.499 [Debug] NB 51216 da 144 PID:738 TID:139688404768512 File ID:111 [No context] 1 [DeviceAllocatorImpl::updateMachineState] - MachineName = < erp-fzyf >, NetBackupVersion = < 0 >, MachineStateOpCode = < 9 > 06/05/2025 15:57:26.438 [Debug] NB 51216 da 144 PID:738 TID:139689423341440 File ID:111 [No context] 1 [DeviceAllocatorImpl::updateMachineState] - MachineName = < erp-fzyf >, NetBackupVersion = < 0 >, MachineStateOpCode = < 9 > 06/05/2025 16:07:26.447 [Debug] NB 51216 da 144 PID:738 TID:139688404768512 File ID:111 [No context] 1 [DeviceAllocatorImpl::updateMachineState] - MachineName = < erp-fzyf >, NetBackupVersion = < 0 >, MachineStateOpCode = < 9 > 06/05/2025 16:17:26.534 [Debug] NB 51216 da 144 PID:738 TID:139688411072256 File ID:111 [No context] 1 [DeviceAllocatorImpl::updateMachineState] - MachineName = < erp-fzyf >, NetBackupVersion = < 0 >, MachineStateOpCode = < 9 > 06/05/2025 16:27:26.462 [Debug] NB 51216 da 144 PID:738 TID:139689423341440 File ID:111 [No context] 1 [DeviceAllocatorImpl::updateMachineState] - MachineName = < erp-fzyf >, NetBackupVersion = < 0 >, MachineStateOpCode = < 9 > # # # grep erp-hana1 /tmp/nb_144.txt|grep -Ei "\<9\>"|tail # # # grep erp-hana2 /tmp/nb_144.txt|grep -Ei "\<9\>"|tail # # # grep erp-test /tmp/nb_144.txt|grep -Ei "\<9\>"|tail #Register in rman catalog a client which was already registered
Hello, I have a new NBU domain, and I'm currently in the process of moving some clients from "old" domain to this new one. When I try to register oracle clients with rman catalog on the new domain, Netbackup is complaining that the client is not registered in the rman catalog. But when registering the same client in the "old" (ie current) domain, there is no issue I believe it's because when we first registered the client, it was configured with the current domain, and now it doesn't want to register it with the new domain because we can't register it twice. But DBAs are saying that we can't unregister the server from the rman catalog because they will lose their backups. Is there a way to register the client on the new domain ?
