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 the same version as that of the media server.

Reason 7:  The server name being advertised to the media server when a restore is attempted is different than it was originally in the Backup Exec Remote Agent Utility on the remote server when that machine was backed up.  For more information, review the following document:

'Unable to attach to a resource' may occur when a restore is attempted if the machine name does not match the name listed in the Backup Exec Remote Agent Utility when the backup was performed.    http://support.veritas.com/docs/306919

Unable to backup the Monitoring Database and Vault Store Database for Enterprise Vault (EV) using the EV agent in Backup Exec 12.0 if EV is configured using a DNS Alias for the backend SQL server.    http://support.veritas.com/docs/304374

Errors reported while backing or selecting some of Enterprise Vault (EV) resources under the EV agent in Backup Exec for Windows Servers when the resources are advertised using the DNS alias for the SQL server.    http://support.veritas.com/docs/317561

 http://support.veritas.com/docs/308893



Exchange Agent

 http://support.veritas.com/docs/325367

A Database restore of an Exchange 2007 database fails with "Unable to Attach" error.    http://support.veritas.com/docs/313401

An attempt to run a Granular Recovery Technology (GRT) backup of the Information Store to tape for Exchange 2007 running on a Windows 2008 server fails with an "Access Denied" error and a restore from disk fails with "Unable to attach".    http://support.veritas.com/docs/305539

An attempt to a restore Mailbox/Public Folder on an Exchange 2007 server running on a Windows 2008 from a Granular Recovery Technology (GRT) enabled Backup-To-Disk set fails with the error "Unable to attach to a resource."    http://support.veritas.com/docs/306689

"Final error: 0xe000848c - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again" when redirect restoring mailboxes or mailbox data to a different Exchange Server    http://support.veritas.com/docs/305824

A restore job to redirect Microsoft Exchange Mailbox Store data to a Recovery Storage Group on an alternate server in the same Administrative Group fails. The final error is "0xe000848c - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again."    http://support.veritas.com/docs/277633

Redirected Restore of an Exchange Mailbox Store to a Recovery Storage Group (RSG) created on a different server fails with an "Unable to attach to one of the drives" error.  http://support.veritas.com/docs/281163

Restore of Exchange 2007 Mailbox Restore fails with Error "Final error: 0xe000848c - Unable to attach to a resource.    http://support.veritas.com/docs/321543

The default BEMCMD backup script entries to backup Exchange resources inserts invalid selections into the selection list script for Exchange 2003 and 2007 servers & the backup fails with "Unable to attach"    http://support.veritas.com/docs/316951

Microsoft Exchange mailbox backup performed with Backup Exec fails with the error "Unable to attach to one of the drives" even though the mailboxes are successfully backed up.
 http://support.veritas.com/docs/261150


Oracle Agent

When backing up Oracle, "Unable to attach to a resource. Make sure that all selected resources exist and are online and then try again." occurs.  http://support.veritas.com/docs/312857

A backup job of an Oracle Failsafe Cluster database may fail if the Oracle cluster group is in an online state on a node other than the node where the MSCS cluster group is also online.    http://support.veritas.com/docs/287987

Unable to attach to one of the drives. An error is displayed when trying to back up a local or a remote Oracle server.

 http://support.veritas.com/docs/258645


Remote Agent for NetWare (RANW)

 http://support.veritas.com/docs/314552


When the same account is used for the Backup Exec for Windows Servers services and the System logon account, if a change is made to the user name/password for the Backup Exec services account, and the change is not made for the System logon account, NetWare data can only be restored to the original location through redirected restores.  http://support.veritas.com/docs/263042

When backing up a NetWare server and the local media server in the same job, using Backup Exec for Windows Servers, the job will fail with the error "Unable to attach to one of the drives" if the NetWare server is the first machine in the selection list.  http://support.veritas.com/docs/262497

When Backup Exec for Windows Servers attempts to back up a NetWare server via the Remote Agent for NetWare while using the System Logon Account, the backup job will fail with communication errors.  http://support.veritas.com/docs/263041

Resource credentials are not applied to the redirection path when restoring NetWare data using Backup Exec for Windows Servers
 http://support.veritas.com/docs/261835


Remote Agent for Windows Servers (RAWS)


'Unable to attach to one of the drives' error is reported while backing up remote system.
 http://support.veritas.com/docs/259874

When using Backup Exec during a backup/restore job of a remote computer behind a firewall, the error "Unable to attach to one of the drives" may occur.
 http://support.veritas.com/docs/258334

During a backup of a system, an "unable to attach to one of the drives" error is reported although the Remote Agent for Windows Server was successfully installed.
 http://support.veritas.com/docs/255187

During backup of remote systems through User-defined Selections, the job ends with the error: "Unable to attach to one of the drives."
 http://support.veritas.com/docs/250678


SQL Agent

 
While redirecting a SQL database, the error "Unable to attach to one of the drives" is returned in Backup Exec for Windows Servers.
 http://support.veritas.com/docs/257114