cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

After Larry's success, I had

After Larry's success, I had a look at my servers. They are Dell 2900s and T610s. The 2900s at least have the most current firmware and drivers for their PERC 5/i RAID controllers, so this solution does not help me. Marcusolini, is there anything further we can check? Richard
Highlighted

I looked at my HP E200i

I looked at my HP E200i controller with firmware version 1.84. There is a newer version 1.86 but it was released to correct the issue below.

"Fixed an issue where logical drives were not being detected during POST or reboot on the HP Smart Array E200i controller with firmware version 1.80, 1.82 or 1.84."

I doesnt look like it would resolve the issue we are experiencing. Besides, the idea of upgrading the RAID controller firmware without an SDR image is just asking for trouble.

 

Marcusolini,  Suggestions?

 

Scott

Highlighted

Hi All,  An initial

Hi All,  An initial workaround fix has been identified, implemented, and unit tested.   The formal hot-fix release process will require more time before the hot-fix is publically available.  Another means to provide this hot-fix sooner is being discussed.  In the meantime, another possible manual temporary workaround, for Windows 2008-R2 only, is to create and initialize a native virtual hard disk (VHD) with a small volume (no drive letter) using the Disk Management console.  At the moment, there is no alternate workarounds for Windows 2003, 2003-R2, and 2008.  Thank you everyone for your continued patience.

Highlighted

Hi Marcusolini,   Thanks for

Hi Marcusolini,

 

Thanks for your above response but creating a VHD disk has not fixed the issue. Do you have a date yet for the Hotfix release?

 

I have multiple servers that only have SAN attached disk & i am getting this error on all of them, meaning i cant get a full successful backup to perform SDR.

Your response would be much appreciated. wink

 

 

Highlighted

Hi Dr Hu,  When able, can you

Hi Dr Hu,  When able, can you please provide the DISKPART and ENUMDISK output from these servers for review?  Thank you.

Highlighted

Hi Marcusolini,   Thankyou

Hi Marcusolini,

 

Thankyou for your response, info requested is below.

 

 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Users\Administrator.IMGROUP>diskpart
 
Microsoft DiskPart version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: CONNECTIONSDB2
 
DISKPART> list disk
 
  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          250 GB      0 B
  Disk 1    Online         1983 GB  1024 KB
  Disk 2    Online         1024 MB  1022 MB
 
DISKPART> select disk 0
 
Disk 0 is now the selected disk.
 
DISKPART> detail disk
 
IBM 1726-4xx  FAStT  Multi-Path Disk Device
Disk ID: 693E70E5
Type   : FIBRE
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : UNAVAILABLE
Current Read-only State : No
Read-only  : No
Boot Disk  : Yes
Pagefile Disk  : Yes
Hibernation File Disk  : No
Crashdump Disk  : Yes
Clustered Disk  : No
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0         System Rese  NTFS   Partition    100 MB  Healthy    System
  Volume 1     C                NTFS   Partition    249 GB  Healthy    Boot
 
DISKPART> select disk 1
 
Disk 1 is now the selected disk.
 
DISKPART> detail disk
 
IBM 1726-4xx  FAStT  Multi-Path Disk Device
Disk ID: 143D4A1C
Type   : FIBRE
Status : Online
Path   : 0
Target : 1
LUN ID : 1
Location Path : UNAVAILABLE
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 2     D   DB2_DATA     NTFS   Partition   1983 GB  Healthy
 
DISKPART> select disk 2
 
Disk 2 is now the selected disk.
 
DISKPART> detail disk
 
Msft Virtual Disk SCSI Disk Device
Disk ID: 31F9AF5F
Type   : Virtual
Status : Online
Path   : 0
Target : 0
LUN ID : 1
Location Path : UNAVAILABLE
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No
 
There are no volumes.
 
DISKPART> exit
 
Leaving DiskPart...
 
C:\Users\Administrator.IMGROUP>cd..
 
C:\Users>cd..
 
C:\>cd enum,
The system cannot find the path specified.
 
C:\>cd enum
 
C:\ENUM>enumdisk
Properties for Device 1
 
Device ID: SCSI\DiskIBM_____1726-4xx__FAStT_0617
 
Adapter Properties
------------------
Bus Type       : FIBRE
Max. Tr. Length: 0x2000000
Max. Phy. Pages: 0xff
Alignment Mask : 0x0
 
Device Properties
-----------------
Device Type     : Direct Access Device (0x0)
Removable Media : No
Vendor ID       : IBM
Product ID      : 1726-4xx  FAStT
Product Revision: 0617
Serial Number   : SF71601025
 
Inquiry Data from Pass Through
------------------------------
Device Type: Direct Access Device (0x0)
Vendor ID  : IBM
Product ID : 1726-4xx  FAStT
Product Rev: 0617
Vendor Str :
 
 
 
