09-12-2012 06:48 PM
If I de-select and then select individual but all components, the 'Simplified Disaster Recovery' indicator turns to 'OFF'. Shall I be able to recover my server in case of disaster?
10-04-2012 12:06 AM
10-04-2012 06:16 AM
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
10-04-2012 12:24 PM
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.
10-10-2012 03:30 AM
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.
10-12-2012 01:57 PM
Hi Dr Hu, When able, can you please provide the DISKPART and ENUMDISK output from these servers for review? Thank you.
10-15-2012 11:56 PM
Hi Marcusolini,
Thankyou for your response, info requested is below.
10-22-2012 05:15 AM
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
10-25-2012 01:41 PM
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.
10-26-2012 06:52 AM
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>
10-26-2012 02:32 PM
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.
11-05-2012 02:49 AM
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.
11-07-2012 12:34 PM
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.
11-08-2012 01:03 AM
Many thanks for your response Marcus, I'll obtain the relevant logs and post asap.
11-08-2012 09:36 AM
Hi Marcus,
Log file attached, hopefully will have the correct info in it.
11-09-2012 11:46 AM
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::DetermineCriticalServices:2035'”. When able, please post the new debug log for review. Thank you.
11-15-2012 04:02 AM
Hi Marcus,
Sorry for the delay in response,we've been insanely busy over the last week. Anyhow, log obtained and attached.
11-15-2012 08:04 AM
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
11-16-2012 01:14 AM
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!
11-16-2012 07:22 AM
Hi Keith Fountain, Good news. Glad that this was helpful. Cheers!
05-11-2013 08:38 AM
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?