cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Veritas.com
Support

Using a Netgear ReadyNAS 1100 as a Backup-To-Disk Folder target

paul_klump
Level 3

‎02-09-2010 05:44 AM

I'm currently in the midst of installing a backup solution on my work network.  I have a server running Windows 2003 Server and have installed BackupExec 12.3.  On this same network, I have a Netgear ReadyNAS 1100.  I am able to connect to the ReadyNAS from the Win2k3 server via SMB and NFS (I installed Windows Services for UNIX), and am able to read and write files to the ReadyNAS when I'm connected via either protocol.

I would like to set up a Backup-To-Disk folder on the ReadyNAS to hold the BE backup files.  I've done some searching on the Internet, and have found various articles that state that I should be able to use a UNC path as the target of a B2D folder, but whenever I attempt a backup, three files get created on the target (a file w/ a .bkf extension, changer.cfg, and Folder.cfg), but then the backup job runs indefinitely without any other files being created.

When I attempt to browse different backup folder locations, I only get so far in the resource tree before it stops.  I've attached the screenshot below; I'm not able to descend down farther into CSS-READYNAS, for example, while if I was browsing through My Network Place, I'm able descend to in the CSS-READYNAS workgroup, as well as into Default LAN.

choose backup location folder - creating b2d location 020410.jpg

While I attempted to browse the network locations above, I ran the Wireshare newtork protocol analyzer on the server running BE, and I didn't see any traffic directed to any newtork hosts.  I created an account for the various BE services to run as, so they are not running as the Local System account.  What, if any, other credentials need to be configured within BE in order for the software to be able to connect to network resources via SMB or NFS?

Any assistance you could give me on this issue woudl be greatly appreciated.  Thanks in advance!

Paul
0 Kudos
9 REPLIES 9

James_McKey
Level 5
Employee Certified

‎02-09-2010 06:05 AM

1. I assume you meant you are running Backup Exec 12.5?
2. What service packs and hotfixes for BE?
3. Is the BE media server in a Domain? If so, the domain account that the Backup Exec Device and Media Service is running on will be what we use to access any B2D folder. If the NAS box isn't in the domain then I'm guessing you've created a machine account on the NAS that has full rights. However, that could be a problem as it might not behave like a Windows box and try the local version of that account. In other words, it might see we are trying to access it as domain\account and just fail that back; however the ability to create some of the necessary files would not seem to indicate that being the issue.

Many NAS boxes do support adding themselves to an AD setup with a domain account, so check into that as well, if you haven't already. Also, I'm going to request a review of this from someone with more recent experience in troubleshooting these kind of issues. My knowledge is a bit rusty in this specific scenario and this exact set of symptoms does not sound familiar.

4. Also, can you post the exact 'access denied' output from the 'Backup to Disk test tool' you mentioned on Twitter and the switches you ran it with?
0 Kudos

paul_klump
Level 3

‎02-09-2010 08:50 AM

James,

1) You are correct, I am runing 12.5, I apologize for the typo.
2) The Media Server is running version 12.5 Rev 2213, and I had installed Service Pack 3
3) Neither the BE media server or the ReadyNAS are part of a domain.  Both hosts are configured to be a member of the same workgroup.

I did make some configuration changes on my side.  I made sure that there was an account on the ReadyNAS whose user name/pwd matched the account I'm using to run the BE services, and that I was able to access this account's home directory from the backup server via SMB.  After this test, I went ino the BE management console and I was able to drill down farther in the Resource tree in the Choose Backup Folder Location window.  I was then able to choose \\css-readynas\cssbackup as a backup location; however, when I attempted a test backup, I encountered the same issue with only three files being created, and the backup job just runs indefinitely without any additional files being written.

4)  I re-ran the B2D test, and it was able to complete.  Below is the log data from the B2DTest.log file, please let me know if you need any further information.