Properties for Device 2
 
Device ID: SCSI\DiskIBM_____1726-4xx__FAStT_0617
 
Adapter Properties
------------------
Bus Type       : FIBRE
Max. Tr. Length: 0x2000000
Max. Phy. Pages: 0xff
Alignment Mask : 0x0
 
Device Properties
-----------------
Device Type     : Direct Access Device (0x0)
Removable Media : No
Vendor ID       : IBM
Product ID      : 1726-4xx  FAStT
Product Revision: 0617
Serial Number   : SX92604572
 
Inquiry Data from Pass Through
------------------------------
Device Type: Direct Access Device (0x0)
Vendor ID  : IBM
Product ID : 1726-4xx  FAStT
Product Rev: 0617
Vendor Str :
 
 
 
Properties for Device 3
 
Device ID: SCSI\DiskIBM_____1726-4xx__FAStT_0617
 
Adapter Properties
------------------
Bus Type       : Scanner Device
Max. Tr. Length: 0x800000
Max. Phy. Pages: 0xffffffff
Alignment Mask : 0x1
 
Device Properties
-----------------
Device Type     : Direct Access Device (0x0)
Removable Media : No
Vendor ID       : Msft
Product ID      : Virtual Disk
Product Revision: 1.0
 
Inquiry Data from Pass Through
------------------------------
Device Type: Direct Access Device (0x0)
Vendor ID  : Msft
Product ID : Virtual Disk
Product Rev: 1.0
Vendor Str :
 
 
 
Properties for Device 4
 
Device ID: SCSI\DiskMsft____Virtual_Disk____1.0_
 ***  End of Device List  ***
 
C:\ENUM>
Highlighted

Marcusolini,   Any updates on

Marcusolini,

 

Any updates on the hotfix or patch? The suggested workaround above does not work for me since my servers are 2003. I am still unable to successfully get an SDR image of my servers.

 

Thanks,

 

Scott

Highlighted

Hi All,  An orphan\interim

Hi All,  An orphan\interim hot-fix has been packaged.  However, since this type of hot-fix is private and not fully qualified the distribution requires a transaction.  What this means is that customer support must be contacted and a case number generated.   When contacting customer support, be sure to mention Technote 184002 and Etrack 2932596.  Please note that a qualified public hot-fix is planned but is not currently available.  Thank you again everyone for your help and patience.

Highlighted

Hi,   We are having the

Hi,

 

We are having the common issue where we can't unselect anything on the D drive of a server with a standard raid5 container which has 1 logical drive divided into two partitions (C & D). The C drive is the system drive and the D drive is a standard data partition. The SDR light turns off if any file on D is unselected. I have run diskpart and the disk details are below. Can someone please tell me what I need to move off the D drive in order to be able to do selective backup of D drives data.

C Drive

 

DISKPART> detail disk

HP LOGICAL VOLUME SCSI Disk Device
Disk ID: 9C16D835
Type   : RAID
Bus    : 0
Target : 4
LUN ID : 0
Read-only  : No
Boot Disk  : Yes
Pagefile Disk  : Yes
Hibernation File Disk  : No
Crashdump Disk  : Yes

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 1     C   OS           NTFS   Partition    137 GB  Healthy    System

DISKPART> select disk 1

Disk 1 is now the selected disk.

 

 

D Drive

 

DISKPART> detail disk

HP LOGICAL VOLUME SCSI Disk Device
Disk ID: 41237368
Type   : RAID
Bus    : 0
Target : 5
LUN ID : 0
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 2     D   DATA         NTFS   Partition   1117 GB  Healthy

DISKPART>

Highlighted

Hi Keith Fountain,  A quick

Hi Keith Fountain,  A quick speculation is that the D: volume is being identified as a system critical volume.  To create backup sets that are capable of disaster recovery, all of the critical system components must be backed up in entirety.  Partial selections of critical system components will not result in a disaster recovery capable backup set.  When able, can you please describe your backup plan for this server and the need to unselect data on the D: volume.  I can subsequently investigate why the D: volume is being identified as a system critical volume.  Thank you.

Hi Marcus,   The server hosts

Hi Marcus,

 

The server hosts a number of data folders but we don't need to backup somewhere in the region of 60GB of the data stored on it and are running quite close to the limit of the LTO4 drive currently in use. The customer is not prepared to spen more money on an LTO5 drive and tapes as the previous BESR image of C with a selective file and folder backup of the D (then backed up to tape via BUE) worked perfectly well. We have four other server on the same installation that backup with SDR enabled without having to fully select additional drives and would like to know what is considered as system critical in order that I can move/change the setup to get to where we need to be. It does seem a little ludicrous that we can't unselect even a basic text file without losing the SDR capability as if the software is clever enough to work out what IS required it must also be capable of knowing what isn't!! Why can't it see that the component it has identified as a required part of the SDR is selected and therefore enable SDR. We have some 400 cients that we are slowly migrating over to 2012 but we are getting this issue at some 10-15% of those migrated so far. I have searched a number of forums and spoken to several Symantec employees but nobody seems able to tell me what constitutes a system critical volume. We have been doing BESR C drive and selective D drive backups for a number of years now and have never been unable to restore a sytem when required. Any information you can give us on this would be greatly appreciated.

