02-22-2011 01:07 AM
I am having a backup job for a production server remaining in a queued state indefinitely. Other backup jobs run fine suggesting that the problem is on the node side. I have tried the following steps with no result:
Both the media and node servers are running fine. No errors are reported on either one of the servers.
Media server = MS 2003 STD SP2 running BE 2010 R1 (Physical server)
Node server = MS 2003 STD SP2 running SQL (Virtual server running on ESX 4.0)
No db's directly being backed up onthe sql box, sql backups are made which BE backs up afterwards meaning no sql agent is required.
Could anyone suggest any other possible fix or nudge me in the right direction as to why this is happening. Any other suggestions to add to the above would be appreciated. I have thought about reinstalling the agent on the node but that might require a reboot which at this point I cant do due to the box being in production.
Solved! Go to Solution.
02-22-2011 09:07 PM
Thanks for feedback.There were no active alerts in BE other the ones for me restarting the the BE services.
Being a high profile box it was important that we got a backup of it last night. We were able the schedule a slot for rebooting it which resolved the issue.
02-22-2011 01:16 AM
Check the alerts tab for any active alert.
02-22-2011 01:22 AM
Try using a new backup job and backup a small directory from the problem. If possible, use a new media set.
02-22-2011 09:07 PM
Thanks for feedback.There were no active alerts in BE other the ones for me restarting the the BE services.
Being a high profile box it was important that we got a backup of it last night. We were able the schedule a slot for rebooting it which resolved the issue.