================================================================================
02/09/10 10:26:13 -------------------------------------------------------------
02/09/10 10:26:13 Symantec Backup Exec B2D Compatibility Test
02/09/10 10:26:13 Build 12.6.2729
02/09/10 10:26:13 Copyright (C) 2008 Symantec Corporation. All rights reserved.
02/09/10 10:26:13
02/09/10 10:26:13 This tool can take up to several hours to complete.  The
02/09/10 10:26:13 amount of time it takes is dependent on the host computer as
02/09/10 10:26:13 well as the underlying appliance technology.  It is
02/09/10 10:26:13 recommend that this tool be run at a time when there will be
02/09/10 10:26:13 minimal impact on business operations.
02/09/10 10:26:13
02/09/10 10:26:13 For the tool to run successfully, the target location of the
02/09/10 10:26:13 test must contain at least 4,339,073,024 bytes of available
02/09/10 10:26:13 space.  Furthermore, any credentials supplied must have
02/09/10 10:26:13 sufficient privileges to create, read, write, and delete
02/09/10 10:26:13 directories and files on the appliance.
02/09/10 10:26:13
02/09/10 10:26:13 Further information about this tool can be found online at
02/09/10 10:26:13 the Symantec product support site:
02/09/10 10:26:13   http://entsupport.symantec.com/umi/v-275-10000
02/09/10 10:27:19 Test Parameters:
02/09/10 10:27:19     Make    : Netgear
02/09/10 10:27:19     Model   : ReadyNAS 1100
02/09/10 10:27:19     Firmware: UNKNOWN
02/09/10 10:27:19     Location: \\css-readynas\cssbackup\B2DTestDir
02/09/10 10:27:19     Username: .\cssbackup
02/09/10 10:27:19
02/09/10 10:27:19     File Count      : 10,000 files
02/09/10 10:27:19     Buffer size     : 65,536 bytes
02/09/10 10:27:19     Mapped file size: 1,048,576 bytes
02/09/10 10:27:20     IO File Size    : 4,296,015,872 bytes
02/09/10 10:27:20     Required Space  : 4,339,073,024 bytes
02/09/10 10:27:20
02/09/10 10:27:20 TRACE: Logging on as user .\cssbackup
02/09/10 10:27:20 Create Directory
02/09/10 10:27:20     ===> PASSED
02/09/10 10:27:20 Disk Space
02/09/10 10:27:20     ===> PASSED
02/09/10 10:27:20 Volume Information
02/09/10 10:27:20     ===> PASSED
02/09/10 10:27:20 Query DOS Devices
02/09/10 10:27:20 TRACE: DOSDEVICE: Global
02/09/10 10:27:20 TRACE: DOSDEVICE: NDIS
02/09/10 10:27:20 TRACE: DOSDEVICE: NPF_{54C7D140-09EF-11D1-B25A-F5FE627ED95E}
02/09/10 10:27:20 TRACE: DOSDEVICE: DISPLAY1
02/09/10 10:27:20 TRACE: DOSDEVICE: NPF_{AB9383DF-B358-460D-A555-3DB57A2309BD}
02/09/10 10:27:21 TRACE: DOSDEVICE: DISPLAY2
02/09/10 10:27:21 TRACE: DOSDEVICE: Root#MS_PPPOEMINIPORT#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
02/09/10 10:27:21 TRACE: DOSDEVICE: {9A623C7F-EB42-4D24-993C-BFC0146F1F8C}
02/09/10 10:27:21 TRACE: DOSDEVICE: DmIoDaemon
02/09/10 10:27:21 TRACE: DOSDEVICE: NPF_{226B4C73-6FC7-43F5-A5D0-9899364BD34F}
02/09/10 10:27:21 TRACE: DOSDEVICE: Ip
02/09/10 10:27:21 TRACE: DOSDEVICE: USB#Vid_046b&Pid_ff10#6&14ff2931&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
02/09/10 10:27:21 TRACE: DOSDEVICE: DISPLAY3
02/09/10 10:27:21 TRACE: DOSDEVICE: WMIAdminDevice
02/09/10 10:27:21 TRACE: DOSDEVICE: IPSECDev
02/09/10 10:27:21 TRACE: DOSDEVICE: DISPLAY4
02/09/10 10:27:21 TRACE: DOSDEVICE: Root#MS_NDISWANIP#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
02/09/10 10:27:21 TRACE: DOSDEVICE: NDPROXY
02/09/10 10:27:21 TRACE: DOSDEVICE: RdpDrDvMgr
02/09/10 10:27:21 TRACE: DOSDEVICE: RpcXdr
02/09/10 10:27:21 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_1010&SUBSYS_10118086&REV_03#4&394cac81&0&0808#{cac88484-7515-4c03-82e6-71a87abac361}
02/09/10 10:27:21 TRACE: DOSDEVICE: NPF_{4FCCE3CA-647B-4BCF-9018-32DA64E4E603}
02/09/10 10:27:21 TRACE: DOSDEVICE: TM_CFW
02/09/10 10:27:21 TRACE: DOSDEVICE: WMIDataDevice
02/09/10 10:27:21 TRACE: DOSDEVICE: NPF_{04183C65-E7B6-49CC-96E3-F889093A57CF}
02/09/10 10:27:21 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_1010&SUBSYS_10118086&REV_03#4&394cac81&0&1008#{ad498944-762f-11d0-8dcb-00c04fc3358c}
02/09/10 10:27:21 TRACE: DOSDEVICE: ACPI#AuthenticAMD_-_x86_Family_15_Model_37#_0#{97fadb10-4e33-40ae-359c-8bef029dbdd0}
02/09/10 10:27:21 TRACE: DOSDEVICE: PIPE
02/09/10 10:27:21 TRACE: DOSDEVICE: {C004E726-369F-40EA-A3FE-65E58630C38D}
02/09/10 10:27:21 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_1010&SUBSYS_10118086&REV_03#4&394cac81&0&1008#{cac88484-7515-4c03-82e6-71a87abac361}
02/09/10 10:27:21 TRACE: DOSDEVICE: UNC
02/09/10 10:27:21 TRACE: DOSDEVICE: NPF_{641C7090-F0E4-41FD-8E2A-6EAD1A7AAD3F}
02/09/10 10:27:21 TRACE: DOSDEVICE: NPF_{1CBC7174-C32E-41F4-B78B-C3350FD54212}
02/09/10 10:27:21 TRACE: DOSDEVICE: NPF_{C004E726-369F-40EA-A3FE-65E58630C38D}
02/09/10 10:27:21 TRACE: DOSDEVICE: VsapiNt
02/09/10 10:27:21 TRACE: DOSDEVICE: PCI#VEN_1022&DEV_7464&SUBSYS_74641022&REV_0B#4&310b4f6b&0&0130#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
02/09/10 10:27:21 TRACE: DOSDEVICE: Root#MS_PTIMINIPORT#0000#{cac88484-7515-4c03-82e6-71a87abac361}
02/09/10 10:27:21 TRACE: DOSDEVICE: Tcp
02/09/10 10:27:21 TRACE: DOSDEVICE: HCD0
02/09/10 10:27:21 TRACE: DOSDEVICE: FltMgrMsg
02/09/10 10:27:21 TRACE: DOSDEVICE: LCD
02/09/10 10:27:21 TRACE: DOSDEVICE: HCD1
02/09/10 10:27:22 TRACE: DOSDEVICE: USB#ROOT_HUB#5&195846ba&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
02/09/10 10:27:22 TRACE: DOSDEVICE: Root#MS_PTIMINIPORT#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
02/09/10 10:27:22 TRACE: DOSDEVICE: {04183C65-E7B6-49CC-96E3-F889093A57CF}
02/09/10 10:27:22 TRACE: DOSDEVICE: PhysicalDrive0
02/09/10 10:27:22 TRACE: DOSDEVICE: NfsRdr
02/09/10 10:27:22 TRACE: DOSDEVICE: ACPI#PNP0303#4&26dcf72f&0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
02/09/10 10:27:22 TRACE: DOSDEVICE: PRN
02/09/10 10:27:22 TRACE: DOSDEVICE: SAC
02/09/10 10:27:22 TRACE: DOSDEVICE: fsWrap
02/09/10 10:27:22 TRACE: DOSDEVICE: {641C7090-F0E4-41FD-8E2A-6EAD1A7AAD3F}
02/09/10 10:27:22 TRACE: DOSDEVICE: NPF_{C3DB14B8-492B-41AB-9415-E2F30A079025}
02/09/10 10:27:22 TRACE: DOSDEVICE: {226B4C73-6FC7-43F5-A5D0-9899364BD34F}
02/09/10 10:27:22 TRACE: DOSDEVICE: Root#MS_PPTPMINIPORT#0000#{cac88484-7515-4c03-82e6-71a87abac361}
02/09/10 10:27:22 TRACE: DOSDEVICE: ACPI#FixedButton#2&daba3ff&0#{4afa3d53-74a7-11d0-be5e-00a0c9062857}
02/09/10 10:27:22 TRACE: DOSDEVICE: ACPI#PNP0C0C#aa#{4afa3d53-74a7-11d0-be5e-00a0c9062857}
02/09/10 10:27:22 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_1010&SUBSYS_10118086&REV_03#4&394cac81&0&1108#{cac88484-7515-4c03-82e6-71a87abac361}
02/09/10 10:27:22 TRACE: DOSDEVICE: Portmap
02/09/10 10:27:22 TRACE: DOSDEVICE: PCI#VEN_1000&DEV_0050&SUBSYS_30601000&REV_02#4&3074bcc0&0&1810#{2accfe60-c130-11d2-b082-00a0c91efb8b}
02/09/10 10:27:22 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_1010&SUBSYS_10118086&REV_03#4&394cac81&0&0908#{ad498944-762f-11d0-8dcb-00c04fc3358c}
02/09/10 10:27:22 TRACE: DOSDEVICE: USB#ROOT_HUB#5&31f16e64&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
02/09/10 10:27:22 TRACE: DOSDEVICE: Root#MS_PPPOEMINIPORT#0000#{cac88484-7515-4c03-82e6-71a87abac361}
02/09/10 10:27:22 TRACE: DOSDEVICE: {C3DB14B8-492B-41AB-9415-E2F30A079025}
02/09/10 10:27:22 TRACE: DOSDEVICE: MountPointManager
02/09/10 10:27:22 TRACE: DOSDEVICE: Root#MS_NDISWANIP#0000#{cac88484-7515-4c03-82e6-71a87abac361}
02/09/10 10:27:22 TRACE: DOSDEVICE: Root#MS_L2TPMINIPORT#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
02/09/10 10:27:22 TRACE: DOSDEVICE: DmConfig
02/09/10 10:27:22 TRACE: DOSDEVICE: STORAGE#Volume#1&30a96598&0&SignatureD281D281Offset7E00Length10A8527600#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
02/09/10 10:27:22 TRACE: DOSDEVICE: WanArp
02/09/10 10:27:22 TRACE: DOSDEVICE: PCI#VEN_1002&DEV_4752&SUBSYS_4732108E&REV_27#4&310b4f6b&0&1830#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}
02/09/10 10:27:22 TRACE: DOSDEVICE: Root#ftdisk#0000#{53f5630e-b6bf-11d0-94f2-00a0c91efb8b}
02/09/10 10:27:22 TRACE: DOSDEVICE: SCSI#Disk&Ven_LSILOGIC&Prod_Logical_Volume&Rev_3000#5&e7b2690&0&000200#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
02/09/10 10:27:22 TRACE: DOSDEVICE: Root#MS_L2TPMINIPORT#0000#{cac88484-7515-4c03-82e6-71a87abac361}
02/09/10 10:27:22 TRACE: DOSDEVICE: DmTrace
02/09/10 10:27:22 TRACE: DOSDEVICE: Root#SYSTEM#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
02/09/10 10:27:22 TRACE: DOSDEVICE: {AB9383DF-B358-460D-A555-3DB57A2309BD}
02/09/10 10:27:23 TRACE: DOSDEVICE: NDISWANIP
02/09/10 10:27:23 TRACE: DOSDEVICE: Root#dmio#0000#{53f5630e-b6bf-11d0-94f2-00a0c91efb8b}
02/09/10 10:27:23 TRACE: DOSDEVICE: NPF_{9A623C7F-EB42-4D24-993C-BFC0146F1F8C}
02/09/10 10:27:23 TRACE: DOSDEVICE: Scsi0:
02/09/10 10:27:23 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_1010&SUBSYS_10118086&REV_03#4&394cac81&0&0908#{cac88484-7515-4c03-82e6-71a87abac361}
02/09/10 10:27:23 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_1010&SUBSYS_10118086&REV_03#4&394cac81&0&0808#{ad498944-762f-11d0-8dcb-00c04fc3358c}
02/09/10 10:27:23 TRACE: DOSDEVICE: TMFilter
02/09/10 10:27:23 TRACE: DOSDEVICE: Root#SYSTEM#0000#{4747b320-62ce-11cf-a5d6-28db04c10000}
02/09/10 10:27:23 TRACE: DOSDEVICE: Root#MS_PPTPMINIPORT#0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}
02/09/10 10:27:23 TRACE: DOSDEVICE: PTILINK1
02/09/10 10:27:23 TRACE: DOSDEVICE: NDISTAPI
02/09/10 10:27:23 TRACE: DOSDEVICE: NdisWan
02/09/10 10:27:23 TRACE: DOSDEVICE: Scsi1:
02/09/10 10:27:23 TRACE: DOSDEVICE: SCSI2MediumChanger
02/09/10 10:27:23 TRACE: DOSDEVICE: IPMULTICAST
02/09/10 10:27:23 TRACE: DOSDEVICE: PTILINK2
02/09/10 10:27:23 TRACE: DOSDEVICE: DmLoader
02/09/10 10:27:23 TRACE: DOSDEVICE: Shadow
02/09/10 10:27:23 TRACE: DOSDEVICE: {4FCCE3CA-647B-4BCF-9018-32DA64E4E603}
02/09/10 10:27:23 TRACE: DOSDEVICE: ACPI#AuthenticAMD_-_x86_Family_15_Model_37#_1#{97fadb10-4e33-40ae-359c-8bef029dbdd0}
02/09/10 10:27:23 TRACE: DOSDEVICE: PTILINK3
02/09/10 10:27:23 TRACE: DOSDEVICE: NPF_NdisWanIp
02/09/10 10:27:23 TRACE: DOSDEVICE: Pscan
02/09/10 10:27:23 TRACE: DOSDEVICE: FltMgr
02/09/10 10:27:23 TRACE: DOSDEVICE: FtControl
02/09/10 10:27:23 TRACE: DOSDEVICE: C:
02/09/10 10:27:23 TRACE: DOSDEVICE: Volume{8b6a855c-bfe4-11de-87c1-806e6f6e6963}
02/09/10 10:27:23 TRACE: DOSDEVICE: MAILSLOT
02/09/10 10:27:23 TRACE: DOSDEVICE: HID#Vid_046b&Pid_ff10&MI_00#8&7d5de48&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
02/09/10 10:27:23 TRACE: DOSDEVICE: AUX
02/09/10 10:27:23 TRACE: DOSDEVICE: Ndisuio
02/09/10 10:27:23 TRACE: DOSDEVICE: HID#Vid_046b&Pid_ff10&MI_01#8&1b05fa86&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
02/09/10 10:27:23 TRACE: DOSDEVICE: Root#RDP_MOU#0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
02/09/10 10:27:23 TRACE: DOSDEVICE: NUL
02/09/10 10:27:23 TRACE: DOSDEVICE: GLOBALROOT
02/09/10 10:27:23 TRACE: DOSDEVICE: Root#RDP_KBD#0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
02/09/10 10:27:23 TRACE: DOSDEVICE: PCI#VEN_1022&DEV_7464&SUBSYS_74641022&REV_0B#4&310b4f6b&0&0030#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
02/09/10 10:27:23 TRACE: DOSDEVICE: PCI#VEN_8086&DEV_1010&SUBSYS_10118086&REV_03#4&394cac81&0&1108#{ad498944-762f-11d0-8dcb-00c04fc3358c}
02/09/10 10:27:23 TRACE: DOSDEVICE: DmInfo
02/09/10 10:27:23     ===> PASSED
02/09/10 10:27:23 Traverse Volume Info
02/09/10 10:27:23 TRACE: Volume: \\?\Volume{8b6a855c-bfe4-11de-87c1-806e6f6e6963}\
02/09/10 10:27:23 TRACE: Device: \Device\HarddiskVolume1
02/09/10 10:27:23 TRACE: No mount points detected
02/09/10 10:27:23     ===> PASSED
02/09/10 10:27:23 Memory Mapped Files
02/09/10 10:27:23 TRACE: Initialize memory map
02/09/10 10:27:23 TRACE: Verify memory map
02/09/10 10:27:24     ===> PASSED
02/09/10 10:27:24 Reparse Points
02/09/10 10:27:24     ===> WARNING - Reparse points not supported on appliance: (0x32) The request is not supported.

