Video Screencast Help

SDR off

Created: 12 Sep 2012 | 59 comments

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?

Comments 59 CommentsJump to latest comment

pkh's picture

When SDR is off, you will not be able to restore the server with SDR.  However, you can still do a manual recovery of the server.  The success of this recovery will depend on what files/folders you have excluded from the backup.  For example, if you exclude the Windows directory, obviously the recovery will fail.  For this reason, SDR does not allow you to exclude anything.  Just in case, you exclude a critical component.

Gayatri_Kokje's picture

SDR icon will turn OFF if you de-select the root node checkbox next to your servername. Please make sure you select the server at this root node level so that the SDR icon is ON and you can recover your system in case of disaster.

The SDR icon will remain ON if you select this root node checkbox and then individually de-select the "non-critical" data volumes or the volumes hosting the disk storage devices.

 

Monster's picture

Most of us know what files are critical. For example, BE2012 cannot save certain temporary XML files that are created by antivirus software. Those files are not critical. Now I have to choose between.

  1. keeping explaining a customer, why backup jobs "fail", or
  2. excluding that file, denying me SDR, or
  3. uninstalling antivirus.

None of the above is truly a solution.

Dipesh's picture

Thanks all for replies to my query.  I am still not clear.  I am explaining what I have done again in little more clear detail:

I created a new backup job (full+incremental), deselected root node of server, and then selected all nodes under the root, i.e. all hard drives, system stat, and SQL Server instance, the SDR indicare turns to off. 

Now, my question is, in case of disaster, if I just boot the server with SDR Disk, and latest backup set created as above, will it recover everything as it was running before desaster?  As pkh's post, what is manual recovery?

Actually, I tested BackupExec 2012 with great success for individual file recovery to complete disaster recovery on the same hardware and OS platform.  After successful trials, I formated and re-installed server as final.  I couldn't understand, if it was working 100% ok in trial run, what kind of problem it experience after re-installation.

Thanks again for reading this much large post.

Dipesh

Gayatri_Kokje's picture

Hi Dipesh,

When you take backup of a system with the SDR icon ON, at the end of backup a .DR file is created for that system which is used in the disaster recovery process. After completion of the backup you will see a Full backup success alert and it will also advice you to copy that .Dr file to an alerate location as well.

When the system you are recovering has the backedup data locally attached, you can perform local recovery from the SDR wizard, during this process you need to provide the .dr file and the location of the backup sets.

When you are recovering a system which was backed up to a remote media server, during recovery you will perform Remote recovery and then point to the media server to perform the recovery.

For a sever recovery it would be necessary to have the .dr file.

This technote will provide you with the details:

http://www.symantec.com/business/support/index?page=content&id=TECH180099

Is there a particular reason why you are un-checking the checkbox at the root?

You can check the root and still manage to keep the SDR icon ON by un-checking non-critical volumes.

By doing the above, you can have the .dr file created for the server.

Hope this solves your issue.

Thanks,

Gayatri

Dipesh's picture

Hello Gayatri,

I have been backing up to NAS.  I checked, my backup sets do not have .dr file. 

Actually, I had been receiving error something like, 'failed load config xml file' related to p2v, however, I am not converting my backups to virtual.  I followed as commented here: https://www-secure.symantec.com/connect/forums/bac... to uncheck root node of the server.

Dipesh

 

Gayatri_Kokje's picture

Hi Dipesh,

The .dr file is not generated as the SDR icon was off in your case, which is the expected behaviour.

Is the server being backedup a physical server or a Virtual machine?

What kind of disks does the machine have? Does it have atleast one locally attached disk drive (SCSI, SATA, IDE etc)

 

Thanks,

Gayatri

Dipesh's picture

Hi Gayatri,

The server being backed up is physical server running Windows 2008 Enterprise 32 Bit. It has 2 x 450 GB SAS Drives (Hardware RAID1).

The .dr file has obviously not been generated when SDR was off (in last attempts), but was not generated even when SDR was on but backup ended up with error for p2v xml (mentionedin my earlier post).

Thanks for immediate replies from your side.

Dipesh

 

pkh's picture

