When a back up job fails it may reference the wrong resource in the error message

Problem

When a back up job fails it may reference the wrong resource in the error message

Error Message

 

OR

Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.

Solution

Examples:

Example 1
Backup- Shadow?Copy?Components
V-79-57344-65149 - AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot provider error (0xE000FE7D): Access is denied.
(see the screen shot for this error in the error section)

In this example the actual failure was on the System State part of the backup, the backup of Shadow Copy Components was successful.

Example 2
Backup- SERVER1\SBSMONITORING
Unable to attach to SERVER1\SEPM.
V-79-57344-33932 - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.

In this example the actual failure was on the SERVER1\SEPM SQL instance, the backup of SERVER1\SBSMMONITORING SQL instance was successful.

Example 3
Backup- VRTSRV::\\SERVER1\Hyper-V?Virtual?Machine\SERVER2
AOFO: Initialization failure on: "VRTSRV::\\SERVER1\Hyper-V?Virtual?Machine\SERVER3".
Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

In this example the failure was on the backup of virtual machine SERVER3, the resource SERVER2 backup was successful.

This issue only occurs at transition to a new resource that is being backed up (i.e. C:, D:, System State, Virtual Machines, SQL Instances)

Workaround:
Review the details of the job log to determine the correct resource the failure occurred on.

Resolution:
The above mentioned issue has now been fixed by way of a hotfix. Please refer the Related Documents section for more information or click on the link www.symantec.com/docs/TECH128298

 
 

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)