Netbackup error code 1. Any issue in restoring any files due to the errors?
At times, getting error code 1 for some backup and a rerun manually is successful. On some other days, it was able to completed successfully. No errors were seen. Any way to turn on more details logging to assist with troubleshooting?
the backup failed to back up the requested files(6)
Hi, Our enviroment we have master server version 8.1.1 in Windows Server 2012 R2 . Last week we are getting a error code 6 form NBU for one snapshot/backup operation with the following error: Nov 25, 2023 12:58:26 PM - Info nbjm (pid=6644) starting backup job (jobid=32857) for client vcs, policy vcs, schedule vcs_full Nov 25, 2023 12:58:26 PM - Info nbjm (pid=6644) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=32857, request id:{12AA4538-D7B1-4091-A24C-7CCEBB5B9ABC}) Nov 25, 2023 12:58:26 PM - requesting resource cifs1-stu Nov 25, 2023 12:58:26 PM - requesting resource srv-nbu01i.msa.com.NBU_CLIENT.MAXJOBS.vcs Nov 25, 2023 12:58:26 PM - requesting resource srv-nbu01i.msa.com.NBU_POLICY.MAXJOBS.vcs Nov 25, 2023 12:58:26 PM - granted resource srv-nbu01i.msa.com.NBU_CLIENT.MAXJOBS.vcs Nov 25, 2023 12:58:26 PM - granted resource srv-nbu01i.msa.com.NBU_POLICY.MAXJOBS.vcs Nov 25, 2023 12:58:26 PM - granted resource MediaID=@aaaah;DiskVolume=\\192.168.140.169\cifs1;DiskPool=cifs1;Path=\\192.168.140.169\cifs1;StorageServer=srv-nbu01i.msa.com;MediaServer=srv-nbu01i.msa.com Nov 25, 2023 12:58:26 PM - granted resource cifs1-stu Nov 25, 2023 12:58:26 PM - estimated 0 kbytes needed Nov 25, 2023 12:58:26 PM - begin Parent Job Nov 25, 2023 12:58:26 PM - begin VMware: Start Notify Script Nov 25, 2023 12:58:27 PM - Info RUNCMD (pid=32432) started Nov 25, 2023 12:58:27 PM - Info RUNCMD (pid=32432) exiting with status: 0 Operation Status: 0 Nov 25, 2023 12:58:27 PM - end VMware: Start Notify Script; elapsed time 0:00:01 Nov 25, 2023 12:58:27 PM - begin VMware: Step By Condition Operation Status: 0 Nov 25, 2023 12:58:27 PM - end VMware: Step By Condition; elapsed time 0:00:00 Nov 25, 2023 12:58:27 PM - begin VMware: Read File List Operation Status: 0 Nov 25, 2023 12:58:27 PM - end VMware: Read File List; elapsed time 0:00:00 Nov 25, 2023 12:58:27 PM - begin VMware: Create Snapshot Nov 25, 2023 12:58:27 PM - Info bpbrm (pid=35140) vcs is the host to backup data from Nov 25, 2023 12:58:27 PM - Info bpbrm (pid=35140) reading file list for client Nov 25, 2023 12:58:27 PM - Info bpbrm (pid=35140) start bpfis on client Nov 25, 2023 12:58:27 PM - Info bpbrm (pid=35140) Starting create snapshot processing Nov 25, 2023 12:58:27 PM - started process bpbrm (pid=35140) Nov 25, 2023 12:58:28 PM - Info bpfis (pid=40904) Backup started Nov 25, 2023 12:58:28 PM - snapshot backup of client vcs using method VMware_v2 Nov 25, 2023 12:58:29 PM - Info bpbrm (pid=35140) INF - vmwareLogger: Creating snapshot for vCenter server srv-vcenter02.dmzmsa.com, ESX host esx51.dmzmsa.com, BIOS UUID 4209005c-4ec2-29a8-b85b-64661575584b, Instance UUID 5009b489-ff24-bdce-eca6-95a8003f543a, Display Name vcs, Hostname trueconf.dmzmsa.com Nov 25, 2023 12:58:29 PM - Info bpbrm (pid=35140) INF - vmwareLogger: Connection state of virtual machine: connected. Nov 25, 2023 12:58:51 PM - end VMware: Create Snapshot; elapsed time 0:00:24 Nov 25, 2023 12:58:51 PM - Info bpfis (pid=40904) done. status: 0 Nov 25, 2023 12:58:51 PM - Info bpfis (pid=40904) done. status: 0: the requested operation was successfully completed Nov 25, 2023 12:58:51 PM - end writing Operation Status: 0 Nov 25, 2023 12:58:51 PM - end Parent Job; elapsed time 0:00:25 Nov 25, 2023 12:58:51 PM - Info nbjm (pid=6644) snapshotid=vcs_1700906306 Nov 25, 2023 12:58:51 PM - begin VMware: Policy Execution Manager Preprocessed Operation Status: 6 Nov 25, 2023 1:25:15 PM - end VMware: Policy Execution Manager Preprocessed; elapsed time 0:26:24 Nov 25, 2023 1:25:15 PM - begin VMware: Stop On Error Operation Status: 0 Nov 25, 2023 1:25:15 PM - end VMware: Stop On Error; elapsed time 0:00:00 Nov 25, 2023 1:25:15 PM - begin VMware: Delete Snapshot Nov 25, 2023 1:25:15 PM - started process bpbrm (pid=40192) Nov 25, 2023 1:25:16 PM - Info bpbrm (pid=40192) Starting delete snapshot processing Nov 25, 2023 1:25:16 PM - Info bpfis (pid=40116) Backup started Nov 25, 2023 1:25:24 PM - Info bpfis (pid=40116) done. status: 0 Nov 25, 2023 1:25:24 PM - end VMware: Delete Snapshot; elapsed time 0:00:09 Nov 25, 2023 1:25:24 PM - Info bpfis (pid=40116) done. status: 0: the requested operation was successfully completed Nov 25, 2023 1:25:24 PM - end writing Operation Status: 0 Nov 25, 2023 1:25:24 PM - begin VMware: End Notify Script Nov 25, 2023 1:25:24 PM - Info RUNCMD (pid=40884) started Nov 25, 2023 1:25:24 PM - Info RUNCMD (pid=40884) exiting with status: 0 Operation Status: 0 Nov 25, 2023 1:25:24 PM - end VMware: End Notify Script; elapsed time 0:00:00 Operation Status: 6 the backup failed to back up the requested files (6) Could you please help me to resolve this? and the error occurs for many time. Thank you, Mike AndrosovFull file list extracted from NetBackup Catalogue
Does anyone know if it is possible to generate an extracted list of all the files that have been backed up ever? I am looking to retire my NBU system, but want to identify items to be restored and moved to archive before I undertake the decom. Going through the restore procedure is a prohibitively slow process. Any advice is appreciated.
Hard Disk Amber light
Hi all, We had been having failed backup jobs every alternate date. We tried to reboot the NBU media server. Today, we checked that all our 12 hard disks are showing amber light. Is this some hardware failure? In the master server, we can see these error codes: 2106: disk storage server is down and 2074 EMM status: Disk volume is down.2106: disk storage server is down and 2074 EMM status: Disk volume is down.
We are using Netbackup 9.1.0.1 and NBU model 5240. We have 2 errors that appear under the Master Server (reports > problems) First error that appeared: PureDiskVolume is marked down. Storage server {rtmo} Second error: NBU Status: 2074 EMM status: Disk volume is down. From our failed disk backup, it states 2106: disk storage server is down. We also saw from the host properties > media server > vnetd proxy encountered an error. We have rebooted the media server and restarted the services on the master server. But the same issue has appeared again after 2 days. We did not make any changes other than enabling the duplication jobs for all backup 1 month ago. We have limited logs from the media and master server as the logging settings is set as 'Mininum logging'. Any clue on why this issue suddenly occured?
