cancel
Showing results for 
Search instead for 
Did you mean: 

Exchange store backup to USB hard drive fails, but tape works ok

Chris_Craig
Level 3

I have a bizarre issue with 12.5 (although this started with 12, but has followed my recent upgrade). If I run a backup of the Exchange 2007 store directly to tape, it works fine, no errors. I can view and restore the store without any issues. If I run the same job, it fails with this error:

Backup- \\server.name\Microsoft Information Store\First Storage Group The version of Microsoft Exchange Server 2007 Management Tools on the Backup Exec media server must be the same version or later as the management tools that are on the Exchange Server 2007 that you want to back up.

Doesn't seem to make any sense - the version of management tools is the latest on both the media server and the exchange server, however I would expect if this wasn't a misleading error message the job to tape would fail as well, but in fact it runs fine, it's only the job to the USB hard hard that fails. On top of this, any other job I run that uses the USB drive or Tape as media works fine.

Any help would be appreciated.

Thanks.

9 REPLIES 9

DominikG
Level 6
Partner Accredited
First of all, there are many problems regarding BE 12.5 and Exchange 2007.
I recommend to update the exchange as well as the BE Server to the latest state. (alle hotfixes)
There have been many issues with Exchange 2007 been solved in some hotfixes.

best regards

Dominik

Ben_L_
Level 6
Employee
Can you use our b2d test tool against that USB drive to see how well it will work as a b2d device?

http://seer.entsupport.symantec.com/docs/321584.htm

Chris_Craig
Level 3
Ran a comparison test with another site - worked fine. Test site was:
Exchange Server OS = Windows 2003 Server x64, Exchange version 8.1 (240.6)
Backup Exec Server OS = Windows 2003 Server x86, Backup Exec version 12.5

Problem site is:
Exchange Server OS = Windows 2008 Server x64, Exchange version 8.1 (240.6)
Backup Exec Server OS = Windows 2003 Server x86, Backup Exec version 12.5

So the only difference, at least at a top level, is the OS of the Exchange server in each case. I have run the B2Dtest and pasted the results below, as expected as any flat file backup to USB works fine, it's only Exchange 2 USB that bombs:

