ERROR BUT DOES BACK UP ? V-79-57344-33932

[638501921]

Job Log: BEX_BOOYCOSVR1_00165.xmlJob Log for Linux Monthly

Completed status: Failed Expand AllCollapse All
Job Information
Job server: BOOYCOSVR1
Job name: Linux Monthly
Job started: 27 August 2005 at 11:00:04 AM
Job type: Backup
Job Log: BEX_BOOYCOSVR1_00165.xml


Drive and media mount requested: 2005/08/27 11:00:04 AM
Device and Media Information
Drive and media information from media mount: 2005/08/27 11:00:07 AM
Drive Name: Backup Monthly Linux
Media Label: B2D000100
Media GUID: {24abb724-6b01-4870-8c2b-0f7a045f2525}
Overwrite Protected Until: 2005/08/28 11:00:07 AM
Appendable Until: 2005/08/28 11:00:07 AM
Targeted Media Set Name: Iomega


Job Operation - Backup
Backup Options
Media operation - overwrite.
Hardware compression enabled.



Server - BOOYCOSVR2
Network control connection is established between 192.168.8.250:51658 <--> 192.168.8.1:10000
Network data connection is established between 192.168.8.250:51661 <--> 192.168.8.1:1025
Unable to attach to \\BOOYCOSVR2\booyco.
V-79-57344-33932 - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again.


Network control connection is established between 192.168.8.250:51658 <--> 192.168.8.1:10000
Network data connection is established between 192.168.8.250:51662 <--> 192.168.8.1:1026
Set Information - \\BOOYCOSVR2\


Backup Set Information
Family Name: "Media created 2005/08/20 11:00:03 AM"
Backup of "\\BOOYCOSVR2\ "
Backup set #2 on storage media #1
Backup set description: "Linux Monthly"
Backup Type: Full - Back Up Files - Reset Archive Bit


Verify completed on 2005/08/27 at 12:49:23 PM.
Verify Set Summary
Verified 102389 files in 3089 directories.
0 files were different.
Processed 46,275,091,759 bytes in 28 minutes and 43 seconds.
Throughput rate: 1537 MB/min





Job Completion Status
Job ended: 27 August 2005 at 12:49:24 PM
Completed status: Failed
Final error: 0xe000848c - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-33932

Errors
Click an error below to locate it in the job log
Backup- BOOYCOSVR2Unable to attach to \\BOOYCOSVR2\booyco.
V-79-57344-33932 - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again.

[Ajit_Kulkarni]

Hello,

Final Error Code: e000848c HEX (0xe000848c HEX) Final Error Description: "Unable to attach to a resource"
Final Error Category: Resource Errors
The possible reasons for the error and their solutions are given below:
Reason 1: The user account specified in Backup Exec to back up/restore the resource does not exist on the resource being backed up/restored.
Solution: Verify that the user account specified exists on the resource being backed up/restored. Edit the backup/restore job on the Job Setup tab and select Resource Credentials. Verify that the user account listed next to the resource exists on the resource being backed up/restored.
Reason 2: The password for the user account specified in Backup Exec to back up/restore the resource is incorrect.
Solution: Verify that the password for the user account specified is correct. In Backup Exec, edit the backup/restore job on the Job Setup tab, click Resource Credentials, and click Change. Select the "Backup Exec Logon Account" used to back up/restore the resource, and click Edit. Click Change password and retype the password for the user account. Make sure that the password entered matches the password for the user account on the resource being backed up/restored.
Reason 3: The resource that the backup/restore job is trying to attach to is offline or no longer exists.
Solution: Verify that the resource being backed up/restored exists and is online.
Reason 4: The Backup Exec Remote Agent for Windows Servers service is not started on the computer that the backup/restore job is trying to attach to.
Solution: Verify that the Backup Exec Remote Agent for Windows Servers service is started on the computer that is being backed up/restored.
Reason 5: The Backup Exec Remote Agent for Windows Servers is not present on the computer that the backup/restore job is trying to attach to.
Solution: Verify that the Backup Exec Remote Agent for Windows Servers is installed on the computer that is being backed up/restored. If the Backup Exec Remote Agent for Windows Servers is not installed, follow the instructions in the Backup Exec Administrator's Guide to install the agent.
Reason 6: The computer that the backup/restore job is trying to attach to has an older version of the Backup Exec Remote Agent.
Solution: Verify that the Backup Exec Remote Agent for Windows Servers installed on the computer that is being backed up/restored is from Backup Exec 9.0 (or later versions). The Backup Exec Remote Agent for Windows NT and Windows 2000 that shipped with Backup Exec 8.x is not compatible with Backup Exec 9.0 for Windows Servers.

Hope this helps you.

Regards


NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.