Backup exec backup job failure
I directly ran a full backup, but the backup was always queued, and there was no rate. The rate was 0. After trying to restart all backup services, I ran the backup task again but there was still no rate. Moreover, I found that the backup service would automatically stop, causing the backup to hang inexplicably. The backup task cannot be continued. How to solve this situation?
nameless job
Dears, Need help in identifying this job We have this job runs every few days and keep running till we cancel it, it has no name but a job ID, NetBackup version 8.2 Windows cluster 2016 the jobs detailed status pasted below, Oct 17, 2023 8:08:39 PM - Info bptm (pid=24192) waited for empty buffer 246084 times, delayed 276048 times Oct 17, 2023 8:08:39 PM - positioning J71544 to file 13 Oct 17, 2023 8:08:39 PM - positioned J71544; position time: 0:00:00 Oct 17, 2023 8:08:39 PM - begin reading Oct 17, 2023 10:22:54 PM - Info bptm (pid=24192) waited for empty buffer 274738 times, delayed 297377 times Oct 17, 2023 10:22:54 PM - end reading; read time: 2:14:15 Oct 17, 2023 10:22:54 PM - positioning J71544 to file 14 Oct 17, 2023 10:22:54 PM - positioned J71544; position time: 0:00:00 Oct 17, 2023 10:22:54 PM - begin reading Oct 18, 2023 12:36:06 AM - Info bptm (pid=24192) waited for empty buffer 255246 times, delayed 289891 times Oct 18, 2023 12:36:06 AM - end reading; read time: 2:13:12 Oct 18, 2023 12:36:06 AM - positioning J71544 to file 15 Oct 18, 2023 12:36:06 AM - positioned J71544; position time: 0:00:00 Oct 18, 2023 12:36:06 AM - begin reading Oct 18, 2023 2:44:42 AM - Info bptm (pid=24192) waited for empty buffer 278977 times, delayed 300485 times Oct 18, 2023 2:44:42 AM - end reading; read time: 2:08:36 Oct 18, 2023 2:44:42 AM - positioning J71544 to file 16 Oct 18, 2023 2:44:42 AM - positioned J71544; position time: 0:00:00 Oct 18, 2023 2:44:42 AM - begin reading Oct 18, 2023 4:47:24 AM - Info bptm (pid=24192) waited for empty buffer 250872 times, delayed 275736 times Oct 18, 2023 4:47:24 AM - end reading; read time: 2:02:42 Oct 18, 2023 4:47:24 AM - positioning J71544 to file 17 Oct 18, 2023 4:47:24 AM - positioned J71544; position time: 0:00:00 Oct 18, 2023 4:47:24 AM - begin reading Oct 18, 2023 5:15:23 AM - current media J71599 complete, requesting next media Any Oct 18, 2023 5:15:23 AM - current media -- complete, awaiting next media Any. Waiting for resources. Reason: Drives are in use, Media server: jo00-nbk03, Robot Type(Number): TLD(6), Media ID: N/A, Drive Name: N/A, Volume Pool: duplication3-tapes, Storage Unit: jo00-nbk01-hcart-robot-tld-6, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A Oct 18, 2023 5:17:29 AM - current media -- complete, awaiting next media Any. Waiting for resources. Reason: Media is in use, Media server: jo00-nbk03, Robot Type(Number): TLD(6), Media ID: N/A, Drive Name: N/A, Volume Pool: duplication3-tapes, Storage Unit: jo00-nbk01-hcart-robot-tld-6, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A Oct 18, 2023 7:10:38 AM - Info bptm (pid=20028) Waiting for mount of media id J71599 (copy 2) on server jo00-nbk01. Oct 18, 2023 7:10:38 AM - started process bptm (pid=20028) Oct 18, 2023 7:10:38 AM - mounting J71599 Oct 18, 2023 7:10:38 AM - Info bptm (pid=20028) INF - Waiting for mount of media id J71599 on server jo00-nbk01 for writing. Oct 18, 2023 7:10:38 AM - granted resource J71599 Oct 18, 2023 7:10:38 AM - granted resource Drive221 Oct 18, 2023 7:10:38 AM - granted resource jo00-nbk01-hcart-robot-tld-6 Oct 18, 2023 7:11:27 AM - Info bptm (pid=20028) media id J71599 mounted on drive index 221, drivepath {7,0,7,0}, drivename Drive221, copy 2 Oct 18, 2023 7:11:27 AM - Info bptm (pid=20028) INF - Waiting for positioning of media id J71599 on server jo00-nbk01 for writing. Oct 18, 2023 7:41:47 AM - current media J71599 complete, requesting next media Any Oct 18, 2023 7:41:47 AM - current media -- complete, awaiting next media Any. Waiting for resources. Reason: Drives are in use, Media server: jo00-nbk03, Robot Type(Number): TLD(6), Media ID: N/A, Drive Name: N/A, Volume Pool: duplication3-tapes, Storage Unit: jo00-nbk01-hcart-robot-tld-6, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A Oct 18, 2023 7:43:25 AM - current media -- complete, awaiting next media Any. Waiting for resources. Reason: Media is in use, Media server: jo00-nbk03, Robot Type(Number): TLD(6), Media ID: N/A, Drive Name: N/A, Volume Pool: duplication3-tapes, Storage Unit: jo00-nbk01-hcart-robot-tld-6, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A Oct 18, 2023 11:05:58 AM - current media -- complete, awaiting next media Any. Waiting for resources. Reason: Media server is currently not connected to master server, Media server: jo00-nbk03, Robot Type(Number): TLD(6), Media ID: N/A, Drive Name: N/A, Volume Pool: duplication3-tapes, Storage Unit: jo00-nbk01-hcart-robot-tld-6, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A Oct 18, 2023 11:15:00 AM - current media -- complete, awaiting next media Any. Waiting for resources. Reason: Media is in use, Media server: jo00-nbk03, Robot Type(Number): TLD(6), Media ID: N/A, Drive Name: N/A, Volume Pool: duplication3-tapes, Storage Unit: jo00-nbk01-hcart-robot-tld-6, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A Oct 18, 2023 12:19:41 PM - granted resource J71626 Oct 18, 2023 12:19:41 PM - granted resource Drive220 Oct 18, 2023 12:19:41 PM - granted resource jo00-nbk01-hcart-robot-tld-6 Oct 18, 2023 12:19:42 PM - Info bptm (pid=20028) media id J71626 mounted on drive index 220, drivepath {6,0,9,0}, drivename Drive220, copy 2 Oct 18, 2023 12:19:42 PM - Info bptm (pid=20028) INF - Waiting for positioning of media id J71626 on server jo00-nbk01 for writing. Oct 18, 2023 1:57:41 PM - Info bptm (pid=24192) waited for empty buffer 359963 times, delayed 1960404 times Oct 18, 2023 1:57:41 PM - end reading; read time: 9:10:17 Oct 18, 2023 1:57:41 PM - positioning J71544 to file 18 Oct 18, 2023 1:57:41 PM - positioned J71544; position time: 0:00:00 Oct 18, 2023 1:57:41 PM - begin reading Oct 18, 2023 4:36:14 PM - Info bptm (pid=24192) waited for empty buffer 377853 times, delayed 390237 times Oct 18, 2023 4:36:14 PM - end reading; read time: 2:38:33 Oct 18, 2023 4:36:14 PM - positioning J71544 to file 19 Oct 18, 2023 4:36:14 PM - positioned J71544; position time: 0:00:00 Oct 18, 2023 4:36:14 PM - begin reading Oct 18, 2023 5:13:23 PM - Info bptm (pid=24192) waited for empty buffer 86264 times, delayed 88900 times Oct 18, 2023 5:13:23 PM - end reading; read time: 0:37:09 Oct 18, 2023 5:13:23 PM - Info bptm (pid=24192) Waiting for mount of media id J71547 (copy 1) on server JO00-NBK01. Oct 18, 2023 5:13:23 PM - started process bptm (pid=24192) Oct 18, 2023 5:13:23 PM - mounting J71547 Oct 18, 2023 5:13:23 PM - Info bptm (pid=24192) INF - Waiting for mount of media id J71547 on server JO00-NBK01 for reading. Oct 18, 2023 5:13:23 PM - current media J71544 complete, requesting next media Drive217:J71547 Oct 18, 2023 5:13:23 PM - granted resource J71547 Oct 18, 2023 5:13:23 PM - granted resource Drive213 Oct 18, 2023 5:13:51 PM - mounted J71547; mount time: 0:00:28 Oct 18, 2023 5:13:51 PM - Info bptm (pid=24192) J71547 Oct 18, 2023 5:13:51 PM - Info bptm (pid=24192) INF - Waiting for positioning of media id J71547 on server JO00-NBK01 for reading. Oct 18, 2023 5:13:51 PM - positioning J71547 to file 1 Oct 18, 2023 5:13:51 PM - positioned J71547; position time: 0:00:00 Oct 18, 2023 5:13:51 PM - begin reading Oct 18, 2023 7:55:06 PM - Info bptm (pid=24192) waited for empty buffer 373954 times, delayed 392326 times Oct 18, 2023 7:55:06 PM - end reading; read time: 2:41:15 Oct 18, 2023 7:55:06 PM - positioning J71547 to file 2 Oct 18, 2023 7:55:06 PM - positioned J71547; position time: 0:00:00 Oct 18, 2023 7:55:06 PM - begin reading Oct 18, 2023 10:31:12 PM - Info bptm (pid=24192) waited for empty buffer 413360 times, delayed 424429 times Oct 18, 2023 10:31:12 PM - end reading; read time: 2:36:06 Oct 18, 2023 10:31:12 PM - positioning J71547 to file 3 Oct 18, 2023 10:31:12 PM - positioned J71547; position time: 0:00:00 Oct 18, 2023 10:31:12 PM - begin reading Oct 19, 2023 1:09:30 AM - Info bptm (pid=24192) waited for empty buffer 390542 times, delayed 402798 times Oct 19, 2023 1:09:30 AM - end reading; read time: 2:38:18 Oct 19, 2023 1:09:30 AM - positioning J71547 to file 4 Oct 19, 2023 1:09:30 AM - positioned J71547; position time: 0:00:00 Oct 19, 2023 1:09:30 AM - begin reading Oct 19, 2023 3:35:33 AM - Info bptm (pid=24192) waited for empty buffer 357286 times, delayed 373167 times Oct 19, 2023 3:35:33 AM - end reading; read time: 2:26:03 Oct 19, 2023 3:35:33 AM - positioning J71547 to file 5 Oct 19, 2023 3:35:33 AM - positioned J71547; position time: 0:00:00 Oct 19, 2023 3:35:33 AM - begin reading Oct 19, 2023 5:53:41 AM - current media J71626 complete, requesting next media Any Oct 19, 2023 5:56:47 AM - Info bptm (pid=20028) EXITING with status 96 <---------- Oct 19, 2023 5:56:47 AM - Info bptm (pid=24192) EXITING with status 0 <---------- Oct 19, 2023 5:56:47 AM - Error nbjm (pid=27972) NBU status: 96, EMM status: No media is available client process aborted (50)
Back up is slower than usual
We are using Symantec backup exec15 and when we run the back up, It is slower than usual, In job history, previous Job rate is 1000MB/min but now it became 500mb/min , please advise what to do to increase the performance. it was taking only 7 hours to do the process before but now it is taking 1 day already. Thanks in advance!
Migrating BE 2014 to BE 21 on a new server problems
We are currently running Backup Exec 2014 on a Windows Sever 2008 R2. We need to decommission that server and migrate BE to a new Windows Server 2016. We are aware that BE 2014 will not run on Server 2016, so we are looking for the most effective/supported method of migrating. We’ve tried the Migration Assistant, but that will only go from Be 2014 to BE 20. Having Installed version 20, the migration fails on source database credentials and incompatibility. Trying the manual migration method, the copying of the database via beutility appears to work but then errors when attempting to start the services, leaving us with an inoperative system. We tried installing BE 2016 but that fails to open. We’ve tried all installs/migrations etc through various administrator/domain admin accounts and get the same errors each time. Have we any options left? Is there a recommended\foolproof method of migrating our current Backup exec catalogues\data\jobs etc to a more up-to-date and supported version compatible with Windows Server 2016? Has anyone else attempted this, and found any workarounds?Emergency Help
Dears Kindly Your Experience to Provide Solution For Below Contiguous Case from 25 days Some one From Our Company Tried Backup Exec 2014 as trial and make backup over tape then cyber attacj happened erase all Server even backup exec server now we make new installation of one server and install backupexe then try to restore it say in restore server not trusted and ask for credential and dont know what credential so can help to restore without this password or what suggestion
I am looking better backup solution for Windows 7 and XP based old machine.
Please suggest, I am looking backup solution for Windows 7 and XP based old physicals machine. Where I can backup the system and as well recover the backup. If required I can backup full system image restore the image also if need I can take file and folder backup too. Please suggest the right solution for Windows 7 and XP based physical system.