02/09/10 10:27:24 Sparse Files
02/09/10 10:27:24     ===> WARNING - Sparse files not supported on appliance: (0x32) The request is not supported.

02/09/10 10:27:24 B2D Pre-allocation
02/09/10 10:27:24 TRACE: Positioning file pointer
02/09/10 10:27:24 TRACE: Writing a single buffer to extend file
02/09/10 10:27:24 TRACE: Setting end of file
02/09/10 10:27:24     ===> PASSED
02/09/10 10:27:24 Random IO
02/09/10 10:27:24 TRACE: Seeking to offset 0
02/09/10 10:27:24 TRACE: Writing 67108864 bytes to file
02/09/10 10:27:34 TRACE: Seeking to offset 0
02/09/10 10:27:34 TRACE: Reading 67108864 bytes from file
02/09/10 10:27:34 TRACE: Testing end of file
02/09/10 10:27:34 TRACE: Seeking to offset 1048576
02/09/10 10:27:34 TRACE: Reading 1048576 bytes from file
02/09/10 10:27:34 TRACE: Writing 1048576 bytes to file
02/09/10 10:27:34 TRACE: Seeking to offset 67108864
02/09/10 10:27:34 TRACE: Writing 655360 bytes to file
02/09/10 10:27:34 TRACE: Seeking to offset 67108864
02/09/10 10:27:34 TRACE: Reading 655360 bytes from file
02/09/10 10:27:34 TRACE: Testing end of file
02/09/10 10:27:34 TRACE: Seeking to offset 1048576
02/09/10 10:27:34 TRACE: Setting end of file
02/09/10 10:27:35 TRACE: Testing end of file
02/09/10 10:27:35 TRACE: Seeking to offset 0
02/09/10 10:27:35 TRACE: Reading 1048576 bytes from file
02/09/10 10:27:35 TRACE: Writing 1048576 bytes to file
02/09/10 10:27:35 TRACE: Testing end of file
02/09/10 10:27:35 TRACE: Seeking to offset 0
02/09/10 10:27:35 TRACE: Reading 2097152 bytes from file
02/09/10 10:27:35 TRACE: Testing end of file
02/09/10 10:27:35 TRACE: Seeking to offset 0
02/09/10 10:27:35 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping 131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping 131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping 131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping 131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping 131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping 131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping 131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping 131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping 131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping 131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping 131072 bytes
02/09/10 10:27:36 TRACE: Seeking to offset 2031616
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping -131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping -131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping -131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping -131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping -131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping -131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping -131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping -131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping -131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping -131072 bytes
02/09/10 10:27:36 TRACE: Reading 65536 bytes from file
02/09/10 10:27:36 TRACE: Skipping -131072 bytes
02/09/10 10:27:37     ===> PASSED
02/09/10 10:27:37 Default B2D Configuration
02/09/10 10:27:37 TRACE: Writing to file
02/09/10 10:34:14 TRACE: Reading from file
02/09/10 10:39:42     ===> PASSED
02/09/10 10:39:42 Read buffer B2D Configuration
02/09/10 10:39:44 TRACE: Writing to file
02/09/10 10:46:13 TRACE: Reading from file
02/09/10 10:51:39     ===> PASSED
02/09/10 10:51:39 No write buffering B2D Configuration
02/09/10 10:51:40 TRACE: Writing to file
02/09/10 10:58:11 TRACE: Reading from file
02/09/10 11:03:30     ===> PASSED
02/09/10 11:03:30 File Handles
02/09/10 11:19:24     ===> WARNING - Unable to create test file: (0x4) The system cannot open the file.

