Running FSAUtility to check for orphaned placeholders will not class placeholders as orphaned for improperly deleted savesets.
| Article:TECH147650 | | | Created: 2011-01-07 | | | Updated: 2011-01-18 | | | Article URL http://www.symantec.com/docs/TECH147650 |
| NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made. |
Problem
When FSAUtility -o runs to delete Orphaned placeholder shortcuts, checks are only made against the Enterprise Vault databases, the utility will not check for missing savesets.
Cause
FSAUtility -o relies on the Enterprise Vault databases to check whether a placeholder is in an orphaned state. An orphaned placeholder occurs when an archived item is deleted programmatically from Enterprise Vault. This can be by Storage Expiry or Archive Explorer.
Solution
If a Saveset is missing from it's phyiscal location, the orphaned shortcut check will not delete the corresponding placeholder from the file server.
|
|
Article URL http://www.symantec.com/docs/TECH147650
Terms of use for this information are found in Legal Notices
Thank you.