When a job is not successful, the .dr file will not be created and this failed backup cannot be used for SDR recovery.  This is because if a critical file/folder cannot be backed up, then it is pointless to do any recovery.  Only upon successful completion and with SDR on, will the .dr file be created.  You would need to correct whatever is causing the job to fail.

As for manual recovery of a server, there is a chapter called Preparing for Disaster Recovery in the Admin Guide which tells you how to manually recover a server without using SDR.

marcusolini's picture

Hi.  We need to determine if your server is configured as described in article: http://www.symantec.com/business/support/index?page=content&id=TECH184002.  When able, please execute the following commands, capture the output, and post the output.  Ensure that the SELECT DISK and DETAIL DISK commands are done for all of the disk numbers output by the LIST DISK command.  Thank you.

(1) C:\>DISKPART

(2) DISKPART> LIST DISK

(3) SELECT DISK 0

(4) DETAIL DISK

(5) SELECT DISK 1

(6) DETAIL DISK

Dipesh's picture

Hello Marcusolini,

Please check following results off commands asked by you:

C:\Users\sysadmin>diskpart

Microsoft DiskPart version 6.0.6002
Copyright (C) 1999-2007 Microsoft Corporation.
On computer: PROSERVER

DISKPART> list disk

  Disk ###  Status      Size     Free     Dyn  Gpt
  --------  ----------  -------  -------  ---  ---
  Disk 0    Online       419 GB      0 B

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> detail disk

HP LOGICAL VOLUME SCSI Disk Device
Disk ID: C5E79E65
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 0     C   System       NTFS   Partition     98 GB  Healthy    System
  Volume 1     D   Vol1         NTFS   Partition     98 GB  Healthy
  Volume 2     E   Vol2         NTFS   Partition     98 GB  Healthy
  Volume 3     F   EDP          NTFS   Partition    126 GB  Healthy

DISKPART>

Hope this would help you understanding my setup.

Dipesh

 

marcusolini's picture

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.

Dipesh's picture

Hello,

Now, I selected root node for backup and ran full backup, it ended with error for p2v xml file:

Failed to load the configuration xml file.
C:\Program Files\Symantec\Backup Exec\Catalogs\PROSERVER\CatalogProcessTemporaryFolder\{5FE9B22B-D746-4D80-A7BA-E9F4CEB84C83}\p2v.xml

server.domain.com Backup-Full -- The job failed with the following error: Failed to load the configuration xml file.
 

but at the same time, .dr file has been generated and following message also has been logged:

You have successfully completed a backup job that includes all critical system components. The computer is now fully backed up.

I understand that now my server is fully backed up and I shall be able to recover it fully off disaster, but isn't there any way, I can get full success message?

Dipesh

pkh's picture

Excluding this file will make the error message go away.

Dipesh's picture

There is no such file there, the folder C:\Program Files\Symantec\Backup Exec\Catalogs\PROSERVER\CatalogProcessTemporaryFolder\{5FE9B22B-D746-4D80-A7BA-E9F4CEB84C83}\ is empty.

pkh's picture

It could be a hidden file.  Try excluding the folder instead.

rablack's picture

Hi,

I have the exact same problem - SDR fails with the p2v.xml error.

Excluding the folder automatically turns off SDR.

This is clearly no use.

I have tried creating a convert-to-virtual job along with the backup in an attempt to have the file created, but this does not work as there is no vmware or hyper-v environment for the server to connect to.

Please help,

Richard

saa515's picture

I am also having a similair problem.

 

When doing full backups of our servers (actually 3 servers are having this problem) the SDR light is on, the entire server is being backed up, but the jobs completes with an exception :

 

V-79-57344-42009 - Failed to load the configuration xml file.
 
D:\Backup Exec Catalogs\BACKUPSERVER\CatalogProcessTemporaryFolder\{C63B7D94-DF36-4CE4-B388-BC61E9CE7632}\p2v.xml
 
 
Because of this exception, I am not able to create a SDR disk. Above you mentioned to exclude this file from the backup selection. The path is the location of the backup exec catalogs, which are not available to uncheck in the backup selection menu (since they are not even on the same server)
 