02/09/10 11:19:24 Cleanup Directory
02/09/10 11:19:25 TRACE: Skipping entry .
02/09/10 11:19:25 TRACE: Skipping entry ..
02/09/10 11:20:58     ===> PASSED
02/09/10 11:20:58
02/09/10 11:20:58 Total Tests Run: 15
02/09/10 11:20:58 Passed: 12
02/09/10 11:20:58 Failed: 0
02/09/10 11:20:58 Warned: 3
02/09/10 11:20:58
02/09/10 11:20:58 TRACE:
02/09/10 11:20:58 TRACE: Functions called:
02/09/10 11:20:58 TRACE: -----------------
02/09/10 11:20:58 TRACE: CloseHandle                      10005
02/09/10 11:20:58 TRACE: CreateDirectory                  1
02/09/10 11:20:58 TRACE: CreateFile                       10004
02/09/10 11:20:58 TRACE: CreateFileMapping                1
02/09/10 11:20:58 TRACE: DeleteFile                       9996
02/09/10 11:20:58 TRACE: FindFirstFile                    1
02/09/10 11:20:58 TRACE: FindFirstVolume                  1
02/09/10 11:20:58 TRACE: FindFirstVolumeMountPoint        1
02/09/10 11:20:58 TRACE: FindNextFile                     9998
02/09/10 11:20:58 TRACE: FindNextVolume                   1
02/09/10 11:20:58 TRACE: FindVolumeClose                  1
02/09/10 11:20:58 TRACE: FlushFileBuffers                 4
02/09/10 11:20:58 TRACE: GetDiskFreeSpaceEx               1
02/09/10 11:20:58 TRACE: GetFileAttributes                1
02/09/10 11:20:58 TRACE: GetFileSizeEx                    1
02/09/10 11:20:58 TRACE: GetVolumeInformation             3
02/09/10 11:20:58 TRACE: GetVolumePathName                3
02/09/10 11:20:58 TRACE: ImpersonateLoggedOnUser          1
02/09/10 11:20:58 TRACE: LogonUser                        1
02/09/10 11:20:58 TRACE: MapViewOfFile                    1
02/09/10 11:20:59 TRACE: QueryDosDevice                   2
02/09/10 11:20:59 TRACE: ReadFile                         197781
02/09/10 11:20:59 TRACE: RemoveDirectory                  1
02/09/10 11:20:59 TRACE: SetEndOfFile                     2
02/09/10 11:20:59 TRACE: SetFilePointer                   33
02/09/10 11:20:59 TRACE: UnmapViewOfFile                  1
02/09/10 11:20:59 TRACE: WriteFile                        197723
02/09/10 11:20:59 TRACE:
02/09/10 11:20:59
02/09/10 11:20:59 Final Analysis:
02/09/10 11:20:59 ---------------
02/09/10 11:20:59 Create Directory - PASSED
02/09/10 11:20:59 Disk Space - PASSED
02/09/10 11:20:59 Volume Information - PASSED
02/09/10 11:20:59 Query DOS Devices - PASSED
02/09/10 11:20:59 Traverse Volume Info - PASSED
02/09/10 11:20:59 Memory Mapped Files - PASSED
02/09/10 11:20:59 Reparse Points - WARNING - Reparse points not supported on appliance: (0x32) The request is not supported.

