I ran into an issue with a customer and came to the conclusion that NetBackup just will not recover "auto saved" files and those that were open. However, customer is asking if it backed up, it should be recoverable, which is a valid point. I could not find documentation to prove this and am hopping on here to see whether or not you can validate. Here is why:
Both files mentioned had "(Auto Saved)" in the file name and backed up a sister file with a '~' as a prefix. The fact we ran a file level restore from the same image and same directory, proved nothing was wrong with the backup. But am I correct in thinking these files are just pointer records and it's the admins' duty to exclude them from backup?
The problem looks to be you are trying to restore a file from an Windows optimized backup (policy attribute "Enable optimized backup of Windows deduplicated volumes" checked) of a Windows deduplicated file system from MSDP. This is not supported for this type of backup and the source must be from Basic disk (the initial backup also must be sent to Basic disk).
It may be possible to recover the data with the help from Veritas support. If the data is important log a support call and reference article 100032817.
In the meantime, please review the requirements and target devices for these type of backups (it is detailed in the NetBackup Server Admin guide volume 1) to ensure you can recover files. At present it is unlikely that you would be able to restore any file from the backups of that file system.
Thanks for responding. I ran into that article about NTFS dedups and asked the customer whether or not they were, he couldn't confirm or deny it. He assured it's a VM policy. I suggested running an image restore, no-go there too. I am going to circle back and verify if it is an NTFS/NDMP dedup setup. However, wouldn't that mean no other file should be restorable? I'll update you with what I hear.
The point is a restore from a full backup is not guaranteed (and probably wont work). Restores from incremental backups should work as the incremental backup rehydrates the files (it is only the full backup that does funky stuff with the Windows dedupe file system).
And to your original question, there is nothing that special about the autosaved files to prevent them being restored (you just need to ensure that the backup is valid - which in this case it appears not to be).
We just verified that the policy is not an NTFS or NDMP dedup, nor is "optimized backups" enabled (it's actually greyed out). So, I am just sending him an exclusions list and explained that autosaved, autorecovered and ~ files will be backed up, but the backup validation occurs in the restore, so in essence it's a 'best effort' backup.