What are some ways that a file can be a placeholder but not be in the archive?

[tluncefo]

We have a couple FSA only environments (8.0.4 and 9.0.2) and we are starting to come across files that are placeholders, but there is no corresponding file in the archive.

I am just wondering what ways exist that would allow this to occur.

This is an example of the error code we get when we try to recall the file:

Error The item is no longer in the vault      (0xc0045034)

[LCT]

It means that the archived item has been deleted from vault one way or another. Antivirus deleting DVS files is a typical way, corrupted disks which causes corrupted archived data. If this is the case then you will need to restore vault store partitions from backup.

I would recommend running EVSRV to check your database against your vault store partitions and do repair etc. You'll need to have special attentions when running EVSRV so you might want to log a case with SYMC Tech Support.

[LCT]

It is possible that the archive(s) have been deleted from the EV server and the placeholders have become orphaned.

[John_Chisari · Accepted solution]

To me that error means that the item has been cleanly deleted from it's corresponding archive, evsvr is not going to show you much.

Would suggest running fsautility with the -o -r options to give you a report on how many orphaned shortcuts are on your file servers.

[Jeff_Shotton]

Having duplicate placeholders (from a restore operation, perhaps) with delete on delete or delete on recall set.

Storage expiry taking care of the data

The file is actually just an offline file (the placeholder icon is actually just an offline file indicator)

You could run FSAUtility to find out how many 'orphan' placeholders there really are.

http://www.symantec.com/docs/TECH185615

Plenty of 'valid' reasons that this might happen before suspecting dvs files deleted or some sort of error in the system.

Regards,

Jeff