cancel
Showing results for 
Search instead for 
Did you mean: 

RD1000 not ejected after backup - beremote.exe open handles

ICAP
Level 2

Hi,

I'm using Dell RD1000 removeable HDDs with BackupExec 2012 on Windows SBS 2011. With BE 2010R3 the HDDs were successfully ejected after the BE job, with 2012 they fail to eject. A seperate "eject job"does not eject them and even windows can't eject them ("drive in use").

I used process explorer to check for open handles and it shows me that beremote.exe has handles on pdi.txt, pdi_strm.bin and some ShareWebDb_log.ldf files. If I stop the beremote service, windows can successfully eject the HDD.

Is there any other solution for this problem except automatically restarting beremote after each job?

Thanks,

Daniel

 

 

9 REPLIES 9

Backup_Exec1
Level 6
Employee Accredited Certified

Hi

 

But in process explorer which process is having handle on this file, Also in this you see this when doing GRT backup of exchange or any backup going to RD1000

Also could you post the snap of process explorer end of the job showing handle

 

Thanks

ICAP
Level 2

See attached screenshot.

Backup_Exec1
Level 6
Employee Accredited Certified

Hi

 

There was an issue for exchange GRT backup in BE 2010 r3 to which got resolve please see the document

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

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

Now as in your case also at end there are handle for beremote so as a workaround for now you can now use batch script in post command which will restart remote agent service end of the job

You can open a case with symantec to investigate this further for BE 2012

 

Thanks

pkh
Moderator
Moderator
   VIP    Certified

Did you read the user's requirement?  He does not want to restart the remote agent service.

bc2012
Not applicable

I've got the exact same scenario. SBS2011 and BE2012 (adding SP1 had no effect), beremote.exe keeps file handles open on the ShareWebDB files even after job shows completed.  Latest RDXmon is installed and have run the EnableBestEffort.bat  The moment you stop beremote.exe you can eject the drive.

I assume a work around would be to run a post-job script that restarts the beremote.exe service and then ejects the drive?

You would think that after years and years of RDX eject issues, Symantec would test this issue in every product release.

adelphi
Level 3

I've opened a case at tech support regarding this issue.

They told me to:

- apply BE2012 SP1

if SP1 doesn't help:

- recreate the removeable disk storage in BE

- reinstall der windows drivers for RDX

 

I had no time to test it...

mschollbach
Level 1

i've got the same problem (no automatic eject of cartridge) on a system with sbs2011, backup exec 2010 r3 and a rdx device from tandberg.. beremote.exe is holding a handle on a file called 'ShareWebDb_log.ldf'. today i unchecked 'grt' for sharepoint.

 

when i use "enablebesteffort.bat" the user can eject the cartridgy manually! but automatically doesn't work.

 

---EDIT--------------------------------------------------------------------------------

By disabling "GRT" for Sharepoint Backup the job completes and isn't holding a handle on the media. This lets the system eject the cartridge automatically and you can eject the cartridge manually without using "Enablebesteffort.bat" from Tandberg!

It works!

Milind_P
Level 2
Employee Accredited Certified

Hello,

 

Please open up a case with Tech support ot work on this

 

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

 

Thanks,

Milind 

Milind_P
Level 2
Employee Accredited Certified

Please open up a case with Technical Support to work on this http://www.symantec.com/docs/TECH191155