I have attached a file showing the current selection list for the server with individual files for each drive shown in the additional dump on the right of its respective drive.

Highlighted

Hi Keith Fountain.  Thank you

Hi Keith Fountain.  Thank you for providing some of the backup plan details.  The Backup Exec Administrator’s Guide contains some information concerning critical system components in sections: “About backing up critical system components” and  “About selecting data to back up”.  To determine what data is specifically being considered critical on this specific system’s D: volume, a Remote Agent debug log from the system is needed.   Please let me know if you are unfamiliar with collecting a Remote Agent debug log.  If you are familiar, then when able, please begin collection of the debug log and then create the following registry key: “HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Simplified System Protection\Discover”.  This should cause additional details to be posted to the debug log.  When able, please post the debug log for review.  Thank you.

Highlighted

Many thanks for your response

Many thanks for your response Marcus, I'll obtain the relevant logs and post asap.

Highlighted

Hi Marcus,   Log file

Hi Marcus,

 

Log file attached, hopefully will have the correct info in it.

Highlighted

Hi Keith Fountain.  Thank you

Hi Keith Fountain.  Thank you for providing the debug log so quickly.  Unfortunately, the debug log does not contain the anticipated additional debug details.  Please ensure that the debug log capture and registry key are being performed on the specific system with the D: volume in question.  If this is the case, then as an alternate and if able, manually restarting the Remote Agent Service while capturing the debug log will ensure collection of the additional debug details.   This is a sample of the expected additional debug details:  “BEREMOTE: [11/07/12 15:21:16] [1580]  2012-11-07T15:21:16.472  - Identifying Critical System Services... in 'CCriticalResource:Smiley Very HappyetermineCriticalServices:2035'”.  When able, please post the new debug log for review.  Thank you.

Highlighted

Hi Marcus,   Sorry for the

Hi Marcus,

 

Sorry for the delay in response,we've been insanely busy over the last week. Anyhow, log obtained and attached.

Highlighted

Hi Keith Fountain,  No

Hi Keith Fountain,  No worries and thank you for the new debug log.  Based on the debug log, it appears that the MailMarshal Services that are installed on the D: volume are causing the D: volume to be considered a system critical device.  A workaround consideration would be to consolidate the system critical MailMarshal Services by reinstalling onto the existing system critical C: volume.  Another workaround consideration is to isolate the system critical MailMarshal Services by reinstalling onto a newly created small volume.  Please let me know if these are not viable workarounds.  Additional detailed information is below.  Hope this proves helpful.  Thank you for your help and patience. 

MMArrayManager - D:\Program Files (x86)\Marshal\MailMarshal\MMArrayManager.exe
MMController' - D:\Program Files (x86)\Marshal\MailMarshal\MMController.exe
MMEngine' - D:\Program Files (x86)\Marshal\MailMarshal\MMEngine.exe
MMPop3' - D:\Program Files (x86)\Marshal\MailMarshal\MMPop3.exe
MMReceiver' - D:\Program Files (x86)\Marshal\MailMarshal\MMReceiver.exe
MMSender' - D:\Program Files (x86)\Marshal\MailMarshal\MMSender.exe
MMUpdater' - D:\Program Files (x86)\Marshal\MailMarshal\MMUpdater.exe

Highlighted

Hi Marcus,   Many thanks for

Hi Marcus,

 

Many thanks for that, having looked through the log it's gonna be quite easy to determine for all of the other clients we have the problem at so many thanks for the registry key and debug info. Most helpful!

Highlighted

Hi Keith Fountain,  Good

Hi Keith Fountain,  Good news.  Glad that this was helpful.  Cheers!

Highlighted

We get this error on our

We get this error on our Exchange Server backups. We perform a full Exchange Backup every night. We checkmarked everything at the top level and left everything checked. 

I am not as concered with Simplified Disaster Recovery as much as I am just being able to restore the Exchange Database. 

We are running Exchange 2003 on Server 2003 (Standard). This is an HP server with SAS drives. I suspect after reading this thread that Server 2003 DISKPART is reporting the SAS drives as Fiber SANs drives. 

Anyway, if all I am concerned with is being able to restore the Exchange Database, does it matter if the job is 'Successful with Exceptions', and this being the only exception, since I don't care about SDR?