Tape Drives - (no Media)
When the be15 services start my tape drives show a tape inside of them (see pic 1) Then a few mins later all of the drives go to status (No Media) from there any backups to tape just queue forever. Any backups to disk flow through just fine and complete. I have rebooted and resyned the server and drives. i have done my updates to BE. Rescanned the Drives, Inventory Slots, cleaned the drives. The Actual Robotic library doesnt show any issues on Drive 2-4. Errros in the ADAMM.log show the following when i attempted to do a backup and it was queued. 14200] 10/26/18 14:55:00.326 PvlDevice::DriveUtilThreadProc() - unable to determine media dismount slot. Drive = 1131 "Tape drive 0003" Slot = 4294967295 SysMediaID = 999999 MediaId = 999999 [12768] 10/26/18 14:55:28.382 PvlDevice::DriveUtilThreadProc() - unable to determine media dismount slot. Drive = 1130 "Tape drive 0002" Slot = 4294967295 SysMediaID = 999999 MediaId = 999999 [08972] 10/26/18 14:55:56.994 PvlDevice::DriveUtilThreadProc() - unable to determine media dismount slot. Drive = 1132 "Tape drive 0004" Slot = 4294967295 SysMediaID = 999999 MediaId = 999999 I was thinking about removing the drivers from windows, rebooting letting it reinstall. what is everyone elses thoughts?983Views0likes2CommentsBE2015 adding Enterprise Option but EO is BE2016
So I'm wanting to add Enterprise Option to BE 2015 for CASO but the link I get form Veritas with my entitlement number takes me to BE2016 Feature Pack 1... My issue is this .. I still have 2003 servers runing AD and this is why I cannot go to BE2016 yet. If I install this option is it going to take me to BE2016... Is there a link to previous version of Enterprise option? Do I just need the SLA key and enter it which "unlocks" the option in BE2015? Thanks in advanceSolved1.9KViews0likes3Commentscrcontrol.exe --processqueue never finishes?
Hi guys. We have had the issue that our Backup Exec dedup disk(approx 14TB) was close to running out of space. So after some investigation I found the running the "crcontrol.exe --processqueue" command, could do some cleanup. First time I ran it discovered there were about 44.000 tlog files in the queue folder, so I disabled all backup jobs to let it work on the files. Now A WEEK later, there are still files created in the folder, it has cleaned the folder several times, but it constantly seems to create more tlog files to work on, between 100-2000.. running "crcontrol.exe --processqueueinfo" keeps giving Busy=yes and pending=yes A few times have i caught pending=no, but the scheduled run at 12:20 and 00:20 seems to reset pending to "yes" The "crcontrol.exe --queueinfo" reports: total queue size: 12440670369 Am i supposed to stay patient and pray to god nothing happens? Or should i just start the backup jobs again? It seems it has cleaned up to make 3TB of available space. Any advice?1.9KViews0likes2Comments