02/09/10 11:20:59     The appliance does not support reparse points.  Some
02/09/10 11:20:59     of the advanced B2D technologies such as GRT may not
02/09/10 11:20:59     function.
02/09/10 11:20:59
02/09/10 11:20:59     For GRT to function correctly, either the B2D path
02/09/10 11:20:59     or the temporary path for GRT operations must be an
02/09/10 11:20:59     NTFS partition that supports reparse points.  If this
02/09/10 11:20:59     is not the case, GRT operations will fail.
02/09/10 11:20:59
02/09/10 11:20:59     For more information on this topic please refer to
02/09/10 11:20:59     the Backup Exec Administrators Guide.
02/09/10 11:20:59 Sparse Files - WARNING - Sparse files not supported on appliance: (0x32) The request is not supported.

02/09/10 11:20:59     * Sparse file support is required for Backup Exec
02/09/10 11:20:59     * versions prior to 12.6 for GRT to function.
02/09/10 11:20:59     * If the Backup Exec installation is 12.6 or greater
02/09/10 11:20:59     * this test can be ignored.
02/09/10 11:20:59
02/09/10 11:20:59     The appliance does not support sparse files. Some
02/09/10 11:20:59     of the advanced B2D technologies such as GRT may
02/09/10 11:20:59     not function.
02/09/10 11:21:00
02/09/10 11:21:00     For GRT to function correctly, either the B2D
02/09/10 11:21:00     path or the temporary path for GRT operations
02/09/10 11:21:00     must be an NTFS partition that supports sparse
02/09/10 11:21:00     files.  If this is not the case, GRT operations
02/09/10 11:21:00     fail.
02/09/10 11:21:00
02/09/10 11:21:00     For more information on this topic please refer
02/09/10 11:21:00     to the Backup Exec Administrators Guide.
02/09/10 11:21:00 B2D Pre-allocation - PASSED
02/09/10 11:21:00 Random IO - PASSED
02/09/10 11:21:00 Default B2D Configuration - PASSED
02/09/10 11:21:00 Read buffer B2D Configuration - PASSED
02/09/10 11:21:00 No write buffering B2D Configuration - PASSED
02/09/10 11:21:00 File Handles - WARNING - Unable to create test file: (0x4) The system cannot open the file.

