Why backups can fail with a "V-79-57344-34110 - AOFO: Initialization failure" when the Advanced Open File Option (AOFO) is selected in the Backup Job Properties

Article:TECH71225  |  Created: 2010-01-08  |  Updated: 2013-05-03  |  Article URL http://www.symantec.com/docs/TECH71225
Article Type
Technical Solution

Product(s)

Issue



Why backups can fail with a "V-79-57344-34110 - AOFO: Initialization failure" when the Advanced Open File Option (AOFO) is selected in the Backup Job Properties


Error



UMI Code V-79-57344-34110 will be listed in a job log when AOFO fails to initialize for any reason.  This is a generic UMI Code for "AOFO: Initialization failure on" and does not always return the best Resolution Documentation for an AOFO Failure because of it.  The UMI Code listed towards the end of the job log under Job Completion Status will usually return the best Resolution TechNote Results after this link has been opened, per what shows in the screenshot below. (Figure 1)
 

 
Figure 1


Solution



In addition to locating an AOFO Troubleshooting Document from the final UMI Code Link, the information below may also help to resolve many AOFO Failures:

I. Each remote Windows 2000 and Windows 2003 Machine being backed up with AOFO selected in the Backup Job Properties should have this option installed on it, in addition to the Remote Agent for Windows Servers (RAWS).  The AOFO Option installs vsp.sys, a kernel level driver. This driver interacts directly with the operating system and requires a reboot after installation either on the media server or remote machine.  To confirm whether or not AOFO is installed on a machine, search for the file VSP.SYS in the <systemroot>\system32\drivers directory or check in System Information, Software Environment under Drivers. (Figure 2)
 

Figure 2
 
 
 
  • For Windows 2000, ensure that Backup Exec Remote Agent with AOFO is installed. If not, install Remote Agent with AOFO (reboot is required).
  • If issue persist, one can uninstall the remote agent and AOFO, reboot the server, reinstall and reboot once again.
  • VSS (Microsoft Volume Shadow Copy Service) based backups are supported only on Windows 2003, Windows 2008 and Windows Vista. For Windows XP and Windows 2000 VSP (Symantec Volume Snapshot Provider) should be used. If backup with AOFO using VSS is run on Windows 2000 servers, it may give following error:

V-79-57344-34110 - AOFO: Initialization failure on: "C:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). VSS snapshots are not supported on the version of the operating system running on the target computer.

 
Note:  Only VSS can be used when backing up Windows 2008 Servers, so please do not attempt to either push out or perform a silent installation (local command line install) of the AOFO Option on these machines.  AOFO and the Remote Agent should also be un-installed prior to upgrading a previous version of Windows to Windows 2008 and then only the Remote Agent be installed after the upgrade has been completed.
 

 
II. The default settings for AOFO are "Automatically select open file technology" and "Process logical volumes for backup one at a time". (Figure 3)
 

 
Figure 3
  
 

 
If a combination of Windows 2000 and Windows 2003 Servers are being backed up, it is usually best to leave the default setting of "Automatically select open file technology" selected to prevent AOFO Failures.  AOFO Backups of Windows 2000 Machines with Microsoft Volume Shadow Copy Service (VSS) selected will fail because VSS only exists on Windows 2003 and above.  AOFO Backup of Windows 2003 Machines with only Symantec Volume Snapshot Provider selected will fail if Shadow Copy Components or System State are selected because only VSS can be used to back these items up.  
 

 
If Veritas Storage Foundation for Windows (VSFW) is either selected or installed, VSFW must be installed on both the media server and any remote machines being backed up.  This also applies to Hardware Snapshot Providers that may be installed. (Figure 4)
 
Figure 4
 
 
 
Note:  The Advanced Disk-based Backup Option (ADBO) cannot be selected in the Backup Job Properties unless VSFW or a Hardware Snapshot Technology Provider are installed on both the media server and remote machine being backed up. (Figure 5).
 
