Enterprise Vault™ Utilities
- About this guide
- ArchivePoints
- Audit Viewer
- Backtrace
- CenteraPing
- Domino Archive Exporter
- Domino Profile Document Tool
- Domino Retention Plan Tool
- DTrace
- EVDominoExchangeMigration Tool
- About the EVDominoExchangeMigration tool
- Client requirements for the EVDominoExchangeMigration tool
- Adding the EVDominoExchangeMigration tool to the Windows Server firewall exceptions list
- EVDominoExchangeMigration tool and Binary Tree
- Using Quest Notes Migrator for Exchange and the EVDominoExchangeMigration tool
- Requirements for other migration software with the EVDominoExchangeMigration tool
- Running the EVDominoExchangeMigration tool
- EVDuplicateCleaner
- EVEARemovalUtility
- EVFSASetRightsAndPermissions
- EVrights
- EVservice
- EVSPShortcutManager
- EVSVR
- About EVSVR
- Starting EVSVR
- EVSVR commands
- EVSVR application states
- Creating an EVSVR operation file
- Editing an EVSVR operation file in which you have enabled checkpointing
- Running an EVSVR operation
- About the EVSVR operation settings
- Using the output from one EVSVR operation as input for another operation
- Viewing the EVSVR output log file
- Running EVSVR in interactive mode
- Improving EVSVR performance when processing CAB collections
- FSARunNow
- FSAUndelete
- FSAUtility
- NTFS to Centera Migration
- About NTFS to Centera Migration
- Managing migrator jobs using NTFS to Centera Migration
- Creating migrator jobs using NTFS to Centera Migration
- Deleting active jobs using NTFS to Centera Migration
- Deleting source files after migration using NTFS to Centera Migration
- NTFS to Centera Migration log files
- Permissions Browser
- Policy Manager (EVPM)
- About Policy Manager
- Policy Manager syntax
- Saving a Policy Manager initialization file as a Unicode file
- Policy Manager initialization file syntax
- Sections and keynames in Policy Manager initialization file
- [Directory] section of the Policy Manager initialization file
- [Archive] section of the Policy Manager initialization file
- [ArchivePermissions] section of the Policy Manager initialization file
- [Filter] section of the Policy Manager initialization file
- [Mailbox] section of the Policy Manager initialization file
- [Folder] section of the Policy Manager initialization file
- [PublicFolder] section in the Policy Manager initialization file
- [PSTdefaults] section in the Policy Manager initialization file
- [PST] section in the Policy Manager initialization file
- [PSTcheckpoint] section in the Policy Manager initialization file
- [NSFDefaults] section in the Policy Manager initialization file
- [NSF] section in the Policy Manager initialization file
- [NSFCheckPoint] section in the Policy Manager initialization file
- Policy Manager initialization file examples
- Policy Manager initialization file example 1
- Policy Manager initialization file example 2
- Policy Manager initialization file example 3
- Policy Manager initialization file example 4: PST migration
- Policy Manager initialization file example 5: NSF migration
- Policy Manager initialization file example 6: folder permissions
- About using the Provisioning API to run Policy Manager scripts
- ResetEVClient
- Vault Store Usage Reporter
Recreating placeholders
You can use FSAUtility with the -c parameter to recreate the placeholders for archived files in their original location. This facility may prove useful if you need to restore a file server to its original state or synchronize the file server with the Enterprise Vault archive. If multiple versions of the same file exist in the archive, the utility creates a placeholder for the latest version only.
Note:
Before you use this option with Dell EMC Celerra/VNX placeholders, ensure that FSAUtility is configured to use a suitable method for identifying the placeholders.
See About using FSAUtility with Dell EMC Celerra/VNX placeholders.
FSAUtility -c -s UNC_path [-D mm-dd-yyyy] [-f] [-l log_level] [-r]
Where:
-s UNC_path specifies the path to the required folder, volume, or file server.
-D mm-dd-yyyy specifies an archive date. FSAUtility recreates placeholders for files archived after the specified date.
-f forces FSAUtility to recreate the placeholders when placeholders or files of the same name already exist. The utility first deletes the existing placeholders or files and then creates the new ones.
-l log_level specifies whether to log both successful operations and failed operations (0) or failed operations only (1). By default, FSAUtility logs failed operations only.
-r specifies report mode. FSAUtility generates a report that outlines the activities that it would perform if you were to run it in normal mode, but without performing those activities.
FSAUtility generates a report named
EV_FILESYSTEM_UTILITY_REPORT_DateTime.txt, in the folderinstallpath\Reports\FSAUtility.If you run -c in normal mode, FSAUtility generates a report named
EV_FILESYSTEM_UTILITY_REPORT_DateTime.xml.
The following command recreates the placeholders for the folder \\myserver\users and generates a log file that lists both successful operations and failed operations. The command runs in report mode.
FSAUtility -c -s \\myserver\users -l 0 -r
The following command recreates the placeholders for those files that were archived after July 10 2005 from the folder \\myserver\users\user1. If any files or placeholders of the same name already exist, the command overwrites them with new placeholders.
FSAUtility -c -f -s \\myserver\users\user1 -D 07-10-2005 -l 0
FSAUtility does not support "hard link" files (directory references to files). You cannot recreate any existing placeholders for hard link files. When you perform a recreate operation, FSAUtility recalls any placeholders that are hard link files.
When you recreate placeholders with FSAUtility, you may receive the message "Internal Error Moving Placeholders: Archive ID null for folder folder_path" if you subsequently try to move them to another location. To stop this message from appearing, recreate the archive points and then archive the source folder before you try to move the placeholders.
Due to a NetApp restriction, FSAUtility does not recreate placeholders if the path to the folder exceeds 512 characters.