Solved

Backup Exec 11D. Problem with jobs hanging in queue state.

Posted on 2009-04-08
16
3,778 Views
Last Modified: 2013-12-01
Hello.

I am experiencing problems with jobs just hanging in queue. I have let it hang for about 30 minutes and then I cancel it. Then it just says cancel pending until I manually restart all the Backupexec services. Then the backupexec job engine service can't be stopped "in an ordarly fashion". But eventually I get it to stop and restart all the services.

The scenario is one W2K3 server with filebackup only to a HP Ulttrium LTO2 device.
I am using the Symantec drivers for this device. It locates it, can inventory and scan it without any problems, but when I start a job to it it will never run. The device and tape in the gui turns green so it seems to be doing something.
I have checked for any alerts in BE, checked that the tapes can be written to and checked for any unusual in the eventlog's on the server. Nothing yet that can explain this.

Note that this server is on a ship outside of India somewhere and I am sitting in Norway over RDP over a 256kb satelite link. Any more questions MAY take some time to respond to :)

Also. I have a NAS connected and the jobs will not run "backup to disk folder" either.
Anyone that have experienced this kind of thing?

Tom
0
Comment
Question by:Laksen83
  • 10
  • 5
16 Comments
 
LVL 14

Expert Comment

by:dmwynne
ID: 24103557
Has this ever worked?  Are these new tapes?

 When the job to tape hangs if you look at the tape drive in Backupexec so you can see the tape does it have a question mark in the label field?  I had something similar to what you described and it turned out to be some defective tapes.  These were brand new tapes I was using but there was something wrong with them.  They inventoried as well but hung when a job was run.
0
 
LVL 28

Expert Comment

by:honmapog
ID: 24110349
Does the backup to a "Backup to disk device" also hang in a queued state?
In the devices tab, try right-clicking the server name, checking "Pause Server" and then unchecking "Pause Server" again.

Make sure that in the Windows services, the "Removable Storage" service is stopped and the startup type is "Disabled".

If all that doesn't help, try the following:
* In Backup Exec, right-click the tape drive and uncheck Enable. Right-click again and choose Delete.
* Close the GUI
* Stop Backup Exec services.
* Run program files\symantec\backup exec\tapeinst.exe. Choose to "Use Symantec tape drivers for all devices". Also make sure to check "Delete entries for tape devices that are not available". run through the wizard.
* Start the services
* Start the GUI - try again.
0
 

Author Comment

by:Laksen83
ID: 24155520
Hello!

Sorry for the late answer. Been quite busy.
This also regards backup-to-disk .
I have tried to pause the server and unpause it again without success.
This is quite a strange problem. I am running the same scenario on 7 other vessels without any problems. 1 Vessel is on Backupexec 12.
Maybe I have to try to upgrade to BE 12 on this vessel also to see if that works.

But I will try the Removable Storage service tip and see if that has anything to do with it.

Tom :)
0
 

Author Comment

by:Laksen83
ID: 24155524
Oh,  and I have tried different tapes. :)

Tom
0
 

Author Comment

by:Laksen83
ID: 24155734
Still no luck with the "Removable Storage service" tip.
But, I will now let the job run, even it has a status of queued, for however long it takes before it "times out".

Tom
0
 

Author Comment

by:Laksen83
ID: 24155996
After 36 minutes the job fails with this :


V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine SEISERVER.
The media server will use the local agent to try to complete the operation.
Remote Agent not detected on \\SEISERVER.

AND

Backup- SEISERVERV-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
V-79-57344-65072 - The database server is not responding. Backup set canceled.
V-79-57344-65072 - The database server is not responding. Backup set canceled.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine SEISERVER.
The media server will use the local agent to try to complete the operation.
Remote Agent not detected on \\SEISERVER.

This is infact the server itself that is going to take backup OF itself. Why does it bother to search and try the REMOTE AGENT?

Tom
0
 
LVL 28

Expert Comment

by:honmapog
ID: 24161156
Backup Exec always connects to the remote agent service on a system it needs to back up. Even if it needs to back up itself.

Is the "Backup Exec Remote Agent" service started under the LocalSystem account?
Possibly something's corrupt in the Remote Agent component on the local system. Try upgrading to the latest service pack for 11d.
0
 

Author Comment

by:Laksen83
ID: 24165475
Hello.

Okay. Then that describes why it uses the remote agent locally :)

The Back Exec Remote Agen service is started.
I will try to upgrade the software by running live update but that will probably take QUITE SOME TIME due to the fact that this server is on a research vessel outside of India on a 256kb satelite link.

Tom :)
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 

Author Comment

by:Laksen83
ID: 24182492
No results on that.
Now the job has just hung for 1 hour. Will let it hang until it is timed out and post results.
Is there any way of seeing a detailed log of what is going on with BE ?
0
 
LVL 28

Expert Comment

by:honmapog
ID: 24186382
Run sgmon.exe - that will show you in detail what's going on. Post the corresponding sgmon.log file you'll fine in the logs subdirectory of Backup Exec.
0
 

Author Comment

by:Laksen83
ID: 24204226
I started the mon and let it run for about 1 night.

Here is the log.
SEISERVER---SGMon.log
0
 
LVL 28

Expert Comment

by:honmapog
ID: 24207567
I can only see one job starting: it was a job called Partial, which used a Backup to Disk device and not the tape drive you mentioned. Is that the job you're concerned about?

Unfortunately the log doesn't show that much. It definitely does not seem to be a device problem. The B2D media loaded without problems.
0
 

Author Comment

by:Laksen83
ID: 24212398
Hello.

The problem regards both B2D and Tape Device.
If it had only been one of the device's, troubleshooting this would be much easier.
This is really becoming a problem nad it is strange that no other vessels I have the exact same setup are getting these error's.
Also, prevoius to my attempt to fix this, BE has been tried to be reinstalled and installed another version (12) without success.
This is really getting onto my nerves! :(

Tom
0
 
LVL 28

Expert Comment

by:honmapog
ID: 24218391
Are you backing up multiple resources C: D:, System State, ... in the job?
If so, try changing the order of the resources and start the job with a different resource.

If you're using AOFO in the job, try turning it off to see if it makes a difference.

Try selecing the server through the "Windows Network" section of the selection tree in Backup Exec.
0
 

Author Comment

by:Laksen83
ID: 24303691
Hello.

I have tried excluding AOFO, changing the order of the backup and so on. Disabled all HP software (insight manager and so on).

I believe there is NOTHING else I can do.
I will go onboard the ship in June and check it out when I am sitting next to the server and backup unit and post my findings.
0
 

Accepted Solution

by:
Laksen83 earned 0 total points
ID: 25433280
I have not found any solution to this yet.
So I moved the SCSI card and installed BE on another server. Then it is working.
0

Featured Post

Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

Join & Write a Comment

Create your own, high-performance VM backup appliance by installing NAKIVO Backup & Replication directly onto a Synology NAS!
VM backup deduplication is a method of reducing the amount of storage space needed to save VM backups. In most organizations, VMs contain many duplicate copies of data, such as VMs deployed from the same template, VMs with the same OS, or VMs that h…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now