AOFO used

[rosarian]

Im trying to run BE9.1 on W2KServer backing up multiple volumes. It used to work just fine but now I am getting the following error message:

OFO: Initialization failure on: "I:". Advanced Open File Option used: Veritas Volume Snapshot Provider (VSP).
OFO: Volume specified is not snappable. Possible reasons: Not a fixed drive, or contains an active cache file or does not have a valid source or is write protected.

Now I have done some reaserch on this and have already performed the following to try and resolve:

1. Setup same Job under different name
2. Logged onto network with different user
3. Setup a different BE logon
4. Excluded .tmp & .vsp files from realtime virus scan
5. Disabled outgoing RealTime Monitor virus scan while BE ran
6. Disabled all virus protection while BE ran
7. Changed where cache file is stored to a drive not being backed up
8. Changed the cache file minimum & maximum sizes

All the above have failed to resolve the issue. I have set the AOFO to snap one volume at a time the next time BE runs. If this doesn't work then the last option I have been able to find is to set the Quite time lower.

If anyone has any other ideas on how to resolve this error it would be most appreciated.

 

[steveot]

Check the server for .vsp file. If the job did not backup properly then then it left the .vsp files. You have to reboot and delete them.

 

[rosarian]

I have checked the local drive of the server running BE, the drive where im pointing the cache files to go to and all the drives that are suppose to be backed up and there are no .vsp files to be found

 

[rosarian]

Also, how much space do the cache files require?

 

[steveot]

The I: drive is it local to backup exce or is it on another server? Are you trying to backup a remote server or the local server?

 

[rosarian]

The I: drive is a remote server. The rest of the remote servers backup just fine and thats what I don't understand about the I: drive

 

[TigerDivision]

This goes to show that the AOFO is still flaky. I've given up on using it in fact I've switched it off!

 

[rosarian]

I am backing up multiple remote servers and the local drive

 

[Empmark]

We have just started having the same issue after many weeks of good backups. I have just excluded the vsp and tmp files from our scans per the Veritas recommendation but I am disappointed to hear that may not work.

What intersts me is that the only server we are having an issue on is a Win2k. I haven't seen it on any 2003 Servers. I noticed your issue was also on a Win2k Server. Just curious if this issue is only affecting 2000 Server and if so maybe this will help in the troubleshooting. Wish I could be more help but I will update on any solutions I find.

 

[rosarian]

After setting the AOFO to snap one volume at a time and BE ran last nite it still gave me the same error but also added drive J with the same error. I double checked these drives and they are local drives to the W2K server. When I try to open the Sys folder on these drives it tells me access denied, but Im logged on as Admin. So im going to try rebooting the server and see if that will allow me access to the Sys folder and take care of the problem.

 

[TigerDivision]

This also happens on Windows NT Server boxes. I've had same issues when trying to back up remote servers running NT and W2K.

 

[rosarian]

This goes out to everyone that has been having the same problem as I. We noticed yesterday that when we tried to open the system info folder on the drive that was reporting the AOFO error that we would get Access Denied. We rebooted the server and the Job completed successfully with no exceptions.

So if you are getting the error message listed at the beginning of this post and are unable to access the System Volume Information folder on the drive thats giving the error all you need to do is reboot the server.

 

[rosarian]

Thanks everyone for you help in resolving this issue...