08/06/09 10:51:45 -------------------------------------------------------------
08/06/09 10:51:45 Symantec Backup Exec B2D Compatibility Test
08/06/09 10:51:45 Build 12.6.2729
08/06/09 10:51:45 Copyright (C) 2008 Symantec Corporation. All rights reserved.
08/06/09 10:51:45
08/06/09 10:51:45 This tool can take up to several hours to complete.  The
08/06/09 10:51:45 amount of time it takes is dependent on the host computer as
08/06/09 10:51:45 well as the underlying appliance technology.  It is
08/06/09 10:51:45 recommend that this tool be run at a time when there will be
08/06/09 10:51:45 minimal impact on business operations.
08/06/09 10:51:45
08/06/09 10:51:45 For the tool to run successfully, the target location of the
08/06/09 10:51:45 test must contain at least 4,339,073,024 bytes of available
08/06/09 10:51:45 space.  Furthermore, any credentials supplied must have
08/06/09 10:51:45 sufficient privileges to create, read, write, and delete
08/06/09 10:51:45 directories and files on the appliance.
08/06/09 10:51:45
08/06/09 10:51:45 Further information about this tool can be found online at
08/06/09 10:51:45 the Symantec product support site:
08/06/09 10:51:45   http://entsupport.symantec.com/umi/v-275-10000
08/06/09 10:52:14 Test Parameters:
08/06/09 10:52:14  Make    : UNKNOWN
08/06/09 10:52:14  Model   : UNKNOWN
08/06/09 10:52:14  Firmware: UNKNOWN
08/06/09 10:52:14  Location: g:\B2DTestDir
08/06/09 10:52:14  Username: Current User (CRUISE\acronym)
08/06/09 10:52:14
08/06/09 10:52:14  File Count      : 10,000 files
08/06/09 10:52:14  Buffer size     : 65,536 bytes
08/06/09 10:52:14  Mapped file size: 1,048,576 bytes
08/06/09 10:52:14  IO File Size    : 4,296,015,872 bytes
08/06/09 10:52:14  Required Space  : 4,339,073,024 bytes
08/06/09 10:52:14
08/06/09 10:52:14 Create Directory
08/06/09 10:52:14  ===> PASSED
08/06/09 10:52:14 Disk Space
08/06/09 10:52:14  ===> PASSED
08/06/09 10:52:14 Volume Information
08/06/09 10:52:14  ===> PASSED
08/06/09 10:52:14 Query DOS Devices
08/06/09 10:52:14 TRACE: DOSDEVICE: Z:
08/06/09 10:52:14 TRACE: DOSDEVICE: (null)
08/06/09 10:52:14 TRACE: DOSDEVICE: S:
08/06/09 10:52:14 TRACE: DOSDEVICE: Global
08/06/09 10:52:14 TRACE: DOSDEVICE: V:
08/06/09 10:52:14 TRACE: DOSDEVICE: D:
08/06/09 10:52:14 TRACE: DOSDEVICE: Scsi3:
08/06/09 10:52:14 TRACE: DOSDEVICE: NDIS
08/06/09 10:52:14 TRACE: DOSDEVICE: DISPLAY1
08/06/09 10:52:14 TRACE: DOSDEVICE: ACPI#GenuineIntel_-_x86_Family_15_Model_4#_2#{97fadb10-4e33-40ae-359c-8bef029dbdd0}
08/06/09 10:52:14 TRACE: DOSDEVICE: DISPLAY2
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#MS_PPPOEMINIPORT#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
08/06/09 10:52:14 TRACE: DOSDEVICE: DmIoDaemon
08/06/09 10:52:14 TRACE: DOSDEVICE: STORAGE#Volume#1&30a96598&0&SignatureA4B57300Offset7E00Length7470980400#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: Ip
08/06/09 10:52:14 TRACE: DOSDEVICE: SymEvent
08/06/09 10:52:14 TRACE: DOSDEVICE: DISPLAY3
08/06/09 10:52:14 TRACE: DOSDEVICE: {9A7F7772-3B35-4954-816A-63560A3BBF5F}
08/06/09 10:52:14 TRACE: DOSDEVICE: E:
08/06/09 10:52:14 TRACE: DOSDEVICE: WMIAdminDevice
08/06/09 10:52:14 TRACE: DOSDEVICE: IDE#CdRomHL-DT-ST_RW#DVD_GCC-4244N_______________1.02____#5&150c8bda&0&0.0.0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: FDC#GENERIC_FLOPPY_DRIVE#5&d23011c&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: IPSECDev
08/06/09 10:52:14 TRACE: DOSDEVICE: EraserUtilDrvI8
08/06/09 10:52:14 TRACE: DOSDEVICE: DISPLAY4
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#MS_NDISWANIP#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
08/06/09 10:52:14 TRACE: DOSDEVICE: TpFilter
08/06/09 10:52:14 TRACE: DOSDEVICE: PCI#VEN_9005&DEV_0250&SUBSYS_028E1014&REV_07#5&32639624&0&700030#{2accfe60-c130-11d2-b082-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: USBSTOR#Disk&Ven_Seagate&Prod_FreeAgent_Pro&Rev_4109#____________6QG2D9F5&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: USB#ROOT_HUB#4&2b3a0619&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
08/06/09 10:52:14 TRACE: DOSDEVICE: RdpDrDvMgr
08/06/09 10:52:14 TRACE: DOSDEVICE: TAPE0
08/06/09 10:52:14 TRACE: DOSDEVICE: SCSI#Disk&Ven_IBM&Prod_ServeRAID&Rev_6.10#6&1ee72d03&0&000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: TAPE1
08/06/09 10:52:14 TRACE: DOSDEVICE: Volume{dd8a92b0-9a1a-11dd-bbdd-00145e688d81}
08/06/09 10:52:14 TRACE: DOSDEVICE: F:
08/06/09 10:52:14 TRACE: DOSDEVICE: WMIDataDevice
08/06/09 10:52:14 TRACE: DOSDEVICE: STORAGE#Volume#1&30a96598&0&SignatureE8900690Offset7E00LengthE8E0B30400#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: SCSI#Sequential&Ven_IBM&Prod_ULTRIUM-TD2&Rev_4770#6&2ce25659&0&000#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: ACPI#PNP0303#4&25ab6e80&0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
08/06/09 10:52:14 TRACE: DOSDEVICE: COM1
08/06/09 10:52:14 TRACE: DOSDEVICE: USB#Vid_0bc2&Pid_3110#____________6QG2D9F5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
08/06/09 10:52:14 TRACE: DOSDEVICE: PIPE
08/06/09 10:52:14 TRACE: DOSDEVICE: STORAGE#Volume#1&30a96598&0&Signature21Offset500200000Length1D2E800000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: G:
08/06/09 10:52:14 TRACE: DOSDEVICE: UNC
08/06/09 10:52:14 TRACE: DOSDEVICE: NAVEX15
08/06/09 10:52:14 TRACE: DOSDEVICE: BBDRVCHANNEL
08/06/09 10:52:14 TRACE: DOSDEVICE: TCP
08/06/09 10:52:14 TRACE: DOSDEVICE: HCD0
08/06/09 10:52:14 TRACE: DOSDEVICE: FltMgrMsg
08/06/09 10:52:14 TRACE: DOSDEVICE: ACPI#GenuineIntel_-_x86_Family_15_Model_4#_3#{97fadb10-4e33-40ae-359c-8bef029dbdd0}
08/06/09 10:52:14 TRACE: DOSDEVICE: {C92E0ED4-3E48-483D-B2A5-D66F84AEB269}
08/06/09 10:52:14 TRACE: DOSDEVICE: {CDFC7998-5E42-4B4B-AC3C-E158B87D9B82}
08/06/09 10:52:14 TRACE: DOSDEVICE: LCD
08/06/09 10:52:14 TRACE: DOSDEVICE: ACPI#PNP0303#4&25ab6e80&0#{4afa3d53-74a7-11d0-be5e-00a0c9062857}
08/06/09 10:52:14 TRACE: DOSDEVICE: HCD1
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#MS_PTIMINIPORT#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
08/06/09 10:52:14 TRACE: DOSDEVICE: PhysicalDrive0
08/06/09 10:52:14 TRACE: DOSDEVICE: EraserCtrlDrv
08/06/09 10:52:14 TRACE: DOSDEVICE: USBSTOR#Disk&Ven_WD&Prod_10EAVS_External&Rev_1.75#57442D574341553435333533343135&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: PRN
08/06/09 10:52:14 TRACE: DOSDEVICE: HCD2
08/06/09 10:52:14 TRACE: DOSDEVICE: PhysicalDrive1
08/06/09 10:52:14 TRACE: DOSDEVICE: fsWrap
08/06/09 10:52:14 TRACE: DOSDEVICE: CdRom0
08/06/09 10:52:14 TRACE: DOSDEVICE: TpFilterAppQueue
08/06/09 10:52:14 TRACE: DOSDEVICE: IDE#CdRomHL-DT-ST_RW#DVD_GCC-4244N_______________1.02____#5&150c8bda&0&0.0.0#{1186654d-47b8-48b9-beb9-7df113ae3c67}
08/06/09 10:52:14 TRACE: DOSDEVICE: PhysicalDrive2
08/06/09 10:52:14 TRACE: DOSDEVICE: EraserUtilDrv10910
08/06/09 10:52:14 TRACE: DOSDEVICE: ACPI#FixedButton#2&daba3ff&0#{4afa3d53-74a7-11d0-be5e-00a0c9062857}
08/06/09 10:52:14 TRACE: DOSDEVICE: NAVENG
08/06/09 10:52:14 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_24DD&SUBSYS_02DD1014&REV_02#3&11583659&0&EF#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
08/06/09 10:52:14 TRACE: DOSDEVICE: SRTSPX
08/06/09 10:52:14 TRACE: DOSDEVICE: ACPI#PNP0501#2#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
08/06/09 10:52:14 TRACE: DOSDEVICE: ACPI#PNP0F13#4&25ab6e80&0#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
08/06/09 10:52:14 TRACE: DOSDEVICE: ACPI#GenuineIntel_-_x86_Family_15_Model_4#_0#{97fadb10-4e33-40ae-359c-8bef029dbdd0}
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#RDPDR#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}
08/06/09 10:52:14 TRACE: DOSDEVICE: USB#Vid_1058&Pid_1003#57442D574341553435333533343135#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
08/06/09 10:52:14 TRACE: DOSDEVICE: IDE#CdRomHL-DT-ST_RW#DVD_GCC-4244N_______________1.02____#5&150c8bda&0&0.0.0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: FDC#GENERIC_FLOPPY_DRIVE#5&d23011c&0&0#{53f56311-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: MountPointManager
08/06/09 10:52:14 TRACE: DOSDEVICE: Volume{49a054bb-e8ba-11da-a67f-806e6f6e6963}
08/06/09 10:52:14 TRACE: DOSDEVICE: {CED907FE-6D0A-45E4-BA55-B5940B989638}
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#MS_L2TPMINIPORT#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
08/06/09 10:52:14 TRACE: DOSDEVICE: DmConfig
08/06/09 10:52:14 TRACE: DOSDEVICE: STORAGE#Volume#1&30a96598&0&Signature21Offset4000Length5001FC000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: WanArp
08/06/09 10:52:14 TRACE: DOSDEVICE: PCI#VEN_1002&DEV_5159&SUBSYS_02C81014&REV_00#4&1e4c1bd8&0&30F0#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}
08/06/09 10:52:14 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_24D4&SUBSYS_02DD1014&REV_02#3&11583659&0&E9#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#ftdisk#0000#{53f5630e-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: DmTrace
08/06/09 10:52:14 TRACE: DOSDEVICE: Volume{348abf7e-749b-11dc-aa85-00145e688d81}
08/06/09 10:52:14 TRACE: DOSDEVICE: A:
08/06/09 10:52:14 TRACE: DOSDEVICE: {B6CB78C7-3119-4DFD-9979-204B354C53D9}
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#dmio#0000#{53f5630e-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#SYSTEM#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
08/06/09 10:52:14 TRACE: DOSDEVICE: NDISWANIP
08/06/09 10:52:14 TRACE: DOSDEVICE: Scsi0:
08/06/09 10:52:14 TRACE: DOSDEVICE: PCI#VEN_14E4&DEV_1659&SUBSYS_02C61014&REV_11#4&208aa108&0&0028#{ad498944-762f-11d0-8dcb-00c04fc3358c}
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#SYSTEM#0000#{4747b320-62ce-11cf-a5d6-28db04c10000}
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#MS_PPTPMINIPORT#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
08/06/09 10:52:14 TRACE: DOSDEVICE: PTILINK1
08/06/09 10:52:14 TRACE: DOSDEVICE: SCSI#Sequential&Ven_EXABYTE&Prod_VXA-2&Rev_210D#6&106f1ece&0&0b0#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: Scsi1:
08/06/09 10:52:14 TRACE: DOSDEVICE: SCSI2MediumChanger
08/06/09 10:52:14 TRACE: DOSDEVICE: IPMULTICAST
08/06/09 10:52:14 TRACE: DOSDEVICE: NdisWan
08/06/09 10:52:14 TRACE: DOSDEVICE: PTILINK2
08/06/09 10:52:14 TRACE: DOSDEVICE: DmLoader
08/06/09 10:52:14 TRACE: DOSDEVICE: Shadow
08/06/09 10:52:14 TRACE: DOSDEVICE: WGX
08/06/09 10:52:14 TRACE: DOSDEVICE: ACPI#PNP0501#2#{4d36e978-e325-11ce-bfc1-08002be10318}
08/06/09 10:52:14 TRACE: DOSDEVICE: PTILINK3
08/06/09 10:52:14 TRACE: DOSDEVICE: Volume{49a054ba-e8ba-11da-a67f-806e6f6e6963}
08/06/09 10:52:14 TRACE: DOSDEVICE: FltMgr
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#SYSTEM#0003#{4d36e97d-e325-11ce-bfc1-08002be10318}
08/06/09 10:52:14 TRACE: DOSDEVICE: USB#ROOT_HUB20#4&386d75a1&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
08/06/09 10:52:14 TRACE: DOSDEVICE: USB#ROOT_HUB#4&3ad16679&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
08/06/09 10:52:14 TRACE: DOSDEVICE: FtControl
08/06/09 10:52:14 TRACE: DOSDEVICE: C:
08/06/09 10:52:14 TRACE: DOSDEVICE: MAILSLOT
08/06/09 10:52:14 TRACE: DOSDEVICE: SRTSP
08/06/09 10:52:14 TRACE: DOSDEVICE: AUX
08/06/09 10:52:14 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_24D2&SUBSYS_02DD1014&REV_02#3&11583659&0&E8#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
08/06/09 10:52:14 TRACE: DOSDEVICE: PCI#VEN_1000&DEV_0030&SUBSYS_3108103C&REV_07#5&2f6919d9&0&180010#{2accfe60-c130-11d2-b082-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: Volume{7bac805b-e87b-11da-bfd7-00145e688d81}
08/06/09 10:52:14 TRACE: DOSDEVICE: GLOBALROOT
08/06/09 10:52:14 TRACE: DOSDEVICE: Scsi2:
08/06/09 10:52:14 TRACE: DOSDEVICE: Ndisuio
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#RDP_MOU#0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
08/06/09 10:52:14 TRACE: DOSDEVICE: NUL
08/06/09 10:52:14 TRACE: DOSDEVICE: ACPI#GenuineIntel_-_x86_Family_15_Model_4#_1#{97fadb10-4e33-40ae-359c-8bef029dbdd0}
08/06/09 10:52:14 TRACE: DOSDEVICE: Root#RDP_KBD#0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
08/06/09 10:52:14 TRACE: DOSDEVICE: PCI#VEN_1000&DEV_000C&SUBSYS_10201000&REV_02#5&824a6f0&0&200210#{2accfe60-c130-11d2-b082-00a0c91efb8b}
08/06/09 10:52:14 TRACE: DOSDEVICE: Volume{49a054bc-e8ba-11da-a67f-806e6f6e6963}
08/06/09 10:52:14 TRACE: DOSDEVICE: EraserUtilRebootDrv
08/06/09 10:52:14 TRACE: DOSDEVICE: DmInfo
08/06/09 10:52:14  ===> PASSED
08/06/09 10:52:14 Traverse Volume Info
08/06/09 10:52:14 TRACE: Volume: \\?\Volume{49a054bc-e8ba-11da-a67f-806e6f6e6963}\
08/06/09 10:52:14 TRACE: Device: \Device\HarddiskVolume1
08/06/09 10:52:14 TRACE: No mount points detected
08/06/09 10:52:14 TRACE: Volume: \\?\Volume{7bac805b-e87b-11da-bfd7-00145e688d81}\
08/06/09 10:52:14 TRACE: Device: \Device\HarddiskVolume2
08/06/09 10:52:14 TRACE: No mount points detected
08/06/09 10:52:14 TRACE: Volume: \\?\Volume{49a054bb-e8ba-11da-a67f-806e6f6e6963}\
08/06/09 10:52:14 TRACE: Device: \Device\CdRom0
08/06/09 10:52:14 TRACE: Device is a CD ROM device - skipping mount point enumeration
08/06/09 10:52:14 TRACE: Volume: \\?\Volume{49a054ba-e8ba-11da-a67f-806e6f6e6963}\
08/06/09 10:52:14 TRACE: Device: \Device\Floppy0
08/06/09 10:52:14 TRACE: Device is a floppy device - skipping mount point enumeration
08/06/09 10:52:14 TRACE: Volume: \\?\Volume{dd8a92b0-9a1a-11dd-bbdd-00145e688d81}\
08/06/09 10:52:14 TRACE: Device: \Device\HarddiskVolume3
08/06/09 10:52:14 TRACE: No mount points detected
08/06/09 10:52:14 TRACE: Volume: \\?\Volume{348abf7e-749b-11dc-aa85-00145e688d81}\
08/06/09 10:52:14 TRACE: Device: \Device\HarddiskVolume4
08/06/09 10:52:14 TRACE: No mount points detected
08/06/09 10:52:14  ===> PASSED
08/06/09 10:52:14 Memory Mapped Files
08/06/09 10:52:14 TRACE: Initialize memory map
08/06/09 10:52:14 TRACE: Verify memory map
08/06/09 10:52:14  ===> PASSED
08/06/09 10:52:14 Reparse Points
08/06/09 10:52:14 TRACE: Volume supports reparse points
08/06/09 10:52:14  ===> PASSED
08/06/09 10:52:14 Sparse Files
08/06/09 10:52:14 TRACE: Volume supports sparse files
08/06/09 10:52:14  ===> PASSED
08/06/09 10:52:14 B2D Pre-allocation
08/06/09 10:52:14 TRACE: Positioning file pointer
08/06/09 10:52:14 TRACE: Writing a single buffer to extend file
08/06/09 10:55:25 TRACE: Setting end of file
08/06/09 10:55:25  ===> PASSED
08/06/09 10:55:25 Random IO
08/06/09 10:55:25 TRACE: Seeking to offset 0
08/06/09 10:55:25 TRACE: Writing 67108864 bytes to file
08/06/09 10:55:25 TRACE: Seeking to offset 0
08/06/09 10:55:25 TRACE: Reading 67108864 bytes from file
08/06/09 10:55:25 TRACE: Testing end of file
08/06/09 10:55:25 TRACE: Seeking to offset 1048576
08/06/09 10:55:25 TRACE: Reading 1048576 bytes from file
08/06/09 10:55:25 TRACE: Writing 1048576 bytes to file
08/06/09 10:55:25 TRACE: Seeking to offset 67108864
08/06/09 10:55:25 TRACE: Writing 655360 bytes to file
08/06/09 10:55:25 TRACE: Seeking to offset 67108864
08/06/09 10:55:25 TRACE: Reading 655360 bytes from file
08/06/09 10:55:25 TRACE: Testing end of file
08/06/09 10:55:25 TRACE: Seeking to offset 1048576
08/06/09 10:55:25 TRACE: Setting end of file
08/06/09 10:55:25 TRACE: Testing end of file
08/06/09 10:55:25 TRACE: Seeking to offset 0
08/06/09 10:55:25 TRACE: Reading 1048576 bytes from file
08/06/09 10:55:25 TRACE: Writing 1048576 bytes to file
08/06/09 10:55:25 TRACE: Testing end of file
08/06/09 10:55:25 TRACE: Seeking to offset 0
08/06/09 10:55:25 TRACE: Reading 2097152 bytes from file
08/06/09 10:55:25 TRACE: Testing end of file
08/06/09 10:55:25 TRACE: Seeking to offset 0
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping 131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping 131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping 131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping 131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping 131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping 131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping 131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping 131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping 131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping 131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping 131072 bytes
08/06/09 10:55:25 TRACE: Seeking to offset 2031616
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping -131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping -131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping -131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping -131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping -131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping -131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping -131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping -131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping -131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping -131072 bytes
08/06/09 10:55:25 TRACE: Reading 65536 bytes from file
08/06/09 10:55:25 TRACE: Skipping -131072 bytes
08/06/09 10:55:25  ===> PASSED
08/06/09 10:55:25 Default B2D Configuration
08/06/09 10:55:25 TRACE: Writing to file
08/06/09 10:58:20 TRACE: Reading from file
08/06/09 11:00:48  ===> PASSED
08/06/09 11:00:48 Read buffer B2D Configuration
08/06/09 11:00:48 TRACE: Writing to file
08/06/09 11:03:43 TRACE: Reading from file
08/06/09 11:06:13  ===> PASSED
08/06/09 11:06:13 No write buffering B2D Configuration
08/06/09 11:06:13 TRACE: Writing to file
08/06/09 11:09:15 TRACE: Reading from file
08/06/09 11:11:41  ===> PASSED
08/06/09 11:11:41 File Handles
08/06/09 11:11:48  ===> PASSED
08/06/09 11:11:48 Cleanup Directory
08/06/09 11:11:48 TRACE: Skipping entry .
08/06/09 11:11:48 TRACE: Skipping entry ..
08/06/09 11:11:51  ===> PASSED
08/06/09 11:11:51
08/06/09 11:11:51 Total Tests Run: 15
08/06/09 11:11:51 Passed: 15
08/06/09 11:11:51 Failed: 0
08/06/09 11:11:51 Warned: 0
08/06/09 11:11:51
08/06/09 11:11:51 TRACE:
08/06/09 11:11:51 TRACE: Functions called:
08/06/09 11:11:51 TRACE: -----------------
08/06/09 11:11:51 TRACE: CloseHandle                      10010
08/06/09 11:11:51 TRACE: CreateDirectory                  1
08/06/09 11:11:51 TRACE: CreateFile                       10010
08/06/09 11:11:51 TRACE: CreateFileMapping                1
08/06/09 11:11:51 TRACE: DeleteFile                       10002
08/06/09 11:11:51 TRACE: DeviceIoControl                  2
08/06/09 11:11:51 TRACE: FindFirstFile                    1
08/06/09 11:11:51 TRACE: FindFirstVolume                  1
08/06/09 11:11:51 TRACE: FindFirstVolumeMountPoint        4
08/06/09 11:11:51 TRACE: FindNextFile                     10004
08/06/09 11:11:51 TRACE: FindNextVolume                   6
08/06/09 11:11:51 TRACE: FindVolumeClose                  1
08/06/09 11:11:51 TRACE: FlushFileBuffers                 5
08/06/09 11:11:51 TRACE: GetCompressedFileSize            2
08/06/09 11:11:51 TRACE: GetDiskFreeSpaceEx               1
08/06/09 11:11:51 TRACE: GetFileAttributes                2
08/06/09 11:11:51 TRACE: GetFileSizeEx                    1
08/06/09 11:11:51 TRACE: GetVolumeInformation             3
08/06/09 11:11:51 TRACE: GetVolumePathName                3
08/06/09 11:11:51 TRACE: MapViewOfFile                    1
08/06/09 11:11:51 TRACE: QueryDosDevice                   7
08/06/09 11:11:51 TRACE: ReadFile                         197781
08/06/09 11:11:51 TRACE: RemoveDirectory                  1
08/06/09 11:11:51 TRACE: SetEndOfFile                     2
08/06/09 11:11:51 TRACE: SetFilePointer                   33
08/06/09 11:11:51 TRACE: SetFilePointerEx                 1
08/06/09 11:11:51 TRACE: UnmapViewOfFile                  1
08/06/09 11:11:51 TRACE: WriteFile                        197724
08/06/09 11:11:51 TRACE:
08/06/09 11:11:51
08/06/09 11:11:51 Final Analysis:
08/06/09 11:11:51 ---------------
08/06/09 11:11:51 Create Directory - PASSED
08/06/09 11:11:51 Disk Space - PASSED
08/06/09 11:11:51 Volume Information - PASSED
08/06/09 11:11:51 Query DOS Devices - PASSED
08/06/09 11:11:51 Traverse Volume Info - PASSED
08/06/09 11:11:51 Memory Mapped Files - PASSED
08/06/09 11:11:51 Reparse Points - PASSED
08/06/09 11:11:51 Sparse Files - PASSED
08/06/09 11:11:51 B2D Pre-allocation - PASSED
08/06/09 11:11:51 Random IO - PASSED
08/06/09 11:11:51 Default B2D Configuration - PASSED
08/06/09 11:11:51 Read buffer B2D Configuration - PASSED
08/06/09 11:11:51 No write buffering B2D Configuration - PASSED
08/06/09 11:11:51 File Handles - PASSED
08/06/09 11:11:51 Cleanup Directory - PASSED
08/06/09 11:11:51
08/06/09 11:11:51 The appliance has completed all tests successfully and should
08/06/09 11:11:51 be compatible with Backup Exec B2D technology.  If you are
08/06/09 11:11:51 experiencing issues with the appliance using an existing
08/06/09 11:11:51 Backup Exec installation, please contact Symantec Technical
08/06/09 11:11:51 Support for further assistance.
08/06/09 11:11:51
08/06/09 11:11:51 The results of this test have been placed into the following
08/06/09 11:11:51 log file:
08/06/09 11:11:51
08/06/09 11:11:51   C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\B2DTest.log
08/06/09 11:11:51
08/06/09 11:11:51 Please include this log file in any communication with your
08/06/09 11:11:51 vendor or Symantec Technical Support.
08/06/09 11:11:51
08/06/09 11:11:51 If you have any additional questions please review the
08/06/09 11:11:51 knowledge base article for this tool online at the Symantec
08/06/09 11:11:51 product support site:
08/06/09 11:11:51 http://entsupport.symantec.com/umi/v-275-10000



