How can I reinstall AOFO without having to uninstall/reinsall BackupExec from scratch or is there another fix for this problem?
We have setup several backup jobs on a Windows Server 2003 R2 Standard x64 edition. All jobs are completing fine, apart from the job on the host server that runs BackupExec with the following error:
V-79-57344-34110 - AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Based on the Symantec KB I checked the advanced options of BackupExec and I am not able to setup AOFO as it states it is not correctly installed. From a second server within the network that runs BackupExec I know the way it should work.
I have followed a workaround from the Symantec KB to manually reinstall the AOFO driver(s), but to no avail. I really don't want to go down the route of having to reinstall BackupExec from scratch as I would have to setup all the backup jobs again.
Is there away to reinitialize AOFO or reinstall it? The 11d version in use now is an upgrade from v10.
V-79-57344-34110 - AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Based on the Symantec KB I checked the advanced options of BackupExec and I am not able to setup AOFO as it states it is not correctly installed. From a second server within the network that runs BackupExec I know the way it should work.
I have followed a workaround from the Symantec KB to manually reinstall the AOFO driver(s), but to no avail. I really don't want to go down the route of having to reinstall BackupExec from scratch as I would have to setup all the backup jobs again.
Is there away to reinitialize AOFO or reinstall it? The 11d version in use now is an upgrade from v10.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the reply.
The "MS Software Shadow Copy Provider" was set to manual. I have now set it to automatic just in case. The output for the list providers command is as follows:
Provider name: 'Symantec Software VSS Provider'
Provider type: Software
Provider Id: {262b716e-bb23-41b5-aaef-e
Version: 1.0
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-5
Version: 1.0.0.7
I will also have a look at the workaround. The other servers on the network do have a Symantec Software VSS Provider service, but the one with the problem does not. Not sure whether it was removed or whether it has never been there.
The "MS Software Shadow Copy Provider" was set to manual. I have now set it to automatic just in case. The output for the list providers command is as follows:
Provider name: 'Symantec Software VSS Provider'
Provider type: Software
Provider Id: {262b716e-bb23-41b5-aaef-e
Version: 1.0
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-5
Version: 1.0.0.7
I will also have a look at the workaround. The other servers on the network do have a Symantec Software VSS Provider service, but the one with the problem does not. Not sure whether it was removed or whether it has never been there.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
There are no AOFO licenses, so that would explain that part and you are right, the error relates to VSS. I have installed the rollup package via the MSKB link you kindly provided and the server was rebooted over the course of the week-end. I checked again today and still the following error:
_______
V-79-57344-34110 - AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Microsoft Volume Shadow Copy Services (VSS) snapshot provider returned the error: "Catastrophic failure". To make sure that the VSS is not disabled and can be started, click Control Panel, and then click Administrative Tools. Open the Services, and start Volume Shadow Copy. Check the Windows Event Viewer for details.
_______
I have checked the eventlog and there is nothing conclusive and the "Volume Shadow Copy" service is set to Automatic and was started. The MSKB articles refer only (obviously) to issues relating to their own NTbackup and the MSVSS. However, I had a look ad the vss providers on t he server in question and found this:
_______
Provider name: 'Symantec Software VSS Provider'
Provider type: Software
Provider Id: {262b716e-bb23-41b5-aaef-e
Version: 1.0
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-5
Version: 1.0.0.7
_______
Although the error states MSVSS, it would seem that the Symantec VS service is not available or installed, but BackupExec could be looking for it. I have already tried a repair installation to no avail and haven't found anything in the Symantec KB that covers a manual reinstallation. Is there a way I can re-register or reinstall the Symantec VS serivce or make BE use the MS VSS?