Video Screencast Help

Failed Backups

Created: 29 Jan 2005 • Updated: 21 May 2010 | 2 comments

Backups have started failing on our mailserver over the last couple of days, with the following: OFO: Initialization failure on: "C:". 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.
Jobs have been running previously without any problems, AOFO option is installed and configured to automatically detect best option to use.

Also the following files have been listed as being skipped:
The item C:\compaq\vcagent\vcagent.log in use - skipped.
The item C:\Inetpub\nntpfile\article.hsh in use - skipped.
The item C:\Inetpub\nntpfile\group.lst in use - skipped.
The item C:\Inetpub\nntpfile\groupvar.lst in use - skipped.
The item C:\Inetpub\nntpfile\history.hsh in use - skipped.
The item C:\Inetpub\nntpfile\xover.hsh in use - skipped.
The item C:\Inetpub\nntpfile\root\_slavegroup\group.vpp in use - skipped.
The item C:\Inetpub\nntpfile\root\control\group.vpp in use - skipped.
The item C:\Program Files\Microsoft SQL Server\MSSQL$BKUPEXEC\LOG\ERRORLOG in use - skipped.
The item C:\Program Files\VERITAS\Backup Exec\NT\Data\BEX00047.xml in use - skipped.
The item C:\Program Files\VERITAS\Backup Exec\NT\Logs\adamm.log in use - skipped.
The item C:\WINNT\system32\Perflib_Perfdata_5b4.dat in use - skipped.
The item C:\WINNT\system32\Perflib_Perfdata_7b4.dat in use - skipped.
The item C:\WINNT\system32\Perflib_Perfdata_804.dat in use - skipped.
The item C:\WINNT\system32\Perflib_Perfdata_ab0.dat in use - skipped.
The item C:\WINNT\system32\dns\dns.log in use - skipped.
The item C:\WINNT\system32\LogFiles\W3SVC1\ex050128.log in use - skipped.
Along with log & dat files being skipped in the Exchsrvr\MTADATA\ folder due to being in use, again no problems previously.
Any advice would be greatly appreciated.

Comments 2 CommentsJump to latest comment

Abhinav Bindroo's picture

The error usually occurs if the .tmp files (snapshot) created by AOFO are not deleted as they are in use.

Refer to following technote

You may also reboot the suspected server and verify the results.

Further, the Exchange database and related data should be backed up using the Exchange Agent and not AOFO.


Hope this helps

Ameet Thakkar's picture

In addition, please refer the following.

Perfdata is used to access data about systemperformance, hence it is called PERFormance DATA. PerfLib is a performance counter library hence PERFormance LIBrary.This information is not required and hence will not create any issues during restore.

"Backup Exec 9.x for Windows Servers" requires Exchange Agent to perform an online backup of Exchange Databases. The items get skipped if selected as a flat-file (i.e. through /program files/exchsrvr/mdbdata) and results into exceptional errors.
To crosscheck, explicitly select the exchange data folder for backup and ensure that Exchange System Attendant and Information Store services are running.

Additional Information:

Backup Exec Agent for Microsoft Exchange Server provides a fast and flexible way of protecting your online Exchange 5.x and Exchange 2000 Server data. This agent provides complete individual mailbox backup, including protection for embedded messages, objects, attributes and all Outlook components. For more information, see " Backup Exec for Windows NT and Windows 2000 - Agent for Microsoft Exchange Server" on page 1067 of the Admin guide. You can download it from the following URL:

Note: When backing up Exchange database, there is no need to have AOFO. The online Exchange database backup is taken care by the Exchange Agent.If you have the Exchange Agent, then we suggest you unselect the \exchsrvr directory from the normal file level backup.With this directory selected for backup, the Backup Exec software will attempt to perform a "flat file" backup of the Exchange database. As the database is running and the files are open, Backup Exec will report, in the job history log, that the Exchange files have been skipped:
When backing up these files make sure they are only backed up via the Exchange Agent. DO NOT select any of these files from anywhere else in Backup Exec apart from the Exchange Agent. If selections are made from anywhere else uncheck them. The selections for backup should only be made from the Exchange Agent.

As an additional information, kindly refer the following technote as well
Title:- During the backup of an Exchange server, the Microsoft Exchange database files are skipped.


As an additional information, refer the forllowing Microsoft Q article.;...

We hope this helps. Let us if the steps mentioned above has helped you solve the problem.