Chris_Craig
Level 3

.

Luke_Cassar
Level 5
I dont know if its related or not.. but I did see somewhere that a missing default share (\\servername\x$) can cause issues for some sofware including Exchange. This share is created by default for all drives except USB drives, because they are added after the OS boots. I think this was an issue related to restoring an exchange database to a USB disk, but it could potentially cause issues for other software.

On the server with the USB disk attached (which I assume is the BE media server) have you tried rebooting the machine while the USB drive is plugged in and switched on? This apparently creates the default share during Windows startup and fixed the issue.

Like I said.. dont know if its the right issue, but worth a shot.

Cheers.

Chris_Craig
Level 3
Interesting...although I did restart the server during the upgrade process from 12.0 to 12.5.

Chris_Craig
Level 3
Backup to tape was working as granular backup does not occur when going to tape.
I cleared space off one of the fixed disks and ran the backup, which also failed, so it wasn't specifically to USB.
Running the same job but with the granular backup unselected now reports "OK" when backing up to USB or fixed disk.
I see there are plenty of other threads on this issue, this one can be closed.

DominikG
Level 6
Partner Accredited

GRT backups to tape can also work, but as GRT is a disk-based technology, it should be done to disk.
Best practice is backup to disk and duplicate to tape.
Could you post the configuration of the backup, as well as the selectionlist?
The Exchange backups in my test environment only ran without problems after updating windows on both machines, updating the exchange and updating BE as well as the RAWS.

best regards

DOminik

mdzale
Level 3
Hello Chris,

I have on backup environment on which I setup GRT backup to disk and duplicate to tape and it works just fine.
I also have other backup environment on the other site wher GRT backup goes directly to tape and everything works fine.

But i had similar problem once so I suggest you try this:

- If the backup device specified in the backup job is a "backup-to-disk-folder" or "backup-to-disk device" that has not been written to before.
- Create and run a backup job that backs up at least one file and targets the "backup-to-disk-folder" or "backup-to-disk device".  This will initialize the "backup-to-disk-folder" or "backup-to-disk device" allowing the Test Run job to perform a "media check".



Regards,
Marinko