Any ideas how to resolve this? Not being able to create SDR disks makes me extremely nervous, especially since one of the servers with this problem is our primary domain controller.
 
 
I've found these 2 articles related to the issue, but it looks as if there is no solution yet.
 
http://www.symantec.com/business/support/index?page=content&id=TECH189081&actp=search&viewlocale=en_US&searchid=1348173200181
 
http://www.symantec.com/business/support/index?page=content&id=TECH184002
 
Does anyone know of a work around? All 3 servers that have this issue are physical servers, with Windows Server 2003 Enterprise x32.
 
 
 
Thank you,
 
Scott
 
marcusolini's picture

Hi all,  Please review my previous post that requests DISKPART information.  Please also include the Backup Exec Job Log.  When able, collect this information and post it for review.  The most likely next steps will be to gather corresponding Backup Exec debug logs.  Thank you.

rablack's picture

My server is also physical Win 2003 R2 32-bit. It has a locally attached LTO-3 tape drive and a single RAID array, which seems to exclude the knowledge base article which talks about unsuported device types.

I really need an answer to this, as it is preventing me from deploying BE in our environment, without SDR capability.

Thanks,

Richard

saa515's picture

Marcusolini,

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.

 

Thank you,

Scott

 

 

 

 

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
 
C:\Documents and Settings\user>diskpart
 
Microsoft DiskPart version 5.2.3790.3959
Copyright (C) 1999-2001 Microsoft Corporation.
On computer: server
 
DISKPART> list disk
 
  Disk ###  Status      Size     Free     Dyn  Gpt
  --------  ----------  -------  -------  ---  ---
  Disk 0    Online       137 GB  4080 KB
 
DISKPART> select disk 0
 
Disk 0 is now the selected disk.
 
DISKPART> detail disk
 
HP LOGICAL VOLUME SCSI Disk Device
Disk ID: D99AD99A
Type   : FIBRE
Bus    : 0
Target : 4
LUN ID : 0
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 1     C                NTFS   Partition    137 GB  Healthy    System
 
DISKPART>
AttachmentSize
Job Log .docx 21.2 KB
marcusolini's picture

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.

rablack's picture

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.

Richard

saa515's picture

Marcusolini,

 

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.

 

 

Thanks,

Scott

rablack's picture

Marcusolini,

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.

Richard

saa515's picture

Some more information on the server - below is the RAID controller information and config.

 

 

Internal Controller 
Controller Status OK 
Controller Smart Array E200i 
Slot 0 
Controller Serial Number PR6CMU3149  
Bus Interface PCI 
RAID 6 (ADG) Status Disabled 
Firmware Version 1.84 
Rebuild Priority Low 
Transformation Priority Low 
Surface Scan Delay 15 sec 
Number of Ports 2 (Internal only) 
Number of Arrays 1 
Number of Logical Drives 1 
Number of Physical Drives 2 
 Array Accelerator 
Array Accelerator Present True 
Cache Status OK 
Array Accelerator (Cache) Ratio 100% Read / 0% Write 
Total Cache Size 64 MB 
Battery/Capacitor Pack Count  0 
 Arrays 
 SAS Array A - 1 Logical Drive(s) 
 Logical Drive(s) / Local OS Access Name 
 Logical Drive 1 (136.7 GB, RAID 1) \\.\PhysicalDrive0 
 Assigned Drives 
 146 GB 1-Port SAS Drive at Port 1I : Box 1 : Bay 1 
 146 GB 1-Port SAS Drive at Port 1I : Box 1 : Bay 2 
 Unassigned Drives 
 None 
 Spare Drives 
 None 
 Tape Devices 
 None 
 
Logical Drive
Status OK
Drive Number 1
Drive Unique ID 600508B1001031343920202020200000
Size 139979 MB
Fault Tolerance RAID 1
Heads 255
Sectors 32
Cylinders 35132
Stripe Size 128 KB
Array Accelerator Enabled
Disk Name \\.\PhysicalDrive0
Disk Partition Information Partition Number: 1, Size: 136.7 GB, Mount Point: C:\

 

