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
Details:
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
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
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://support.veritas.com/docs/237444
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://support.veritas.com/docs/256762
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 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. A support case may also need to be
opened with
Microsoft.
http://support.veritas.com/docs/278212
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.
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:
Products Applied:
Backup Exec 10.0, 10.0 5484, 10.0 5520, 10d (10.1), 10d (10.1) 5629, 11d (11.0), 11d (11.0) 6235, 11d (11.0) 7170, 12.0, 12.5, 9.1, 9.1 4691
Subjects:
Backup Exec
Application: Backup, How To, Open File Option, Troubleshooting
Languages:
English (US)
Operating Systems:
Windows 2000Advanced Server, Server
Windows Server 2003
Enterprise Server, Standard Server
Windows Small Business Server 2003
Premium Edition, Standard Edition