• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 830
  • Last Modified:

Backup Exec question: Why can't I move the AOFO cache?

I'm running Backup Exec 9.1 on a Windows 2000/Exchange 2000 server.  The C: drive has only 600 MB's free space, and when I try to run a backup job with OFO enabled, it creates a cache that uses all of that space and crashes the server.  I used the AOFO Wizard to create locations on two other drives, unchecking the "default location" option.  Nonetheless, every time I try to run a job it creates the cache on C: and down goes the server again.

Has anyone seen this problem before, and is there anything I can do short of denying Write permissions to the C: drive for my backup account?
0
tomghormley
Asked:
tomghormley
  • 6
  • 4
  • 2
  • +2
1 Solution
 
Pete LongConsultantCommented:
you need to run a wizard to do this hang on................
0
 
Pete LongConsultantCommented:
0
 
tomghormleyAuthor Commented:
Thanks for your response.  As I mentioned above, I did run the AOFO Wizard.  Is there another wizard with which I'm not familiar?

Thanks again.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
maduropaCommented:
Is it possible that the AOFO files are still in use, and because of that they cannot be moved?

Maybe not in use with Backup Exec but another program like a virus-scanner?
exclude the path in the scanner, also exclude the new destination, and try again
0
 
tomghormleyAuthor Commented:
I will add the new locations to the Exclusion list and try again tonight.  Thanks for your response.
0
 
David_FongCommented:
600MB used by the AOFO cache? Sounds like you're trying to use AOFO to backup Exchange rather than using the Exchange agent. Should never be 600MB of open files on a server that need to be backed up. Well on a really big enterprise fileserver maybe but that woldn't have Exchange installed on it. Backup Exec is meant to have the sense to deselect the raw data files if the Exchange agent is working correctly but sometimes it can get confused.
0
 
tomghormleyAuthor Commented:
You make a good point.  I hadn't thought about it in those terms, but there's no way that many files would be open.  In fact, I've encountered this immediately after a reboot, when few if ANY files would be open.  So it is using OFO to backup exchange.

The problem is, I HAVE the Exchange agent installed.  Why isn't it using that?  You mention it becoming "confused."  Do you know of a way I can un-confuse it?
0
 
David_FongCommented:
Manually deselect the Exchange data files from the file based backup, http://support.veritas.com/docs/207980. (the link at the bottom also applies but I doubt anyone has deliberately turned the functionality off).
0
 
scrathcyboyCommented:
sorry, disagree, 600 MB is nothing these days, the windows swap file can exceed that on a server.
Two important principles here -
1. if that is all the free space you have, you should be changing up to bigger hard drive before anything else
2.  If backup exec 9 cant default its temporary cache directory to another drive, then it is a pretty poor product isnt it?  This is mindless programming.  If it were me, Id be looking for a better backup program.
0
 
David_FongCommented:
pagefile.sys has been automatically excluded since ver 7.2.
0
 
tomghormleyAuthor Commented:
Thanks for all the responses.  Excluding the MBDATA and other files did not help, as the 600MB+ cache file was still there and the server did crash.  I ended up having to drive back to the office at 10:30 to bounce the server (my company has not yet learned to appreciate DRAC/iLO cards).

scrathcyboy:

While I appreciate your taking the time to offer your opinion, answers like these always make me wonder why people bother to click that "Submit" button.  I posed a question about an immediate need with a specific problem.  I just inherited this network, and recognize that there are disk space issues.  As for Backup Exec, I've used it for over five years (various versions).  It has its bugs like any program, but it has otherwise been a reliable solution.  Your response reminded me of the Linux gearheads who, anytime someone asks how to do/fix something in Windows reply "Your first step is to get rid of 'Windoze' and move your entire company over to Linux."

I won't tell you how to live your life, but FWIW, I try to give specific answers related to people's problems.  If a fat guy gets shot and is bleeding out, I doubt he is interested in the paramedic's thoughts on cholesterol and a healthy diet at that time.  Saying things like "I'd be looking for a better backup program" contributes nothing to the dialogue and helps no one.  If I had posted a question asking for opinions on the worthiness or practicality of BE or advice on disk space your comment would have been helpful and relevant.  In this case they were not.

Sorry for the rant, but this issue is driving me crazy and I get disappointed when I see "New Comment" on my question and the comments are only philosophical in nature.
0
 
maduropaCommented:
What permissions are granted to the backup-account.

I've had troubles once with a backup-account, it had all the backup-admin rights, but lacked the domain-admin rights. In fact, backups went perfect, but I couldn't look into session-info. After adding to the domain-admin group, everything worked perfect.
In light of what David said, about the 600 MB's of open files, maybe the backupuser hasn't sufficient rights for some files and thus sees it as open files?
So check rights, and add him to the domain-admins,

I assume that the backup-user account has all needed rights for the other partitions to write?
0
 
tomghormleyAuthor Commented:
Maduropa-

Thanks for responding.  The backup account is a domain admin.
0
 
David_FongCommented:
If you disable the job from using AOFO at least you'll see what files are open and it won't crash the server. Then I would uninstall the AOFO agent with "setup.exe /RANT32: -s -u" (from the rant32 directory), reboot and push it out again. Als I generally force it to use veritas snapshot provider as I don't think MS VSS is stable enough yet.
0
 
tomghormleyAuthor Commented:
Thanks, David.  I will try that.  As for the snapshot provider, I'm stuck with Veritas anyway because it's a Windows 2000 box.  At my last job I replaced a 2000 network with all new 2003, so it has been frustrating to "downgrade" with this new job at times.  
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 6
  • 4
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now