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
About using FSAUtility with Dell EMC Celerra/VNX placeholders
Read this section if you want to use FSAUtility with placeholders on Dell EMC Celerra/VNX volumes.
FSAUtility can identify a placeholder on a Dell EMC Celerra/VNX device by using either a Windows API call or a Celerra/VNX HTTP API call. Table: Default API call for detecting Dell EMC Celerra/VNX placeholders lists the API call that FSAUtility uses by default with each of its placeholder-related options.
Table: Default API call for detecting Dell EMC Celerra/VNX placeholders
FSAUtility option | FSAUtility parameter | Default API call for detecting Dell EMC Celerra/VNX placeholders |
|---|---|---|
Bulk recall of files corresponding to placeholders | FSAUtility -b | Windows API call |
Recreate placeholders | FSAUtility -c | Windows API call |
Move placeholders and their corresponding files | FSAUtility -m | Windows API call |
Delete orphaned placeholders | FSAUtility -o | Windows API call |
Migrate placeholders | FSAUtility -pm | Celerra/VNX API call |
Note that by default FSAUtility with the -pm parameter uses the Celerra/VNX API call. This default helps to ensure that placeholder migration always succeeds, regardless of the Celerra/VNX configuration. If you use FSAUtility -pm with any supported Celerra/VNX configuration, you may want to change the setting for this option to use the more performance-efficient Windows API call.
With the other placeholder-related parameters (-b, -c, -m, and -o), FSAUtility uses the efficient Windows API call by default.
You can configure the API call that FSAUtility uses for each placeholder-related option by editing the FSAUtility.exe.config file.