Using a network hard drive with Backup Exec 11d

My client has a Windows 2003 Small Business Server running as a domain
controller with Backup Exec 11d installed.

I'm trying to configure Backup Exec to backup to a network-attached
hard drive. The device I'm using can be seen at the following address:

http://www.scan.co.uk/Products/ProductInfo.asp?WebProductID=604572 

I have configured this drive as a backup-to-disk device within BE and
configured a backup job to use it. However, when the job is run, the
status goes from Initializing to Queued and doesn't change. There are
no alerts or errors. If I view the device under the Devices tab while
the job is running it occassionally flashes up as in-use for a few
seconds.

I know this drive is visible as I can view it within windows explorer
using the UNC path \\<Device>\Public and it is writable. The backup
job is set to run as the domain administrator so it has write
permissions on the drive.

Any help with this will be greatly appreciated as I've tried
everything I can think of!!

Thanks.
LVL 1
_KeepItSimple_Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
bhanukir7Connect With a Mentor Commented:
Hi,

is this giving any licensing errors or any errors in the log. Can you please review the log and check if there are any licensing errors or any errors in the backupexec logs.
By default the for disk to disk backups the backup file size is 1 gb and it will create additional files as and when the backup size will increase beyond 1 GB.

Check if there are any device/maintenance updates available and update backup exec to the latest.

From what we see it appears to be communicating with the device correctly, but subseqently it is not writing any data. Check if he is able to run a backup by creating a disk to disk backup device on the server itself.

bhanu

0
 
ormerodrutterCommented:
Whe you plugged this USB hard disk to your server it should be assigned a drive letter (e.g. f:\). Can you check in your Backup-to-disk device you have specified this as the PATH?
0
 
_KeepItSimple_Author Commented:
Thanks for your response but you've misunderstood the setup. The hard disk is not connected to the server at all. The hard disk has an in-built ethernet connection and it is connected directly to the network. The hard disk can be accessed directly using a UNC path so it doen't have a drive letter but I can map a drive to it if required. I haven't done so because I thought that accessing a networked resource using the UNC path would be more reliable.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
_KeepItSimple_Author Commented:
Some additional info:

When a backup-to-disk folder is created on the drive in question the following files are created automatically:

Changer.cfg
Folder.cfg

When a backup job is run to the B2D device a new file appears called @@@@@@@@.bkf and is always exactly 1,048,576 kb in size.

I hope this helps.
0
 
bhanukir7Commented:
Hi,

Are you able to write data from windows to this network device. Try creating a folder and copy data from the disk and copy back from it. Are you able to copy data to it from windows. Check this first.
 
Try to selecting around 100 mb of data and run a test backup from backupexec using disk to disk.

Do you see any issue with the network connectivity.

If possible try connecting this disk using USB connector if they have provided the USB connectors and create a new folder under the drive and configure that as a new disk to disk backup and see if you are able to backup using backup exec when you are connecting it through usb. To isolate the network card errors on that disk.

bhanu

The changer.cfg and folder.cfg are backexec files which are created and they contain the configuration info.
0
 
_KeepItSimple_Author Commented:
Hello,

I can write data to the device over the network and have successfully copied and deleted data on it using the same SMB share path as I have given to backup exec so I don't think there is any fault with the network connectivity of the drive. I would have thought that the successful creation of the *.cfg files in the B2D folder confirms that BE can indeed see and write to the drive?

I have tried the small test run you have suggested with the same results. I have noticed that despite the backup job seemingly stuck the drive is getting very hot.

I'll try hooking up the drive directly to the server using USB when I'm next at the client site - that costs them money so I don't want to be there too often!

Thanks for the help so far.
0
 
_KeepItSimple_Author Commented:
Upped the points at this appears to be more difficult than I initially thought :)
0
 
_KeepItSimple_Author Commented:
I see no errors in the logs that would indicate a license problem. Unfortunately, the LiveUpdate program hasn't been installed so I can't check for BE updates. I'll be onsite in the next couple of days so I'm going to install LiveUpdate and check for updates, try a B2D on the server and try a B2D with the HDD connected directly through USB.

I'll report back as soon as I have the results.

Thanks.
D.
0
All Courses

From novice to tech pro — start learning today.