can't delete AOFO folder 1

[shellac]

I have 2 files on my server in C:\Backup Exec AOFO Store. I have to delete due to disk space and it tells me I can't. I've tried stopping the remote agent service and the VSP service and it still won't let me delete it.

Any help is appreciated.

Thanks

 

[dali99]

Rebooting the server will clear these files.

 

[masm]

I have the same problem on the majority of our servers. The OFO cache file is not deleted at the end of the backup and it becomes locked. This means the following backup OFO fails because the previous OFO cache file is still there. The only way to remove is to reboot which is not a viable solution. Veritas have no idea (how odd).

Anyone else having similar problems? I've followed all the suggested Veritas fixes but no joy. I've been trying to find something that will unlock the file without rebooting the server but so far with little luck.

 

[stevet3]

Exclude the \Backup Exec AOFO Store folder from virus scanning. Exlude .tmp or .vsp files from virus scanning.

Enable Single Volume snap for Backup Exec 9.1 only

http://seer.support.veritas.com/docs/264464.htm

 

[masm]

Yup tried all these solutions with no luck. Veritas are out of ideas and I have had a case open for months with them. If I find anything new I'll post it as I have another Veritas technician calling me from the States tomorrow to try and fix this.

 

[mplsupport]

Here's a way to delete those files without rebooting..

Make sure that no backing is running,,

use procexp.exe from sysinternals.. search handles for vsp files.. the locked files will show up.. click on one and it will focus in the procexp.exe window.. then right click and click close handle.

 

[blackisle]

cheers mplsupport - I had the same problem, 20s with procexp.exe and all is well

 

[masm]

Thanks for this. I had tried this util from sysinternals before but found that it left the BE agent in an unstable state which could still only be solved with a reboot. Restarting the BE service didn't help. I did go through and close any handle that referenced vsp files or the OFO cache folder. Perhaps I was too over enthusiastic! I'll try again just deleting vsp handles.

 

[subzeroNL]

O YES, just what i was looking for, i have this problem but thx to you mplsupport!!!! i dont have to reboot the server THX man.....