02/09/10 11:21:00     The appliance is unable to maintain a large quantity
02/09/10 11:21:00     of open file handles.  B2D technologies such as GRT
02/09/10 11:21:00     may not function correctly.  The test could only open
02/09/10 11:21:00     9,994 of 10,000 files.
02/09/10 11:21:00
02/09/10 11:21:00     Check the appliance configuration to see if there is
02/09/10 11:21:00     a way to increase the number of open files the
02/09/10 11:21:00     appliance can support.
02/09/10 11:21:00 Cleanup Directory - PASSED
02/09/10 11:21:00
02/09/10 11:21:00 One or more of the test have completed with warnings.
02/09/10 11:21:00 Backup Exec should be compatible with the appliance; however,
02/09/10 11:21:00 some features or functions may not be available.
02/09/10 11:21:00
02/09/10 11:21:00 The results of this test have been placed into the following
02/09/10 11:21:00 log file:
02/09/10 11:21:00
02/09/10 11:21:00   C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\B2DTest.log
02/09/10 11:21:00
02/09/10 11:21:00 Please include this log file in any communication with your
02/09/10 11:21:00 vendor or Symantec Technical Support.
02/09/10 11:21:00
02/09/10 11:21:00 If you have any additional questions please review the
02/09/10 11:21:00 knowledge base article for this tool online at the Symantec
02/09/10 11:21:00 product support site:
02/09/10 11:21:00 http://entsupport.symantec.com/umi/v-275-10000
==================================================================================================


