Backup Exec 12 Error Communication Stalled
Contents |
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you communication stalled backup exec 2010 quickly narrow down your search results by suggesting possible matches as you type. Showing results
Communication Stalled Backup Exec 2010 R3
for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Inventory jobs stop with status of backup exec inventory stalled "Communication ... VOX : Backup and Recovery : Backup Exec : Inventory jobs stop with status of "Communication ... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark
Backup Exec Status Stalled
Subscribe Printer Friendly Page Inventory jobs stop with status of "Communication Stalled" Damien_Smith N/A 11-07-2011 08:58 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, I have Backup Exec 12 installed on a Windows Server 2003 SP2 machine. I have recently started to get errors when I run Inventory jobs. The job will start but after a few minutes will stop saying "Communication backup exec 2012 stuck on verify Stalled". I can't cancel the job and they usually continue in this state for about 15 minutes. When the job does finally stop the status is "Recovered". If I then open the properties of the job the error I see is "e00081d9 - The Backup Exec job engine system service is not responding". There are no error messages in the event logs. Labels: 12.x and Earlier Backup and Recovery Backup Exec Backup Exec (media server only) Windows 0 Kudos Reply 3 Replies Have you looked at - VJware Level 6 Employee Accredited Certified 11-07-2011 09:12 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Have you looked at - http://www.symantec.com/docs/TECH75749 0 Kudos Reply What sort of patch level are Tmy_70 Level 5 Partner Accredited Certified 11-08-2011 05:39 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content What sort of patch level are you running for BEWS 12?What SP do you have installed? Chances are that having the latest SP for BEWS will allow you to install these patches, or at least addresses issues that these patches create...something to read up on. Try to solved this by pausing and unpausing the server. open the BE GUI open the Devices tab right
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research
Backup Exec Stuck On Queued
Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet The Utility jobs in Backup Exec will not run until the server is paused/unpaused in the Backup Exec console. Article:000035211 Publish: Article URL:http://www.veritas.com/docs/000035211 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a https://vox.veritas.com/t5/Backup-Exec/Inventory-jobs-stop-with-status-of-quot-Communication-Stalled/td-p/434884 Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem The Utility jobs in Backup Exec will not run until the server is paused/unpaused in the Backup Exec console. Error Message Communication https://www.veritas.com/support/en_US/article.TECH63380 Stalled. Sometimes while running an Utility Job Operations on a device like (Inventory, Erase etc.), the job switches to "Communication Stalled" state and then ends in a "Recovered Status". Sometime they may just remain "Queued". It may also be observed that an unlock job invoked via Backup Exec for Windows Servers completes successfully, but the library's control panel reports "Doors locked by SCSI" on performing a "release magazine" operation to change the tapes. However the backup and restore operations may run without any problems. Cause The above mentioned problem can occur if for some reason the Backup Exec database has the ServerStatus flag set to indicate that the server is "Paused" but the Backup Exec console is unable to display that status in the Backup Exec User Interface. Solution This issue has been fixed in Backup Exec 2010 R3 SP1 For customers with Backup Exec 12.5, the above mentioned issue is now fixed by way of a hotfix. Please refer the Related Documents Section for more information about the hotfix. Note: A very limited number of customers are experiencing this issue even after installing the above mentioned
Case and Cooling Fetish CPU & Motherboard Technologia Mobile Computing Outpost Networking Matrix Other Hardware Agora Classifieds Ars DIY Forum (Name TBD!) Operating Systems & Software http://arstechnica.com/civis/viewtopic.php?t=83301 Battlefront Microsoft OS & Software Colloquium Linux Kung Fu Windows Technical https://community.spiceworks.com/topic/175698-backup-exec-communication-stalled Mojo Distributed Computing Arcana Macintoshian Achaia Programmer's Symposium The Server Room Ars Lykaion Gaming, Extra Strength Caplets The Lounge The Soap Box The Boardroom The Observatory Ars Help & Feedback Ars Subscription Member Areas Image Galleries Help with Symantec Backup Exec 12 36 posts MCSE_in_training Ars backup exec Scholae Palatinae Registered: Jan 30, 2008Posts: 631 Posted: Fri Jun 12, 2009 11:38 am Up until recently Backup Exec has worked pretty well. Last week I had to reboot the server. No backup job has run successfully since then!When the machine first boots, the backup exec job engine service isn't running. I manually start it. It starts fine. I can then start a backup job, it runs for about 25 communication stalled backup minutes or so then the status changes to "communication stalled". If I wait long enough it errors would with a communication problem with the media services. By the time that happens the backup exec job engine service has stopped again. This is the only error in the event log:Faulting application bengine.exe, version 12.0.1364.134, faulting module kernel32.dll, version 5.2.3790.4062, fault address 0x0000bee7.I've re-applied the settings for the user the service runs as. No change. I've tried running Live Update, it finds 2 updates and downloads them but it won't actually install them. Any ideas?I would have noticed this sooner but I've been busy getting our new file server up and running. Luckily I can run backups on the critical servers via NTBackup and dump them to the brand new empty file server. But that is a short term fix only. BulkRate Ars Scholae Palatinae Registered: Sep 9, 2003Posts: 740 Posted: Fri Jun 12, 2009 11:51 am At least in the Liveupdate bundled with 11D the LU session needed to be launched with the same credentials that the BackupExec services were running under in order to sucessfully apply. Be a shame if this hasn't yet been fixed, but hey...try it and see. molo Ars Legatus Legionis et Subscriptor Registered: Nov 10, 1999Posts:
Join Now Back story: Our tape drive failed recently, so I switched our backups to removable disks on another server. Backup Exec (10.1 rev 5629) runs on server A and backs up to disks on server B. Things went swimmingly well until...I tried a restore. Then BE comes back with an error message after 35 minutes and says "communication stalled" right before it kills the restore job and takes all the BE services offline. I did a test restore from several other disks and those worked fine, coming back within a minute on a restore of a file or two. The disk I'm restoring from seems fine. I can read it just fine in Windows. The only related post I can find here on SpiceWorks is a suggestion to check the timeout settings, although 35 minutes seems like plenty of time to talk to the drive. Setup: Server A: Windows 2003 Standard Server B: Windows 2008 Enterprise Backup Exec 10.1 rev 5629 Storage: Idealstor 4 bay unit using 2 TB drives If anyone has any suggestions I'm all eyes. Reply Subscribe RELATED TOPICS: Rant warning... I'm DONE with Backup Exec Symnantec Backup Exec Communication Stalled status Anyone still using Backup Exec?   14 Replies Mace OP NetworkNerd Dec 9, 2011 at 6:03 UTC If you run an inventory job on the drive giving you trouble, does it complete successfully? That would at least tell you if BE can recognize there are BE files on that drive. 0 Jalapeno OP Hennepin Dec 13, 2011 at 9:23 UTC It takes over an hour, but then inventory does indeed complete successfully. Trying a catalog against the disk though errors out after about 35 minutes. 0 Mace OP NetworkNerd Dec 17, 2011 at 1:02 UTC What if you try removing and re-installing the remote agent on server B? 0 Jalapeno OP Hennepin Dec 19, 2011 at 10:39 UTC Server B just operates as a depository for the data, so there isn't an agent running there. 0 Mace OP NetworkNerd Dec 19, 2011 at 10:59 UTC What if you manually copied the BE files inside your target backup to disk folder on server B to somewhere else (maybe a removable drive or even somewhere on server A)? Then, create a backup-to-disk folder that points to the new location, run an inventory job, and then try a restore. I wouldn't think that would change what happens, bu