Please enter search query.
Search <product_name> all support & community content...
Article: 100020752
Last Published: 2012-10-09
Ratings: 0 4
Product(s): Backup Exec
Problem
Backup job hangs in a running state during a backup of remote servers
Solution
Issue:
A backup job will hang in a running status and the byte does not increase. The elapsed time will continue to increase. Typically when a job is in this state, the cancel job will hang as well.
Please Note:
The job activity may not report an accurate source. Please see document 323194 in related material for more information
How to Isolate and identify what server the job is hung on:
1. Check the active job log while the job is in a hung state and note the current 'source' and make note of the server name
2. Open the selection list for the job that is currently hung and look at the resource order
3. Make note the resources and the order starting at the server name from above (step 1) to the next server in line and the resources for that server (close list once recorded)
4. Open a restore job and check to see if ALL resources from the server in step 1 were backed up
5. If all resources on the server from step 1 appear to be backed up, the next server/resource in line (step 3) is most likely where the job is hung
*If the job is already canceled look at the end of the job log once the job is manually canceled or fails to see the last resource it may have been trying to connect to*
Solution:
There are various reasons for why a job can hang. Some solutions include;
1. Troubleshoot the resource itself (SQL instance, Exchange, System State, connection to the server, etc..)
(To further isolate this issue, attempt to create a new backup of flat files from the server identified if the resource is a database of some sort)
2. Try to restart the Backup Exec Remote Agent Service on the remote server(s). (The service may be in an inconsistent state causing the hang)
3. Re-install the latest version of RAWS onto the remote server