0 Kudos

James_McKey
Level 5
Employee Certified

‎02-09-2010 11:14 AM

We only write one BKF file at a time (e.g. first is b2d000001.bkf) and we use that one file to stream all the backup data into until we hit the default limit of 4GB (http://seer.entsupport.symantec.com/docs/272517.htm). Are you seeing the byte count increase during the job? If not, what state is the job in? You might actually be having an issue unrelated to the destination for the B2D or are cancelling it before it gets beyond a certain preliminary phase.
0 Kudos

paul_klump
Level 3

‎02-09-2010 11:43 AM

James, I just started another backup job, which I will let run.  It's about 2:40 PM EST and I leave for the day around 5:30 PM EST, so I'll check the progress before I leave for the day.
0 Kudos

paul_klump
Level 3

‎02-09-2010 01:35 PM

James,

I started the job around 2:40 and stepped away, and hadn't noticed that a "backup-to-disk device is offline" message popped up right away.  I set the B2D folder back to online at 3:10 PM, and a few files were created on the disk:

02/09/2010  04:33 PM    <DIR>          .
02/09/2010  10:04 AM    <DIR>          ..
02/09/2010  03:11 PM             2,048 Folder.cfg
02/09/2010  03:12 PM             2,048 B2D000004.bkf
02/09/2010  03:11 PM               122 Changer.cfg
               3 File(s)          4,218 bytes

While this test backup was running, I've also been running the Wireshark newtork protocol analyzer to capture all traffic between the BE server and the ReadyNAS.  For the most part, I see no network traffic passing between the hosts, except for traffic in the following pattern:

--------------------------------------------------------
701    2010-02-09 15:16:59.539115    x.x.x.109    x.x.x.108    SMB    Echo Request
702    2010-02-09 15:16:59.539676    x.x.x.108    x.x.x.109    SMB    Echo Response
703    2010-02-09 15:16:59.820348    x.x.x.109    x.x.x.108    TCP    1350 > 445 [ACK] Seq=29175 Ack=31292 Win=64919 Len=0
-------------------------------------------------------

The x.x.x.109 host is the BE server, and the x.x.x.108 is the ReadyNAS.  This packet pattern seems to repeat every 34 seconds.

I've left the backup job running, and I plan on checking it in about 45 minutes.  I have saved the Wireshark packet capture, in the event that someone would need to look it over.
0 Kudos

paul_klump
Level 3

‎02-12-2010 05:09 AM

James,

So I've been out of the office for the past two days due to inclement weather here in the Northeast, so I let the backup job run over this time.  I checked this morning, the job is still labeled as active.  I also checked the files in the B2D folder location; the same 3 files I mentioned in my last update are present, and their timestamps haven't changed.

Paul
0 Kudos

paul_klump
Level 3

‎02-18-2010 05:09 AM

James,

I had been out of the office most of the week, but I had let that backup job just sit there and run.  It looked like it just went into a paused state. I then went to the drive share and saw that there were no change to the timestamps to the files I listed above.

I did see an alert that were 7 updates available to BE, so I'm running LiveUpdate as I type this.  I'll try to run another backup job later today, but if you have any insight on the info from my most recent postings, it'd be appreciated.

Paul
0 Kudos

paul_klump
Level 3

‎03-11-2010 01:13 PM

James,

I haven't replied back in a while, but I would like to report that I've successfully been able to back up my Windows servers via BE, and was able to perform a system restore of a test server using an IDR boot CD.

I'm not sure if the errors I was coming across were because I was using the local media server as my initial backup test source, and I didn't install the RAWS client on the media server.  I had run LiveUpdate on the media server, and then decided to install the RAWS client on my test server to see if I would get a different result.  And, as I mentioned, I was able to backup and restore data without a problem.

Would you be able to clarify whether a RAWS client would need to be installed on the media server in order to back it up, or should I be able to back up the local disks on the media server without a license?  I'm going to make a disk image of our media server by some other means and save a RAWS license for a future production Windows system, but for my own knowledge, I'd like to know if that is the case. Thanks!

Paul
0 Kudos

Ken_Putnam
Level 6

‎03-11-2010 01:53 PM

Would you be able to clarify whether a RAWS client would need to be installed on the media server in order to back it up, or should I be able to back up the local disks on the media server without a license? 


Ever since v9.0, all data access on a covered machine is via the "remote" agent, even on the media server itself.  You are not charge separately for this agent, it is part of the media server code 
0 Kudos