Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

BackupExec 2010 R2 - backup on HP C5683 does not end

Created: 10 Feb 2011 • Updated: 10 Feb 2011 | 5 comments
This issue has been solved. See solution.

With the old Veritas Backup Exec 9 all was working well.
We now switched to BackupExec 2010 R2 (also installed the symantec drivers for the HP C5683 tape drive).

Simple backup job, just one folder for testing.
backup runs, and judged by the amount of data backuped, all data went to the tape drive.
without verify backup option enabled: backup never ends - status stays on "backup"
with verify backup option enabled: verify never ends - status stays on "verify"

i did debug the backupsession. once all data is on the drive / verfiy "ends", the is a timout from the storagedevice, and the BESERVER continues to log "Service_Running" forever.
when i try to "abort" that backup, then this does not work either. after 1 hour it still tries to abort.
i have to restart the backupserver and jobs services to get it aborted.

i also tried to switch back to the MS drivers for the HP C5683 -> same problem.

backup2disc in 2010 R2 works flawlessly

i did uninstall Backup exec 2010R and clean installed version 9 - all working well there.

i am lost. anyone an idea why the jobs never end with the HP C5683 ?

Comments 5 CommentsJump to latest comment

Kiran Bandi's picture

Clear Eject media after completing backup option under device and media options of the backup job. It may solve your problem..

EDIT: You can also configure auto respond to media eject alert in BE.

Regards..

solidservo's picture

Now backupjobs do finish again. Yet I need to have the media ejected automatically.

Is this nolonger possible?

*edit* tried to eject the media wth the option inside backupexec -> devices
same problem. that task will run forever and not eject the media from the tapedrive. :(

Kiran Bandi's picture

You have to respond to the media eject alert... Check in your alerts tab. Media eject alert may be waiting for your response. And the better choice is to configure auto response to the media eject alert as i said in my earlier post. For configuring auto response to alerts see the following article...

http://www.symantec.com/docs/HOWTO22882

Regards..

SOLUTION