Figure 5
 
 
 

 
The "Process logical volumes for backup one at a time" Feature only allows one snapshot of each volume to be performed at a time and this can potentially help prevent failures on systems that have limited hardware resources available (i.e.: processor, physical memory, etc...).
 

 
Note:  By default, the AOFO Cache File is placed on the volume with the most free space not being snapped by the AOFO option backup.  If the volume being snapped is the only volume with available space, then the cache file is placed there.
 

 
III. Make sure the disk resources being backed up are not heavily fragmented and defragment the hard disks on a regular basis at a time when a backup job is not running.    http://www.symantec.com/docs/TECH11562
 

 
IV.  Confirm each machine being backed up with AOFO has enough physical Random Access Memory (RAM) installed/available, the RAM is not mismatched, and is what the hardware manufacturer recommends/supports.
 

 
V. Make sure the anti-virus software is not configured to scan the AOFO Cache Folder at the same time a backup runs.
 

 
VI. Confirm in Control Panel, Add/Remove Programs that no other application is installed that also uses an open file technology and can conflict with AOFO (i.e.: St. Bernards Open Transaction Manager, ArcServe, etc...).
 

 
VII. To potentially resolve VSP Failures that still occur after performing the steps listed above, modify the default settings in the AOFO Wizard for the machine the failure occurred with.    http://www.symantec.com/docs/TECH24762 
 

 
VIII. If Volume Shadow Copy (VSS) Initialization Errors occur on Windows 2003, Exchange 2003, or Exchange 2007 Servers during a backup, first confirm all the latest patches have been applied for Backup Exec via either LiveUpdate or manually (re-install the Remote Agent afterward if the machine is remote).  If a backup still fails with a VSS Error:
 
V-79-57344-34110 - AOFO: Initialization failure on: "\\Server\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).  VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot provider selected returned: "Unexpected provider error". Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details. 
Microsoft's Volume Shadow Copy Service (VSS) has encountered an error. It is common to see Event ID 12293 in the Windows Event Viewer.
afterward, run the VSS List Writer Command to check the writer status and then apply/re-apply the latest Windows or Exchange Service Pack if necessary.  You may need to apply Windows 2008 server VSS update (KB940349) A support case may also need to be opened with Microsoft if issue with VSS still persist after applying the updates.  For detailed information, kindly refer:  http://www.symantec.com/docs/TECH42921
 

 
IX. Do not backup files such as Backup to Disk Files (.BKF) or SQL Dump Files (.BAK) in the same backup job where AOFO has been selected.  It is not necessary to back these files up with AOFO and in some rare cases, AOFO can fail to initialize because of the files being selected in the Backup Job Properties.
 
X. V-79-57344-34110 - AOFO: Initialization failure, also gives other error:
Final error: 0x8004230c - 0x8004230c (2147754764)
V-79-57344-34110 - AOFO: Initialization failure error. Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot provider that you selected cannot snap this volume. Select the default snapshot provider, and then run the job again.
 
  • This issue occurs if "Microsoft Software Shadow Copy Provider service" and/or " Volume shadow copy service" are disabled on the target server.
  • This issue also occurs if the Windows root partition (c:\) is running out of free space, or lacks space to hold the Snapshot data.
  • This issue might also occur if the Advanced Open File Option was not pushed to the remote machine.

To resolve this issue:

  • Make sure that the "Microsoft Software shadow copy provider service" and " Volume shadow copy service" on the target server is Enabled and set to Manual but the service Status should be Stopped. These services will start automatically whenever a snapshot backup job is triggered and will be stopped after the backup job completes successfully.
  • Make sure the windows root partition has enough space to hold the Snapshot data.
  • Make sure that the AOFO Option was pushed to the remote machine (Tools --> Install Agents and Media Servers on Other Servers..., Browse to Remote computer --> Make sure that the Advanced Open File Option is checked.) (Steps for BE 2010 and earlier).
It is also seen that, some time along with error  V-79-57344-34110, it can also give following error/exception:
V-79-10000-11223 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot provider that you selected cannot snap this volume. Select the default snapshot provider, and then run the job again.
The backup job completes with exceptions due to inability of Volume Shadow Copy Service (VSS) to snap the volume. When attempting to click the "Shadow Copies" tab in the properties of the volume mentioned in the Job Log , an error is received  "Volume <Drive> is not eligible for shadow copies". See figure 1.
Figure 1
To resolve such issues, right click the Drive > PropertiesSecurity, click Add, and add the System account and grant Full Control rights. See Figure 2.
Figure 2.
 
 
For additional information on AOFO, please see the TechNote listed in the Related Documents Section below.
 
This document is available in the following languages:
 
French:
 
German:
 
Italian:
 

 

 


Supplemental Materials

SourceUMI
ValueV-79-57344-34110
Description

AOFO Initialization Failure


SourceError Code
Value0x8007000E
Description

Snapshot provider error: Ran out of memory



Legacy ID



326302


Article URL http://www.symantec.com/docs/TECH71225


Terms of use for this information are found in Legal Notices