Thank you for your quick response.
Below is the diskpart information for one of the machines having problems.
Also attached is a backup log file.
I'll have to provide the information on Monday as our systems are being powered down for building maintenance right now.
However, I am certain that the server has two basic disk partitions only. It does have a remote access card with a virtual cd-rom drive usb device however. But thew KB doc says that an unsupported device cannot be the ONLY disk.
Hi saa515, Thank you for providing the requested information. Based on the information from your specific system, you are affected by the issue described in Technote 184002 since only a SAN (FIBRE) disk is present on the system. As stated in Technote 184002, a possible workaround is to add a local disk to the system. Since the system affected is Windows 2003 there are not many options besides installing a physical disk to the system since native Virtual Hard Disk is not available and externally created VHDs locally mounted with VHDMOUNT on Windows 2003 are also reported as SAN (FIBRE) disks. As described in Technote 189081, I have confirmed that this issue is actively being investigated. I will continue to investigate the other related issues that are being reported in this post since they appear to not be directly related to Technote 184002. With that said, I will be following up on the issue you are experiencing until a workaround or fix can be provided. Thank you for your patience.
Hi Dipesh, Thank you for the information. Based on the information your server does not appear to be directly affected by Technote TECH184002. I will follow up on the additional information that will be needed to proceed with the investigation. Thank you for your patience.
All 3 of my servers are physical servers, with physical disks installed. They are not connected to a SAN. Now that I understand the problem, do you have any ideas why 3 disks would be improperly identified in DISKPART? Or how I can change them? All 3 of my servers display "Fibre" when they all contain physical disks inside the server. These servers did not complete with this exception until we upgraded from BE 12.5 to BE 2012 a few weeks ago.
My server too shows up as having only a "fibre" disk when in fact it has physical disks. Specifically, this server has a Dell PERC 5/i with 3 SAS disks in a RAID5 array. We also did experience this issue before upgrading to BE2012.
Some more information on the server - below is the RAID controller information and config.
Hi All, In addition to the currently requested DISKPART and Backup Exec Job Log, please also include the output for the Microsoft Enumdisk Command Line Utility. Download Enumdisk1 from the Microsoft link: http://support.microsoft.com/kb/264203. Extract, execute, collect, and post the command line output from ENUMDISK. Thank you.
I've scoured the internet trying to find information as to why DISKPART and ENUMDISK would display incorrect bus types without any luck. There doesn't seem to be much information about this specific problem. Also, my servers are HP and others are experiencing problems with Dell too, so it doesn't seem specific to a certain hardware manufacturer.
Any update or any additional information needed to help resolve this?
Everything seems to have gone quiet here. Any progress?
I'm stuck waiting to for a fix to this - I need to test SDR working for a full backup and bare-metal restore before I can deploy in in production.
I am also stuck waiting for a fix. It is extremely important to get at least one SDR image of my critical servers ASAP. If this issue is still under investigation, could you please provide some suggestions on work arounds or other ways to ensure that I have valid backup data in the event of a failure?
If I can assist with any additional information please let me know.
It is an LSI Logic PCI-X Ultra320 controller that is being used for the C drive. No RAID or anything, just a simple spindle. My tape hardware is on an LSI SAS controller. Nothing connected via FC in this server at the moment, but it did have an idle FC HBA installed.
Windows Update was all happy. But the bottom of http://www.symantec.com/docs/TECH184002 mentions "Updating SCSI or Stroage Array Controller drivers can resolve the issue." so I gave it a try. I just right clicked on the HBA in device manager and let it update from the internet by itself. I believe that I had to reboot.
This solution probably doesn't work for everybody, but if the newer driver reports the disk as a different type, it could work for you. The only way to know is to try?
Here is the current output. I am assuming the "type" used to be "fibre" before I updated the driver.
DISKPART> detail disk
MAXTOR ATLAS15K_18SCA SCSI Disk Device
Disk ID: 301ACE26
Type : SCSI
Bus : 0
Target : 4
LUN ID : 0
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C w2003 NTFS Partition 17 GB Healthy System