Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Backup Exec Removable Drive

Created: 20 Jan 2014 | 6 comments
Baron164's picture

I am running Backup Exec 2010 R3 and I'm using USB drives. I have a Removable Backup-to-disk Folder setup for the USB drives. However when the backup user changes swap drives occasionally the device will go offline. I need it to stop going offline, is there some way of forcing it to automaticaly go back online?

Operating Systems:

Comments 6 CommentsJump to latest comment

VJware's picture

Its expected behavior for the drive to go offline when it is getting swapped. One automated way would be to run a scheduled task to restart all BE services before the backup starts.

EDIT*

Have a look @ the last section of this post by a TA - https://www-secure.symantec.com/connect/articles/h...

Baron164's picture

It's strange then that it doesn't do it all the time, just occassionally. I will setup a scheduled inventory task and see if that works.

Colin Weaver's picture

USB disks (assuming they show up in Windows Explorer as fixed disks and are not defined as removable by the operating system) should be configured as a standard B2D. The removable B2D option is specifically for disks that report to the operating system as removable (which usually means cartridge based media such as RDX technology or some USB flash/pen drives)

 

USB disk if configured as Standard B2D, should go offline when removed but then report as online again a short time after they are re-inserted

Baron164's picture

Ok I'll try that, still curious why it doesn't happen all the time. The reason I didn't do standard backup to disk folders originally is because the drives change and I was told a long time ago on this forum actually, to use removable folders for usb drives that are swapped.

Baron164's picture

After changing the device to a standard backup to disk folder it still goes offline occassionally after changing the drive. I am seeing "Event ID 56 - Driver USBSTOR returned invalid ID for a child device (00000000011E0A49&0)." which could causing this but I'm not sure what this error is.

pkh's picture

Check that your disks do not have the same diskids.  If they do, change them to unique ones using the procedure in my blog below.

https://www-secure.symantec.com/connect/blogs/chan...