Final Error Category Resource Errors Backup Exec
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 backup exec a communications failure has occurred In CommunityCategoryBoardResourcesUsers turn final error: 0xe000fe30 - a communications failure has occurred. on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you a communications failure has occurred between the backup exec job engine and the agent for windows type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Final error category: Resource Errors backup exec ... VOX : Backup e000fe30 a communications failure has occurred backup exec and Recovery : Backup Exec : Final error category: Resource Errors backup exec ... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Final error category: Resource Errors backup exec v9.0 Ben_Schofield Level 2 09-12-2005 10:00 PM Options Mark as New Bookmark Subscribe Subscribe to
V-79-57344-34041
RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi there, I have been looking online though plenty of documentation but can seem to find a resolution for this problem. The backups are working (taking the data over to tape) but are showing as failied due to a resource error Which looks like this The O/S is Win2k server : Unable to attach to MILLBROOKNT\BKUPEXEC.Unable to attach to MILLBROOKNT\BKUPEXEC.with MILLBROOKNT being the name of the serverIf anyone can point me in the right direction I would appreciate the help Labels: 10.x and Earlier Backup and Recovery Backup Exec 0 Kudos Reply 2 Replies Re: Final error category: Resource Errors backup exec v9.0 Ajit_Kulkarni Level 6 09-13-2005 03:19 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello Ben,What type of backup you are taking ?Is it a local backup or a remote backup ?Please mention the exact error message alongwith the error code.RegardsNOTE : If we do not receive your reply withi
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing
0xe00084f9
Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom backup exec 2014 a communications failure has occurred Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 v-79-57344-65072 - the connection to target system has been lost. backup set canceled. 한국어 Português Español USA Site: Veritas Veritas PartnerNet Final error: 0xe00084f9 - A communications failure has occurred between the Backup Exec job engine and the https://vox.veritas.com/t5/Backup-Exec/Final-error-category-Resource-Errors-backup-exec-v9-0/td-p/43914 remote agent, occurs when backing up local media server resources to tape but not to disk. Article:000006536 Publish: Article URL:http://www.veritas.com/docs/000006536 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign https://www.veritas.com/support/en_US/article.TECH128475 in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Final error: 0xe00084f9 - A communications failure has occurred between the Backup Exec job engine and the remote agent, occurs when backing up local media server resources to tape but not to disk. Error Message Final error: 0xe00084f9 - A communications failure has occurred between the Backup Exec job engine and the remote agentFinal error category: Resource ErrorsV-79-57344-34029: Storage device "
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 https://www.veritas.com/support/en_US/article.TECH28737 Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet The error "A communications failure has occurred between the Backup Exec job engine and the remote agent" is reported during a backup of a remote server. Article:000026345 Publish: Article URL:http://www.veritas.com/docs/000026345 Support / Article Sign In Remember me backup exec Forgot Password? Don't have a Veritas Account? Create a 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 error "A communications failure has occurred between the Backup Exec job a communications failure engine and the remote agent" is reported during a backup of a remote server. Error Message A communications failure has occurred between the Backup Exec job engine and the remote agent. Job Completion Status Completed status: Failed Final error code: a00084f9 HEX Final error description: A communications failure has occurred between the Backup Exec job engine and the remote agent. Final error category: Resource Errors The error occurs during backups of remote computers. The error is generated when Backup Exec (tm) is missing a system logon account (Figure 1). UMI - V-79-57344-34041Figure 1 Cause The Backup Exec System Logon Account (SLA) on the Backup Exec server is either missing, corrupt or its credentials has changed. Solution Check if the Backup Exec System Logon Account (SLA) on the Backup Exec server is either missing or its credentials has changed. If neither is the case, create a new account and assign it the SLA role. Verify that the backup job in question is using the updated or newly created SLA before its next use. To check for a system logon account I