Mirror Groups
Drive(s) Assigned to Mirror Group 1 146 GB 1-Port SAS Drive at Port 1I : Box 1 : Bay 1
Drive(s) Assigned to Mirror Group 2 146 GB 1-Port SAS Drive at Port 1I : Box 1 : Bay 2

 

Array
Status OK
Array A
Drive Type SAS

 

Physical Drives
 146 GB 1-Port SAS Drive at Port 1I : Box 1 : Bay 1
 146 GB 1-Port SAS Drive at Port 1I : Box 1 : Bay 2

 

Spare Drives
 None

 

Failed Drives
 None

  

Device Path
 Smart Array E200i in Embedded Slot
 SAS Array A - 1 Logical Drive(s)

 

 

Scott
marcusolini's picture

Hi Scott,  Thank you for the addition information.  When able, please also collect the ENUMDISK information mentioned in my recent post for review as well.  Thank you, Mark.

marcusolini's picture

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.

saa515's picture

 

I'm not sure if you were wanting more information that what is below, if so - please include what commands need to be ran inside of the enumdisk utility.
 
 
Properties for Device 1
 
Device ID: SCSI\DiskHP______LOGICAL_VOLUME__1.84
 
Adapter Properties
------------------
Bus Type       : FIBRE
Max. Tr. Length: 0x40000
Max. Phy. Pages: 0x3f
Alignment Mask : 0x3
 
Device Properties
-----------------
Device Type     : Direct Access Device (0x0)
Removable Media : No
Vendor ID       : HP
Product ID      : LOGICAL VOLUME
Product Revision: 1.84
Serial Number   : PR6CMU3149
 
Inquiry Data from Pass Through
------------------------------
Device Type: Direct Access Device (0x0)
Vendor ID  : HP
Product ID : LOGICAL VOLUME
Product Rev: 1.84
Vendor Str :
 
 
 
 ***  End of Device List  ***
 
Scott
marcusolini's picture

Hi Scott.  This is exactly what we need.  Thank you!

dbrownny's picture

 

I've been reading this thread with interest since I have two Dell servers exhibiting same issue. I'll watch for updates to the thread. If it helps, I have also attached the DISKPART and Enumdisk reports below. These two servers are just about identical and are the only two that give the error:
Failed to load the configuration xml file. C:\Program Files\Symantec\Backup Exec\Catalogs\servername\CatalogProcessTemporaryFolder\{030672F4-89D4-4994-8867-80168FC5CDC0}\p2v.xml  
 
SERVER #1: Dell PowerEdge 2950
Controller: PERC 5/i Integrated 
Firmware Version 5.0.2-0003 
Driver Version 1.21.00.64 
Number of Connectors 2 
Virtual Disks 
Status  Name  State  Layout  Size  Device Name  Type  Read Policy  Write Policy  Stripe Element Size 
Virtual Disk 0  Ready  RAID-5  203.25GB  Windows Disk 0  SAS  No Read Ahead  Write Through  64KB 
Connectors   
Status  Name  State  Connector Type 
Connector 0  Ready  SAS Port RAID Mode 
Connector 1  Ready  SAS Port RAID Mode 
 
C:\>DISKPART
 
DISKPART> LIST DISK
 
  Disk ###  Status      Size     Free     Dyn  Gpt
  --------  ----------  -------  -------  ---  ---
  Disk 0    Online       203 GB      0 B
 
DISKPART> SELECT DISK 0
 
Disk 0 is now the selected disk.
 
DISKPART> DETAIL DISK
 
DELL PERC 5/i SCSI Disk Device
Disk ID: BB180359
Type   : FIBRE
Bus    : 1
Target : 0
LUN ID : 0
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C                NTFS   Partition    183 GB  Healthy    System
  Volume 1     D                NTFS   Partition     20 GB  Healthy
 
C:\enum>enumdisk
Properties for Device 1
 
Device ID: SCSI\DiskDELL____PERC_5/i________1.00
 
Adapter Properties
------------------
Bus Type       : FIBRE
Max. Tr. Length: 0x80000
Max. Phy. Pages: 0x50
Alignment Mask : 0x0
 
