cancel
Showing results for 
Search instead for 
Did you mean: 

NONE/QUEUED Status

systematic92
Level 5

Morning,

 

We are using Backupexec 2010 R3 with the latest patches.

Ive created a job and assigned it to a policy used for other jobs (that do work). The policy is set to overwrite media.

I have checked if there was enough overwritable media in the drive and there was was. But to be extra sure, I moved  five LT05 tapes into the Scratch pool. I have checked the OPP and Append period for the media sets and they are set to 8 weeks and 10 hours.

The issue is the job starts but the 'Current Operation' status is at NONE and the 'Job Status' is QUEUED.

I've navigated over to the devices tab and I can see the device is IN USE and GREEN.

Any ideas what is going on please?

3 REPLIES 3

VJware
Level 6
Employee Accredited Certified

Is there any outstanding alert under the Alerts tab ? And ensure the option to automatically display new alerts is enabled from Tools - Options - Preferences.

 

systematic92
Level 5

No alerts or anything and I have rebooted the tape device and server to no avail. I started the debug monitor and found that the system cycles through the following text every 15 seconds:

 

 

BESERVER: [08/05/13 13:02:47] [6100]     05 AdammAdminBO::Execute() - hr = 0x0
PVLSVR:   [08/05/13 13:02:47] [6000]     PvlEntityDatabase::QueryEntity()
 
            ParentEntityType = MACHINE_ENTITY_TYPE
 
            ParentEntityGuid = {5-A444-47F6-85C7-0FEFEBCCD072}
 
            EntityType = DRIVE_ENTITY_TYPE
 
            EntityGuid = {00000000-0000-0000-0000-000000000000}
 
            EntityName = "
 
            EntityFlags = 0x00000000
PVLSVR:   [08/05/13 13:02:47] [6000]     PvlEntityDatabase::QueryEntity()
 
            ParentEntityType = MACHINE_ENTITY_TYPE
 
            ParentEntityGuid = {C5-A444-47F6-85C7-0FEFEBCCD072}
 
            EntityType = LIBRARY_ENTITY_TYPE
 
            EntityGuid = {00000000-0000-0000-0000-000000000000}
 
            EntityName = "
 
            EntityFlags = 0x00000000
PVLSVR:   [08/05/13 13:02:50] [3312]     AdammSession::MountMedia()
 
            Session = {823BD278-9D1F-4C64-AD08-5A33FC71EA4B}
 
            Drive = {1EECE941-0627-485A-BAA5-8C81753078B5}
 
            Slot = 0025
 
            Side = 0000
PVLSVR:   [08/05/13 13:02:50] [3312]     PvlDrive::MountMedia()
 
            Session = {823BD278-9D1F-4C64-AD08-5A33FC71EA4B}
 
            Drive = {1EECE941-0627-485A-BAA5-8C81753078B5}, "HP 0008"
 
            Slot = 0025
 
            Side = 0001
 
 
The last part interested me (SLOT 0025) so I went to the devices tab, expanded the backup server, expanded the robot (HP 0003) and finally clicked on SLOTS.
 
As you can see from the attached screenshot, the drive HP 0008 is IN USE but it keeps trying to attempt to use SLOT 25, which I presume is the same as SLOT 0025 (as per the debug output). 
 
From the attached screenshot, you can see that the tape assigned to SLOT 25 is not overwritable til June. It doesn't seem like the job wants to skip along to another tape/slot - how can I achieve this? Otherwise, it will constantly stay queued until June, I presume.
 
Thanks,
 

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...do any of your other jobs run currently?

Thanks!