When using FlashBackup-Windows policies, attempts to restore a compressed Microsoft Outlook personal folder file (*.pst) will fail with status code 5 reported, although no error was reported when the file was backed up. (updated November 12, 2010)
tar_restore_vxms::writeData: fiml_write_file failed (uncompressed part) error = 3
updated 3/3/10: Added 7.0 to affected product versions
updated 4/26/10: Added 6.5.6 to affected product versions, changed targeted versions for fix, clarified conditions under which issue appears
updated 6/29/10: Added link to 6.5.6 fix for this issue
When using a FlashBackup-Windows policy to back up a Microsoft Outlook personal folder file (.pst file) which has been compressed, no error will be reported on the backup job, but attempts to restore the file will fail with status code 5 (the restore failed to recover the requested files) reported in the Activity Monitor.
Without obtaining a fix, a potential for recovery failure exists when a single file restore of a compressed Microsoft Outlook personal folder file ("PST" files) from either a FlashBackup for Windows, VMware Consolidated Backup (VCB), vStorage or Hyper-V Mapped FullVM backup fails and it is unfeasible to perform a full volume restore to retrieve the file.
The restore can fail whether directed to the same location or to an alternate client.
What is Affected:
The following versions are affected on all applicable operating systems:
- NetBackup 5.1 through 6.5.6 AND 7.0 where FlashBackup-Windows policies have been created
This condition will only be experienced when all of the following conditions are met:
- A FlashBackup-Windows policy is backing up the PST file
- The PST file is compressed
- There is a data movement in to and/or out of the PST file after the snapshot has been taken and the actual backup is in progress
12:28:14.349 PM: [5456.5208] <2> tar_base::V_vTarMsgM: TAR - I:\User\name\Personal Folders(1).pst
12:28:14.349 PM: [5456.5208] <2> tar_base::V_vTarMsgM: MNR - The file was renamed to the following:
12:28:14.349 PM: [5456.5208] <2> tar_base::V_vTarMsgM: UTF - H:\User\name\Personal Folders(1).pst
12:28:14.349 PM: [5456.5208] <2> tar_restore_vxms::processStateAtHeader: TAR - Restore file: H:\User\name\Personal Folders(1).pst
12:28:14.442 PM: [5456.5208] <16> tar_restore_vxms::errorHandler: VXMS MESSAGE - severity 90, message 1: vfm_restore_write pathname = H:\User\name\Personal Folders(1).pst, message 2 = failed stat = 3
12:28:14.442 PM: [5456.5208] <16> tar_restore_vxms::writeData: fiml_write_file failed (uncompressed part) error = 3
The formal resolution to this issue (Etrack 1720780) is included in the following releases:
- NetBackup 7.0 Release Update 1 (7.0.1)
Please visit the following link for download and readme information:
There are currently no plans to resolve this issue in NetBackup 6.x at this time.
NetBackup 5.x End of Standard Support was March 31, 2008.
A fix for this issue has been posted for NetBackup 6.5.6 and can be obtained by accessing this TechFile:
For other versions:
Disable compression where PST files reside.
PST files which cannot be restored via a single file restore can still be restored by performing a disk image restore of the entire volume containing the file.
If neither of these workarounds is feasible, please contact Symantec technical support, referencing this document ID and Etrack 1720743 to obtain an Emergency Engineering Binary (EEB) containing a fix for this issue.
Symantec strongly recommends the following best practices:
1. Always perform a full backup prior to, and after any changes to the NetBackup environment.
2. Always make sure the NetBackup environment is running the latest version and patch level.
3. Perform periodic "test" restores.
4. Subscribe to technical articles.
How to Subscribe to Email Notification:
Directly to this Article:
Subscribe to this TechNote for any updates which are made to this article, by clicking on the following link:
If this technical information has not been received from the Symantec Technical Support Email Notification Service, please click on the following link to subscribe to future notifications: