more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Final error category: Resource Errors I checked the account used to restore, works fine. Sorry, we couldn't post your feedback right now, please try again later. We are backing up to tape. Check This Out
No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Vision 2016 Vision I'm a bit stuck here and the customere would love to see his mail get restored. Email Address (Optional) Your feedback has been submitted successfully! I can see them both in BackExec as in Windows Explorer on my backup server.
No Yes Did this article save you the trouble of contacting technical support? Also is your exchange in cluster? Backup Exec (12.5) on a non-exchange server with agents on the others.
Browse other questions tagged exchange-2007 restore backupexec or ask your own question. If the server or resource no longer exists, remove it from the selection list. You can click on restore and check if you are able to see individual mailbox. V-79-57344-33932 Backup Exec I used a duplicate backup set to get the data from tape onto my server for faster restore.
Check to see if the Backup Exec Remote Agent Utility is advertising just the NETBIOS name of the server by opening the utility on the remote server and selecting the PUBLISHING V-79-57344-33932 - Unable To Attach To A Resource I would try posting this on the Symantec Backup Exec forums and contacting their support line. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Final error: 0xe000848c - Unable to attach to a re... https://vox.veritas.com/t5/Backup-Exec/Final-error-0xe000848c-Unable-to-attach-to-a-resource/td-p/355463 Solution: Verify that the password for the user account specified is correct.
Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Final Error: 0xe000848c View solution in original post 0 Kudos Reply 10 Replies Hi , 1 As per your sammy_perfect Level 5 12-02-2010 05:35 AM Options Mark as New Bookmark Subscribe Subscribe to Create/Manage Case QUESTIONS? Setup the restore of the database or individual (Exchange, Sharepoint and Oracle only) restore selections 4.
if it is on ws 2008 then edit the host file with the below configuration: ip address backup server name(host name) ip address backup server name(fqdn) ip address exchange server(host my response In particular see the section for Exchange. Unable To Attach To A Resource Backup Exec 2012 Baltimore N/A 12-02-2010 12:06 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I just stated getting this error? Backup Exec 0xe000848c Create/Manage Case QUESTIONS?
You can also look at my answer here for some other things to try. his comment is here The servers I use for this are configured as follows: Exchange 2007 latest SP, Windows 2003 R2 x64. Not the answer you're looking for? 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: 0xe000848c - Unable to attach to 0xe000848c Unable To Attach To A Resource Backup Exec
Make sure that this resource exists, and then try again." Solution Based upon the specified reasons the following solutions should be applied- Reason 1: The user account specified in Backup server, Windows 2008 R2 x64. http://www.symantec.com/business/support/index?page=content&id=TECH71780 0 Kudos Reply I have looked at that... http://popupjammer.com/unable-to/unable-to-find-resource-39-error-vm-39-in-any-resource-loader.html I have tried different tapes, which ended in the same result.
CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical This is what I normally use because it's faster. But I noticed something when I test credentials For the Storage Group it says resource not found... Unable To Attach To A Resource Backup Exec 2015 Make sure that all selected resources exist and are online, and then try again" when trying to restore Enterprise Vault Partition.
Visit http://www.symantec.com/docs/TECH130255 for more information about Logon Accounts. Reason 3: The resource that the backup/restore job is trying to attach to is offline or no longer exists. I tried running the restore from tape and I saw the same thing. Why are Stormtroopers stationed outside the Death Star near the turbolaser batteries adjacent to Bay 327? http://popupjammer.com/unable-to/unable-to-attach-file-galaxy-s6.html It is important to make sure of that beremote can start up because the service may not start up in some reason during R-SDR.
It's a single Exchange Standard server. Remove the RAWS agent from the Exchange server, and then reinstall it via a push-install from the media server. 0 Kudos Reply Removed the license, added it christiaang Level 3 11-17-2010 Edit the selection list properties, click the View Selection Details tab, and then remove the resource. Figure 1. Cause In the normal process, beremote is automatically started after the change Why is First past the post used in so many countries?
In the above scenario, the debug log of beremote is created in X:\ instead of C:\SDRLogs\. Solution If the service of Backup Exec Agent for Windows Servers is started manually Same result. Article:000034659 Publish: Article URL:http://www.veritas.com/docs/000034659 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 Thank You!
Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem "Final error: 0xe000848c - Unable to attach to a resource.