Cannot run jobs to SPO (Storage Provisioning Option) due to invalid path after upgrading to Backup Exec 2010 R2

Problem

When using the base 2010 installation of BE with a Dell Storage Provisioning Option with a Virtual Disk (B2D).  The following issue was seen after upgrading to Backup Exec 2010 R2.



According to the adamm.log file, Build 2896 was in use up to a specified date in the log.  When Adamm was started after the upgrade, it was using build 4164.  That was also the time when the error :


[4904] 10/25/10 10:00:51.540 StorAr: Unexpected VDS result code 0x8007000d encountered.
was displayed just before the Adamm Log Stopped message.

On the next startup of Adamm at 10/25/10 10:04:47.979 there were iSCSI problems in adamm.log and:

[2936] 10/25/10 10:06:27.854 Backup Exec was unable to initialize and communicate with the device VIRTDISK 2 [VIRTDISKDevice          1.00] (The handle is invalid.).  Click the link below for more information on how to diagnose the problem.

And finally, the following in the Adamm.log file which is the first time that the Folder Path shows up with the corruption.

9999:0112:0002:0001  Device Name             "VIRTDISK 2"
                     Secondary Name          "\\?\Volume{88fefcb7-0b1c-4603-
a5bb-1ed884084dbd}"
                     Primary Inquiry         "VIRTDISKDevice          1.00"
                     Serial Number           "VIRTDISKDevice          
{A4E914E9-84BE-48DB-A3B8-7632D63FC309}"
                     Device Flags            SPO_B2D, SN(TYPE 0)
                     Device State            3, Online

                     Device IDs              1008, {A4E914E9-84BE-48DB-A3B8-
7632D63FC309}
                     Device Name             "VIRTDISK 2"
                     Folder Path             "F\?\Volume{88fefcb7-0b1c-4603-
a5bb-1ed884084dbd}\BEData\"
 

Cause

Due to a change in path for the SPO virtual device, the device cannot be accessed for jobs to be run.  This is found during device discovery.  The issue is located within the Backup Exec database.

Solution

 

This issue is resolved in Backup Exec 2010 R3 release.

This issue is resolved in Backup Exec 2010 R2 hotfix (154003).  See Related Documents.

 


Applies To

Backup Exec 2010 R2 (13.0.4164.0) with or without SP1 with Windows 2008

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)