cancel
Showing results for 
Search instead for 
Did you mean: 

Backup to Freecom Network drive 500gb with BE 12.5

Jeroen_Kerkhof
Level 3
Hello,

I'm trying to setup a back-up job that put his data to a network drive in our network.

The only way I figured out was to add a B2D and put in the UNC path.
BE accepted my input and I configured the job.

When the job is running the only status message I get is queued.
There are three files made in the folder:
- @@@@@@@@.bkf
- Changer.cfg
- Folder.cfg

Here is what I have already tried:

- On my BE server (Windows 2003 SBS SR2, SP2) I can browse to the drive with the DNS name or IP with no problems.
- I can manually write files and delete them at the share.
- Update BE 12.5 to the max.

Is there an other way to configure BE to back-up to a network drive or does someone knows how to solve the queued issue?

Thanks in advance.

Best regards.

Jeroen Kerkhof
6 REPLIES 6

Larry_Fine
Moderator
Moderator
   VIP   
this may help troubleshoot http://support.veritas.com/docs/321584
can you run a test B2D job to a local disk drive? to a local tape drive?

Jeroen_Kerkhof
Level 3
Thank you for your response.

I've run the B2D tool and I get some errors in the log.
At Freecom disk I can change the setting of sleep time.

Now I will run the tool again.

Regards,

Jeroen Kerkhof
Automatisering Service Groep

Larry_Fine
Moderator
Moderator
   VIP   
What errors did you get?

Jeroen_Kerkhof
Level 3
Dear Larry,

Thanks for your response.

I have run the tool again after that I disabled the sleeping time on the Freecom network disk.
Below you can find the log.