Device Properties
-----------------
Device Type     : Direct Access Device (0x0)
Removable Media : No
Vendor ID       : DELL
Product ID      : PERC 5/i
Product Revision: 1.00
 
Inquiry Data from Pass Through
------------------------------
Device Type: Direct Access Device (0x0)
Vendor ID  : DELL
Product ID : PERC 5/i
Product Rev: 1.00
Vendor Str :
 ***  End of Device List  ***
 
SERVER #2: Dell PowerEdge 2950
Controller: PERC 5/i Integrated 
Firmware Version 5.0.2-0003 
Driver Version 1.21.00.32 
Number of Connectors 2 
Virtual Disks 
Status  Name  State  Layout  Size  Device Name  Type  Read Policy  Write Policy  Stripe Element Size 
Virtual Disk 0  Ready  RAID-5  203.25GB  Windows Disk 0  SAS  No Read Ahead  Write Through  64 KB 
 
 
C:\>DISKPART
 
DISKPART> LIST DISK
 
  Disk ###  Status      Size     Free     Dyn  Gpt
  --------  ----------  -------  -------  ---  ---
  Disk 0    Online       203 GB      0 B
 
DISKPART> SELECT DISK 0
 
Disk 0 is now the selected disk.
 
DISKPART> DETAIL DISK
 
DELL PERC 5/i SCSI Disk Device
Disk ID: 8769DDD5
Type   : FIBRE
Bus    : 1
Target : 0
LUN ID : 0
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 1     C                NTFS   Partition    183 GB  Healthy    System
  Volume 2     D                NTFS   Partition     20 GB  Healthy
 
C:\ENUM>enumdisk
Properties for Device 1
 
Device ID: SCSI\DiskDELL____PERC_5/i________1.00
 
Adapter Properties
------------------
Bus Type       : FIBRE
Max. Tr. Length: 0x80000
Max. Phy. Pages: 0x50
Alignment Mask : 0x0
 
Device Properties
-----------------
Device Type     : Direct Access Device (0x0)
Removable Media : No
Vendor ID       : DELL
Product ID      : PERC 5/i
Product Revision: 1.00
 
Inquiry Data from Pass Through
------------------------------
Device Type: Direct Access Device (0x0)
Vendor ID  : DELL
Product ID : PERC 5/i
Product Rev: 1.00
Vendor Str :
 ***  End of Device List  ***

 

marcusolini's picture

Hi dbrownny,  Thank you for letting us know and for the helpful information.

saa515's picture

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.

 

Marcusolini,

 

Any update or any additional information needed to help resolve this?

 

Scott

 

 

marcusolini's picture

Hi Scott,   At the moment we seem to have enough information.  Thank you for your help and patience, Mark.

rablack's picture

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.

Thanks,

Richard

saa515's picture

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.

 

Scott

Larry Fine's picture

I fixed my problem server by updating the LSI SCSI driver.  The new version apparently now reports the correct "type" so the full backup job is now successful.

If you find this is a solution for the thread, please mark it as such.

saa515's picture

Larry,

 

Could you be more specific? What specific hardware do you have? Make/Part number of your scsi card? Any downtime associated with the updated driver?

 

Thanks,

 

Scott

Larry Fine's picture

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

DISKPART>

If you find this is a solution for the thread, please mark it as such.

rablack's picture

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

saa515's picture

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

marcusolini's picture

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.

Dr Hu's picture

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

 

 

marcusolini's picture

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

Dr Hu's picture

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>
saa515's picture

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

marcusolini's picture

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.

Keith Fountain's picture

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>

marcusolini's picture

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.

Keith Fountain's picture

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.

drive_selections.jpg
marcusolini's picture

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.

Keith Fountain's picture

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

Keith Fountain's picture

Hi Marcus,

 

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

AttachmentSize
text.txt 236.65 KB
marcusolini's picture

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.

keithfount's picture

Hi Marcus,

 

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

AttachmentSize
dataserver log.txt 284.29 KB
marcusolini's picture

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

keithfount's picture

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!

marcusolini's picture

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

kiwifruit's picture

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?