Queuing duplicate B2D jobs
Our CASO has a B2D folder set up on its local F: drive. Backup sets from the files contained within are duplicated to tape. CASO is running SP1, hotfixes 26 & 27. Note hotfix 27 (B2D pre-allocation) was installed AFTER this problem started.
Recently the jobs have started queuing. In a typical scenario, we will find that there are only one or 2 bkf files with an associated '.lck' file, but BE will show several B2D files in use, and thus start queuing jobs as it thinks the files are in use.
Running an Inventory operation updates the .cfg files, BE shows which bkf files are in use correctly, and the jobs start running again.
Question is, why isn't BE updating the B2D config files?
Error event is as follows...
Event Type:Error
Event Source:Backup Exec
Event Category:None
Event ID:33808
Date:03/10/2006
Time:04:55:19
User:N/A
Computer:BACKUP
Description:
An error occurred while processing a B2D command.
Changer: MoveMedium() Attempt to Dismount to Already Loaded Slot (B2DDrv3.3). Error=0
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLo...
Cheers,
Al.
Comments
Hi Al,
Please refer to this technote for the same:
Backup-to-Disk backup jobs stay "Queued" in the Activity Monitor and the job never runs.
http://support.veritas.com/docs/248709
==============
Hello,
As already stated, the .lck files are deleted, but BE still thinks the bkf files are in use.
Doesn't this point to a problem with the folders.cfg & changer.cfg files? We have this issue in 3 B2d folders, and 1 of them has had new cfg files created, yet we are still experiencing the same issue.
Cheers,
Al.
Hello,
This error may occurs if the folder has been deleted, moved, unshared or the mapped drive containing the Backup Folder has been disconnected. This can also happen if the folder has become inaccessible for any other reason, for example if the disk is in a full state and is offline.
1.Go to Devices tab
2. Make sure that backup To Disk folder is not showing as "Offline" or paused"
3. To resolve the error, make the folder accessible once again.
4.Once the folder has been moved back, recreated or re-mapped, right click on the backup folder, deselect the "Paused" state on the menu. The job will then run as intended. There is no need to resubmit the job.
5. Also try a Inventory of the B2D folder
Thank You,
Shweta
We now have an Inventory job running on the B2D folder every two hours. That seems to keep it happy. Why this should be necessary however, I do not know.
Would you like to reply?
Login or Register to post your comment.