06/19/09 10:39:04 -------------------------------------------------------------
06/19/09 10:39:04 Symantec Backup Exec B2D Compatibility Test
06/19/09 10:39:04 Build 12.6.2690
06/19/09 10:39:04 Copyright (C) 2008 Symantec Corporation. All rights reserved.
06/19/09 10:39:04
06/19/09 10:39:04 This tool can take up to several hours to complete. The
06/19/09 10:39:04 amount of time it takes is dependent on the host computer as
06/19/09 10:39:04 well as the underlying appliance technology. It is
06/19/09 10:39:04 recommend that this tool be run at a time when there will be
06/19/09 10:39:05 minimal impact on business operations.
06/19/09 10:39:05
06/19/09 10:39:05 For the tool to run successfully, the target location of the
06/19/09 10:39:05 test must contain at least 4,339,073,024 bytes of available
06/19/09 10:39:05 space. Furthermore, any credentials supplied must have
06/19/09 10:39:05 sufficient privileges to create, read, write, and delete
06/19/09 10:39:05 directories and files on the appliance.
06/19/09 10:39:05
06/19/09 10:39:05 Further information about this tool can be found online at
06/19/09 10:39:05 the Symantec product support site:
06/19/09 10:39:05 http://entsupport.symantec.com/umi/v-275-10000
06/19/09 10:39:57 Test Parameters:
06/19/09 10:39:57 Make : Freecom disk
06/19/09 10:39:57 Model : 500gb
06/19/09 10:39:57 Firmware: NAS2891-009B2 LOADER 3.2
06/19/09 10:39:57 Location: \\172.16.1.9\ASG_backup\B2DTestDir
06/19/09 10:39:57 Username: Current User (INTERN\administrator)
06/19/09 10:39:57
06/19/09 10:39:57 File Count : 10,000 files
06/19/09 10:39:57 Buffer size : 65,536 bytes
06/19/09 10:39:57 Mapped file size: 1,048,576 bytes
06/19/09 10:39:57 IO File Size : 4,296,015,872 bytes
06/19/09 10:39:57 Required Space : 4,339,073,024 bytes
06/19/09 10:39:57
06/19/09 10:39:57 Create Directory
06/19/09 10:39:57 TRACE: Entity exists
06/19/09 10:39:57 TRACE: Skipping entry .
06/19/09 10:39:57 TRACE: Skipping entry ..
06/19/09 10:39:58 ===> PASSED
06/19/09 10:39:58 Disk Space
06/19/09 10:39:58 ===> PASSED
06/19/09 10:39:58 Volume Information
06/19/09 10:39:58 ===> PASSED
06/19/09 10:39:58 Query DOS Devices
06/19/09 10:39:58 TRACE: DOSDEVICE: Global
06/19/09 10:39:58 TRACE: DOSDEVICE: D:
06/19/09 10:39:58 TRACE: DOSDEVICE: CpqCiCO51
06/19/09 10:39:58 TRACE: DOSDEVICE: CpqCiCO44
06/19/09 10:39:58 TRACE: DOSDEVICE: CpqCiCO38
06/19/09 10:39:58 TRACE: DOSDEVICE: Scsi3:
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO3
06/19/09 10:39:59 TRACE: DOSDEVICE: NDIS
06/19/09 10:39:59 TRACE: DOSDEVICE: DISPLAY1
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO4
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO52
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO45
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO39
06/19/09 10:39:59 TRACE: DOSDEVICE: DISPLAY2
06/19/09 10:39:59 TRACE: DOSDEVICE: PCI#VEN_14E4&DEV_1654&SUBSYS_00E30E11&REV_03#4&2183a681&0&10F0#{ad498944-762f-11d0-8dcb-00c04fc3358c}
06/19/09 10:39:59 TRACE: DOSDEVICE: Root#MS_PPPOEMINIPORT#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
06/19/09 10:39:59 TRACE: DOSDEVICE: PCI#VEN_1000&DEV_0030&SUBSYS_00DA0E11&REV_08#4&19638ecb&0&19E0#{2accfe60-c130-11d2-b082-00a0c91efb8b}
06/19/09 10:39:59 TRACE: DOSDEVICE: DmIoDaemon
06/19/09 10:39:59 TRACE: DOSDEVICE: Ip
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO5
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO53
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO46
06/19/09 10:39:59 TRACE: DOSDEVICE: DISPLAY3
06/19/09 10:39:59 TRACE: DOSDEVICE: E:
06/19/09 10:39:59 TRACE: DOSDEVICE: WMIAdminDevice
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO6
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO60
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO54
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO47
06/19/09 10:39:59 TRACE: DOSDEVICE: IPSECDev
06/19/09 10:39:59 TRACE: DOSDEVICE: DISPLAY4
06/19/09 10:39:59 TRACE: DOSDEVICE: Root#MS_NDISWANIP#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
06/19/09 10:39:59 TRACE: DOSDEVICE: TpFilter
06/19/09 10:39:59 TRACE: DOSDEVICE: WGUARDNT
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO7
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO61
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO55
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO48
06/19/09 10:39:59 TRACE: DOSDEVICE: Scsi4:
06/19/09 10:39:59 TRACE: DOSDEVICE: NDPROXY
06/19/09 10:39:59 TRACE: DOSDEVICE: {1BC4172A-04FE-4B5D-A2F2-F01813F7E91E}
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO8
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO62
06/19/09 10:39:59 TRACE: DOSDEVICE: CpqCiCO56
06/19/09 10:40:00 TRACE: DOSDEVICE: CpqCiCO49
06/19/09 10:40:00 TRACE: DOSDEVICE: STORAGE#Volume#1&3735c57b&0&LDM#{bfa122cd-f1dd-4fdf-8267-9c0d55be6220}#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
06/19/09 10:40:00 TRACE: DOSDEVICE: TAPE0
06/19/09 10:40:00 TRACE: DOSDEVICE: RdpDrDvMgr
06/19/09 10:40:00 TRACE: DOSDEVICE: ENTDRV
06/19/09 10:40:00 TRACE: DOSDEVICE: $VDMLPT1
06/19/09 10:40:00 TRACE: DOSDEVICE: CpqCiCO9
06/19/09 10:40:00 TRACE: DOSDEVICE: CpqCiCO63
06/19/09 10:40:00 TRACE: DOSDEVICE: CpqCiCO57
06/19/09 10:40:00 TRACE: DOSDEVICE: Root#*PNP0501#1_0_17_2_0_0#{4d36e978-e325-11ce-bfc1-08002be10318}
06/19/09 10:40:00 TRACE: DOSDEVICE: CompositeBattery
06/19/09 10:40:00 TRACE: DOSDEVICE: WMIDataDevice
06/19/09 10:40:00 TRACE: DOSDEVICE: Volume{c963f3fa-f6d6-48bd-85ae-626cf74db083}
06/19/09 10:40:00 TRACE: DOSDEVICE: CpqCiCO58
06/19/09 10:40:00 TRACE: DOSDEVICE: Volume{659e0633-930e-11da-8c02-806e6f6e6963}
06/19/09 10:40:00 TRACE: DOSDEVICE: COM1
06/19/09 10:40:00 TRACE: DOSDEVICE: {60AD256F-4AE4-41F9-BFB7-A1192213F19E}
06/19/09 10:40:00 TRACE: DOSDEVICE: Scsi5:
06/19/09 10:40:00 TRACE: DOSDEVICE: BackOfficeStorage
06/19/09 10:40:00 TRACE: DOSDEVICE: CpqCiCO59
06/19/09 10:40:00 TRACE: DOSDEVICE: COM2
06/19/09 10:40:00 TRACE: DOSDEVICE: {16B0E356-BBFD-46E5-A2AC-F751B3E7F18A}
06/19/09 10:40:00 TRACE: DOSDEVICE: CpqHlth
06/19/09 10:40:00 TRACE: DOSDEVICE: PIPE
06/19/09 10:40:00 TRACE: DOSDEVICE: CpqCiAO0
06/19/09 10:40:00 TRACE: DOSDEVICE: COM3
06/19/09 10:40:00 TRACE: DOSDEVICE: UNC
06/19/09 10:40:00 TRACE: DOSDEVICE: Root#MS_PTIMINIPORT#0000#{cac88484-7515-4c03-82e6-71a87abac361}
06/19/09 10:40:00 TRACE: DOSDEVICE: PCI#VEN_0E11&DEV_0046&SUBSYS_409C0E11&REV_01#6&2e5f39ce&0&20080010#{2accfe60-c130-11d2-b082-00a0c91efb8b}
06/19/09 10:40:00 TRACE: DOSDEVICE: Tcp
06/19/09 10:40:00 TRACE: DOSDEVICE: {E24554B2-432A-4A19-B715-F1F46CB71E01}
06/19/09 10:40:00 TRACE: DOSDEVICE: STORAGE#Volume#1&30a96598&0&Signature94C594C5Offset4000Length43D4337400#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
06/19/09 10:40:00 TRACE: DOSDEVICE: Scsi6:
06/19/09 10:40:00 TRACE: DOSDEVICE: HCD0
06/19/09 10:40:00 TRACE: DOSDEVICE: FltMgrMsg
06/19/09 10:40:00 TRACE: DOSDEVICE: Root#CNTX_VPCNETS2_MP#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
06/19/09 10:40:00 TRACE: DOSDEVICE: LCD
06/19/09 10:40:00 TRACE: DOSDEVICE: HCD1
06/19/09 10:40:00 TRACE: DOSDEVICE: Root#MS_PTIMINIPORT#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
06/19/09 10:40:00 TRACE: DOSDEVICE: PhysicalDrive0
06/19/09 10:40:00 TRACE: DOSDEVICE: PRN
06/19/09 10:40:00 TRACE: DOSDEVICE: USB#ROOT_HUB20#4&27805aac&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
06/19/09 10:40:00 TRACE: DOSDEVICE: HCD2
06/19/09 10:40:00 TRACE: DOSDEVICE: PhysicalDrive1
06/19/09 10:40:00 TRACE: DOSDEVICE: fsWrap
06/19/09 10:40:00 TRACE: DOSDEVICE: Root#CNTX_VPCNETS2_MP#0001#{ad498944-762f-11d0-8dcb-00c04fc3358c}
06/19/09 10:40:00 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_25AD&SUBSYS_32010E11&REV_02#3&61aaa01&0&EF#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
06/19/09 10:40:00 TRACE: DOSDEVICE: CdRom0
06/19/09 10:40:00 TRACE: DOSDEVICE: TpFilterAppQueue
06/19/09 10:40:00 TRACE: DOSDEVICE: Root#MS_PPTPMINIPORT#0000#{cac88484-7515-4c03-82e6-71a87abac361}
06/19/09 10:40:00 TRACE: DOSDEVICE: ACPI#FixedButton#2&daba3ff&0#{4afa3d53-74a7-11d0-be5e-00a0c9062857}
06/19/09 10:40:00 TRACE: DOSDEVICE: I:
06/19/09 10:40:00 TRACE: DOSDEVICE: VPCNetS2
06/19/09 10:40:00 TRACE: DOSDEVICE: ACPI#PNP0501#1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
06/19/09 10:40:00 TRACE: DOSDEVICE: PCI#VEN_1113&DEV_1211&SUBSYS_12111113&REV_10#5&6dba692&0&100210#{cac88484-7515-4c03-82e6-71a87abac361}
06/19/09 10:40:00 TRACE: DOSDEVICE: VPCNetS2_{1BC4172A-04FE-4B5D-A2F2-F01813F7E91E}
06/19/09 10:40:00 TRACE: DOSDEVICE: PCI#VEN_1000&DEV_0030&SUBSYS_00DA0E11&REV_08#4&19638ecb&0&18E0#{2accfe60-c130-11d2-b082-00a0c91efb8b}
06/19/09 10:40:01 TRACE: DOSDEVICE: {AACDEF9C-F4EC-4FAF-B0B9-43B76ACA4066}
06/19/09 10:40:01 TRACE: DOSDEVICE: ACPI#GenuineIntel_-_x86_Family_15_Model_4#_0#{97fadb10-4e33-40ae-359c-8bef029dbdd0}
06/19/09 10:40:01 TRACE: DOSDEVICE: ACPI#PNP0501#1#{4d36e978-e325-11ce-bfc1-08002be10318}
06/19/09 10:40:01 TRACE: DOSDEVICE: Root#MS_PPPOEMINIPORT#0000#{cac88484-7515-4c03-82e6-71a87abac361}
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO10
06/19/09 10:40:01 TRACE: DOSDEVICE: {0F9CB33B-7264-4BCF-B998-237B32B9ADBF}
06/19/09 10:40:01 TRACE: DOSDEVICE: PCI#VEN_1002&DEV_4752&SUBSYS_001E0E11&REV_27#4&2183a681&0&18F0#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}
06/19/09 10:40:01 TRACE: DOSDEVICE: Root#CNTX_VPCNETS2_MP#0001#{cac88484-7515-4c03-82e6-71a87abac361}
06/19/09 10:40:01 TRACE: DOSDEVICE: MountPointManager
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO11
06/19/09 10:40:01 TRACE: DOSDEVICE: SCSI#Sequential&Ven_HP&Prod_C7438A&Rev_V601#5&50cb971&0&030#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
06/19/09 10:40:01 TRACE: DOSDEVICE: Root#MS_NDISWANIP#0000#{cac88484-7515-4c03-82e6-71a87abac361}
06/19/09 10:40:01 TRACE: DOSDEVICE: Root#MS_L2TPMINIPORT#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
06/19/09 10:40:01 TRACE: DOSDEVICE: DmConfig
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO12
06/19/09 10:40:01 TRACE: DOSDEVICE: SCSI#Disk&Ven_HP&Prod_LOGICAL_VOLUME&Rev_2.84#7&3410afa7&0&040#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
06/19/09 10:40:01 TRACE: DOSDEVICE: WanArp
06/19/09 10:40:01 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_25A9&SUBSYS_32010E11&REV_02#3&61aaa01&0&E8#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
06/19/09 10:40:01 TRACE: DOSDEVICE: PCI#VEN_1113&DEV_1211&SUBSYS_12111113&REV_10#5&6dba692&0&100210#{ad498944-762f-11d0-8dcb-00c04fc3358c}
06/19/09 10:40:01 TRACE: DOSDEVICE: Root#ftdisk#0000#{53f5630e-b6bf-11d0-94f2-00a0c91efb8b}
06/19/09 10:40:01 TRACE: DOSDEVICE: Volume{659e0635-930e-11da-8c02-806e6f6e6963}
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO13
06/19/09 10:40:01 TRACE: DOSDEVICE: {E1C1B9E3-9046-4A93-A24D-0349F0DC2766}
06/19/09 10:40:01 TRACE: DOSDEVICE: Root#MS_L2TPMINIPORT#0000#{cac88484-7515-4c03-82e6-71a87abac361}
06/19/09 10:40:01 TRACE: DOSDEVICE: DmTrace
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO20
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO14
06/19/09 10:40:01 TRACE: DOSDEVICE: IDE#CdRomHL-DT-ST_CD-ROM_GCR-8486B_______________2.00____#5&2ac52874&0&0.0.0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
06/19/09 10:40:01 TRACE: DOSDEVICE: Root#dmio#0000#{53f5630e-b6bf-11d0-94f2-00a0c91efb8b}
06/19/09 10:40:01 TRACE: DOSDEVICE: NDISWANIP
06/19/09 10:40:01 TRACE: DOSDEVICE: Root#SYSTEM#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO21
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO15
06/19/09 10:40:01 TRACE: DOSDEVICE: Scsi0:
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO22
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO16
06/19/09 10:40:01 TRACE: DOSDEVICE: IDE#DiskWDC_WD1001FALS-00J7B0___________________05.00K05#5&6831c6d&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
06/19/09 10:40:01 TRACE: DOSDEVICE: ACPI#PNP0F13#4&1f443d2a&0#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
06/19/09 10:40:01 TRACE: DOSDEVICE: PCI#VEN_14E4&DEV_1654&SUBSYS_00E30E11&REV_03#4&2183a681&0&10F0#{cac88484-7515-4c03-82e6-71a87abac361}
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO30
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO23
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO17
06/19/09 10:40:01 TRACE: DOSDEVICE: PTILINK1
06/19/09 10:40:01 TRACE: DOSDEVICE: ACPI#PNP0501#0#{4d36e978-e325-11ce-bfc1-08002be10318}
06/19/09 10:40:01 TRACE: DOSDEVICE: PCI#VEN_0E11&DEV_B203&SUBSYS_B2060E11&REV_01#4&2183a681&0&20F0#{1cacf810-33e6-11d3-9fb1-00805fa60301}
06/19/09 10:40:01 TRACE: DOSDEVICE: Root#*PNP0501#1_0_17_2_0_0#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
06/19/09 10:40:01 TRACE: DOSDEVICE: Root#SYSTEM#0000#{4747b320-62ce-11cf-a5d6-28db04c10000}
06/19/09 10:40:01 TRACE: DOSDEVICE: Root#MS_PPTPMINIPORT#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO31
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO24
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO18
06/19/09 10:40:01 TRACE: DOSDEVICE: Scsi1:
06/19/09 10:40:01 TRACE: DOSDEVICE: SCSI2MediumChanger
06/19/09 10:40:01 TRACE: DOSDEVICE: NdisWan
06/19/09 10:40:01 TRACE: DOSDEVICE: WGUARDNT.OAS_CMN.3.3.0.276
06/19/09 10:40:01 TRACE: DOSDEVICE: NDISTAPI
06/19/09 10:40:01 TRACE: DOSDEVICE: LPT1
06/19/09 10:40:01 TRACE: DOSDEVICE: IPMULTICAST
06/19/09 10:40:01 TRACE: DOSDEVICE: LPTENUM#MicrosoftRawPort#6&13179365&0&LPT1#{811fc6a5-f728-11d0-a537-0000f8753ed1}
06/19/09 10:40:01 TRACE: DOSDEVICE: PTILINK2
06/19/09 10:40:01 TRACE: DOSDEVICE: DmLoader
06/19/09 10:40:01 TRACE: DOSDEVICE: Shadow
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO32
06/19/09 10:40:01 TRACE: DOSDEVICE: CpqCiCO25
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO19
06/19/09 10:40:02 TRACE: DOSDEVICE: VMM
06/19/09 10:40:02 TRACE: DOSDEVICE: PTILINK3
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO33
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO26
06/19/09 10:40:02 TRACE: DOSDEVICE: FltMgr
06/19/09 10:40:02 TRACE: DOSDEVICE: FtControl
06/19/09 10:40:02 TRACE: DOSDEVICE: ACPI#PNP0303#4&1f443d2a&0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
06/19/09 10:40:02 TRACE: DOSDEVICE: VPCNetS2_{B14DCC17-864A-4D32-BAFD-3625F3E28614}
06/19/09 10:40:02 TRACE: DOSDEVICE: USB#ROOT_HUB#4&24b43adc&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
06/19/09 10:40:02 TRACE: DOSDEVICE: Root#CNTX_VPCNETS2_MP#0000#{cac88484-7515-4c03-82e6-71a87abac361}
06/19/09 10:40:02 TRACE: DOSDEVICE: C:
06/19/09 10:40:02 TRACE: DOSDEVICE: Volume{bfa122cd-f1dd-4fdf-8267-9c0d55be6220}
06/19/09 10:40:02 TRACE: DOSDEVICE: ExchangeIfs
06/19/09 10:40:02 TRACE: DOSDEVICE: MAILSLOT
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO34
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO27
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO40
06/19/09 10:40:02 TRACE: DOSDEVICE: NaiAvFilter1
06/19/09 10:40:02 TRACE: DOSDEVICE: AUX
06/19/09 10:40:02 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_25AA&SUBSYS_32010E11&REV_02#3&61aaa01&0&E9#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
06/19/09 10:40:02 TRACE: DOSDEVICE: ACPI#ThermalZone#THM0#{4afa3d51-74a7-11d0-be5e-00a0c9062857}
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO35
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO28
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO0
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO41
06/19/09 10:40:02 TRACE: DOSDEVICE: GLOBALROOT
06/19/09 10:40:02 TRACE: DOSDEVICE: STORAGE#Volume#1&3735c57b&0&LDM#{c963f3fa-f6d6-48bd-85ae-626cf74db083}#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
06/19/09 10:40:02 TRACE: DOSDEVICE: NUL
06/19/09 10:40:02 TRACE: DOSDEVICE: Scsi2:
06/19/09 10:40:02 TRACE: DOSDEVICE: IDE#CdRomHL-DT-ST_CD-ROM_GCR-8486B_______________2.00____#5&2ac52874&0&0.0.0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}
06/19/09 10:40:02 TRACE: DOSDEVICE: Root#RDP_MOU#0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
06/19/09 10:40:02 TRACE: DOSDEVICE: Ndisuio
06/19/09 10:40:02 TRACE: DOSDEVICE: ACPI#PNP0501#0#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
06/19/09 10:40:02 TRACE: DOSDEVICE: ACPI#GenuineIntel_-_x86_Family_15_Model_4#_1#{97fadb10-4e33-40ae-359c-8bef029dbdd0}
06/19/09 10:40:02 TRACE: DOSDEVICE: {B14DCC17-864A-4D32-BAFD-3625F3E28614}
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO36
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO29
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO1
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO42
06/19/09 10:40:02 TRACE: DOSDEVICE: Root#RDP_KBD#0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
06/19/09 10:40:02 TRACE: DOSDEVICE: USB#ROOT_HUB#4&312b1c17&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO37
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO50
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO43
06/19/09 10:40:02 TRACE: DOSDEVICE: CpqCiCO2
06/19/09 10:40:02 TRACE: DOSDEVICE: ACPI#PNP0400#5&13608cec&0#{97f76ef0-f883-11d0-af1f-0000f800845c}
06/19/09 10:40:02 TRACE: DOSDEVICE: DmInfo
06/19/09 10:40:02 ===> PASSED
06/19/09 10:40:02 Traverse Volume Info
06/19/09 10:40:02 TRACE: Volume: \\?\Volume{659e0635-930e-11da-8c02-806e6f6e6963}\
06/19/09 10:40:02 TRACE: Device: \Device\HarddiskVolume1
06/19/09 10:40:02 TRACE: No mount points detected
06/19/09 10:40:02 TRACE: Path Name: C:\
06/19/09 10:40:02 TRACE: Volume: \\?\Volume{659e0633-930e-11da-8c02-806e6f6e6963}\
06/19/09 10:40:02 TRACE: Device: \Device\CdRom0
06/19/09 10:40:02 TRACE: Device is a CD ROM device - skipping mount point enumeration
06/19/09 10:40:02 TRACE: Path Name: E:\
06/19/09 10:40:02 TRACE: Volume: \\?\Volume{c963f3fa-f6d6-48bd-85ae-626cf74db083}\
06/19/09 10:40:02 TRACE: Device: \Device\HarddiskDmVolumes\SbssvrDg0\Volume1
06/19/09 10:40:02 TRACE: No mount points detected
06/19/09 10:40:02 TRACE: Path Name: I:\
06/19/09 10:40:02 TRACE: Volume: \\?\Volume{bfa122cd-f1dd-4fdf-8267-9c0d55be6220}\
06/19/09 10:40:03 TRACE: Device: \Device\HarddiskDmVolumes\SbssvrDg0\Volume2
06/19/09 10:40:03 TRACE: No mount points detected
06/19/09 10:40:03 TRACE: Path Name: D:\
06/19/09 10:40:03 ===> PASSED
06/19/09 10:40:03 Memory Mapped Files
06/19/09 10:40:03 TRACE: Initialize memory map
06/19/09 10:40:03 TRACE: Verify memory map
06/19/09 10:40:03 ===> PASSED
06/19/09 10:40:04 Reparse Points
06/19/09 10:40:04 ===> WARNING - Reparse points not supported on appliance: (0x32) The request is not supported.
06/19/09 10:40:04 Sparse Files
06/19/09 10:40:04 ===> WARNING - Sparse files not supported on appliance: (0x32) The request is not supported.
06/19/09 10:40:04 B2D Pre-allocation
06/19/09 10:40:04 TRACE: Positioning file pointer
06/19/09 10:40:04 TRACE: Writing a single buffer to extend file
06/19/09 10:40:04 TRACE: Setting end of file
06/19/09 10:40:04 ===> PASSED
06/19/09 10:40:04 Random IO
06/19/09 10:40:04 TRACE: Seeking to offset 0
06/19/09 10:40:04 TRACE: Writing 67108864 bytes to file
06/19/09 10:40:40 TRACE: Seeking to offset 0
06/19/09 10:40:40 TRACE: Reading 67108864 bytes from file
06/19/09 10:40:40 TRACE: Testing end of file
06/19/09 10:40:40 TRACE: Seeking to offset 1048576
06/19/09 10:40:40 TRACE: Reading 1048576 bytes from file
06/19/09 10:40:40 TRACE: Writing 1048576 bytes to file
06/19/09 10:40:40 TRACE: Seeking to offset 67108864
06/19/09 10:40:40 TRACE: Writing 655360 bytes to file
06/19/09 10:40:40 TRACE: Seeking to offset 67108864
06/19/09 10:40:40 TRACE: Reading 655360 bytes from file
06/19/09 10:40:40 TRACE: Testing end of file
06/19/09 10:40:40 TRACE: Seeking to offset 1048576
06/19/09 10:40:40 TRACE: Setting end of file
06/19/09 10:40:42 TRACE: Testing end of file
06/19/09 10:40:42 TRACE: Seeking to offset 0
06/19/09 10:40:42 TRACE: Reading 1048576 bytes from file
06/19/09 10:40:42 TRACE: Writing 1048576 bytes to file
06/19/09 10:40:42 TRACE: Testing end of file
06/19/09 10:40:42 TRACE: Seeking to offset 0
06/19/09 10:40:42 TRACE: Reading 2097152 bytes from file
06/19/09 10:40:42 TRACE: Testing end of file
06/19/09 10:40:42 TRACE: Seeking to offset 0
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping 131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping 131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping 131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping 131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping 131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping 131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping 131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping 131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping 131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping 131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping 131072 bytes
06/19/09 10:40:42 TRACE: Seeking to offset 2031616
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping -131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping -131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping -131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping -131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping -131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping -131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping -131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping -131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping -131072 bytes
06/19/09 10:40:42 TRACE: Reading 65536 bytes from file
06/19/09 10:40:42 TRACE: Skipping -131072 bytes
06/19/09 10:40:43 TRACE: Reading 65536 bytes from file
06/19/09 10:40:43 TRACE: Skipping -131072 bytes
06/19/09 10:40:43 ===> PASSED
06/19/09 10:40:43 Default B2D Configuration
06/19/09 10:40:43 TRACE: Writing to file
06/19/09 11:14:37 TRACE: Reading from file
06/19/09 11:27:50 ===> PASSED
06/19/09 11:27:50 Read buffer B2D Configuration
06/19/09 11:27:52 TRACE: Writing to file
06/19/09 12:02:19 TRACE: Reading from file
06/19/09 12:16:52 ===> PASSED
06/19/09 12:16:52 No write buffering B2D Configuration
06/19/09 12:16:53 TRACE: Writing to file
06/19/09 12:52:10 TRACE: Reading from file
06/19/09 13:05:28 ===> PASSED
06/19/09 13:05:28 File Handles
06/19/09 13:06:05 ===> WARNING - Unable to create test file: (0x4) The system cannot open the file.
06/19/09 13:06:05 Cleanup Directory
06/19/09 13:06:05 TRACE: Skipping entry .
06/19/09 13:06:05 TRACE: Skipping entry ..
06/19/09 13:06:19 ===> PASSED
06/19/09 13:06:19
06/19/09 13:06:19 Total Tests Run: 15
06/19/09 13:06:19 Passed: 12
06/19/09 13:06:19 Failed: 0
06/19/09 13:06:19 Warned: 3
06/19/09 13:06:19
06/19/09 13:06:19 TRACE:
06/19/09 13:06:19 TRACE: Functions called:
06/19/09 13:06:19 TRACE: -----------------
06/19/09 13:06:19 TRACE: CloseHandle 506
06/19/09 13:06:19 TRACE: CreateDirectory 1
06/19/09 13:06:19 TRACE: CreateFile 506
06/19/09 13:06:19 TRACE: CreateFileMapping 1
06/19/09 13:06:19 TRACE: DeleteFile 501
06/19/09 13:06:19 TRACE: FindFirstFile 2
06/19/09 13:06:19 TRACE: FindFirstVolume 1
06/19/09 13:06:19 TRACE: FindFirstVolumeMountPoint 3
06/19/09 13:06:19 TRACE: FindNextFile 505
06/19/09 13:06:19 TRACE: FindNextVolume 4
06/19/09 13:06:19 TRACE: FindVolumeClose 1
06/19/09 13:06:19 TRACE: FlushFileBuffers 4
06/19/09 13:06:19 TRACE: GetDiskFreeSpaceEx 1
06/19/09 13:06:19 TRACE: GetFileAttributes 1
06/19/09 13:06:19 TRACE: GetFileSizeEx 1
06/19/09 13:06:20 TRACE: GetVolumeInformation 3
06/19/09 13:06:20 TRACE: GetVolumePathName 3
06/19/09 13:06:20 TRACE: GetVolumePathNamesForVolumeName 4
06/19/09 13:06:20 TRACE: MapViewOfFile 1
06/19/09 13:06:20 TRACE: QueryDosDevice 5
06/19/09 13:06:20 TRACE: ReadFile 197781
06/19/09 13:06:20 TRACE: RemoveDirectory 2
06/19/09 13:06:20 TRACE: SetEndOfFile 2
06/19/09 13:06:20 TRACE: SetFilePointer 33
06/19/09 13:06:20 TRACE: UnmapViewOfFile 1
06/19/09 13:06:20 TRACE: WriteFile 197723
06/19/09 13:06:20 TRACE:
06/19/09 13:06:20
06/19/09 13:06:20 Final Analysis:
06/19/09 13:06:20 ---------------
06/19/09 13:06:20 Create Directory - PASSED
06/19/09 13:06:20 Disk Space - PASSED
06/19/09 13:06:20 Volume Information - PASSED
06/19/09 13:06:20 Query DOS Devices - PASSED
06/19/09 13:06:20 Traverse Volume Info - PASSED
06/19/09 13:06:20 Memory Mapped Files - PASSED
06/19/09 13:06:20 Reparse Points - WARNING - Reparse points not supported on appliance: (0x32) The request is not supported.
06/19/09 13:06:20 The appliance does not support reparse points. Some
06/19/09 13:06:20 of the advanced B2D technologies such as GRT may not
06/19/09 13:06:20 function.
06/19/09 13:06:20
06/19/09 13:06:20 For GRT to function correctly, either the B2D path
06/19/09 13:06:20 or the temporary path for GRT operations must be an
06/19/09 13:06:20 NTFS partition that supports reparse points. If this
06/19/09 13:06:21 is not the case, GRT operations will fail.
06/19/09 13:06:21
06/19/09 13:06:21 For more information on this topic please refer to
06/19/09 13:06:21 the Backup Exec Administrators Guide.
06/19/09 13:06:21 Sparse Files - WARNING - Sparse files not supported on appliance: (0x32) The request is not supported.
06/19/09 13:06:21 The appliance does not support sparse files. Some
06/19/09 13:06:21 of the advanced B2D technologies such as GRT may
06/19/09 13:06:21 not function.
06/19/09 13:06:21
06/19/09 13:06:21 For GRT to function correctly, either the B2D
06/19/09 13:06:21 path or the temporary path for GRT operations
06/19/09 13:06:21 must be an NTFS partition that supports sparse
06/19/09 13:06:21 files. If this is not the case, GRT operations
06/19/09 13:06:21 fail.
06/19/09 13:06:21
06/19/09 13:06:21 For more information on this topic please refer
06/19/09 13:06:21 to the Backup Exec Administrators Guide.
06/19/09 13:06:21 B2D Pre-allocation - PASSED
06/19/09 13:06:21 Random IO - PASSED
06/19/09 13:06:21 Default B2D Configuration - PASSED
06/19/09 13:06:21 Read buffer B2D Configuration - PASSED
06/19/09 13:06:21 No write buffering B2D Configuration - PASSED
06/19/09 13:06:21 File Handles - WARNING - Unable to create test file: (0x4) The system cannot open the file.
06/19/09 13:06:21 The appliance is unable to maintain a large quantity
06/19/09 13:06:21 of open file handles. B2D technologies such as GRT
06/19/09 13:06:21 may not function correctly. The test could only open
06/19/09 13:06:21 496 of 10,000 files.
06/19/09 13:06:21
06/19/09 13:06:21 Check the appliance configuration to see if there is
06/19/09 13:06:21 a way to increase the number of open files the
06/19/09 13:06:21 appliance can support.
06/19/09 13:06:22 Cleanup Directory - PASSED
06/19/09 13:06:22
06/19/09 13:06:22 One or more of the test have completed with warnings.
06/19/09 13:06:22 Backup Exec should be compatible with the appliance; however,
06/19/09 13:06:22 some features or functions may not be available.
06/19/09 13:06:22
06/19/09 13:06:22 The results of this test have been placed into the following
06/19/09 13:06:22 log file:
06/19/09 13:06:22
06/19/09 13:06:22 C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\B2DTest.log
06/19/09 13:06:22
06/19/09 13:06:22 Please include this log file in any communication with your
06/19/09 13:06:22 vendor or Symantec Technical Support.
06/19/09 13:06:22
06/19/09 13:06:22 If you have any additional questions please review the
06/19/09 13:06:22 knowledge base article for this tool online at the Symantec
06/19/09 13:06:22 product support site:
06/19/09 13:06:22 http://entsupport.symantec.com/umi/v-275-10000

In the log there is a line 06/19/09 13:06:21 File Handles - WARNING - Unable to create test file: (0x4) The system cannot open the file.
It looks like that the disk doesn't support a large quantity of open file handles. In my opinion Backup Exec does write one file at a time to disk.
At the webpage http://seer.entsupport.symantec.com/docs/321584.htm I can't find more information about the warning message.

What do you think about this?

Thanks in advance.

Regards,

Jeroen

Larry_Fine
Moderator
Moderator
   VIP   
The test results from that look like the device shoul work fine for file backups, but would NOT be good for GRT backups.  So that puts us back to your job queued problem.

Do you have any other backup targets?  a Tape drive?  a Local B2D target?  If not, I suggest creating a local B2D target and creating a tiny test backup to see if BE can run ANY jobs.  This may help http://seer.entsupport.symantec.com/docs/191594.htm

Jeroen_Kerkhof
Level 3
Our server has a tape streamer and makes every night a full backup.
I have tried a couple of times the local disk back-up and it works fine.

You mention in your post GRT back-up. I don't know what that is.
I will look tomorrow on google for information about it.