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
Configuring which API call FSAUtility uses to identify Dell EMC Celerra/VNX placeholders
The FSAUtility.exe.config file controls which API call FSAUtility uses to identify Dell EMC Celerra/VNX placeholders. For each placeholder-related FSAUtility option, the file contains an entry to specify which API call to use.
In the supplied FSAUtility.exe.config file these entries are all commented out, so FSAUtility uses its default API call for each option. That is, FSAUtility uses the Celerra/VNX API call for placeholder migration, and the Windows API call for the other placeholder-related options.
You can edit the FSAUtility.exe.config to set which API call FSAUtility uses for an option.
To configure which API call FSAUtility uses to identify Dell EMC Celerra/VNX placeholders
- On the Enterprise Vault server on which you want to run FSAUtility, navigate to the Enterprise Vault installation folder, for example
C:\Program Files (x86)\Enterprise Vault. - Open the
FSAUtility.exe.configfile with a text editor such as Notepad. Find the section of the file for the FSAUtility option whose API call you want to set:
<PHMigration> for the FSAUtility -pm option.
<MovePlaceHolder> for the FSAUtility -m option.
<BulkRecall> for the FSAUtility -b option.
<RecreatePlaceHolder> for the FSAUtility -c option.
<OrphanPlaceHolder> for the FSAUtility -o option.
- Remove the comment characters from the start and end of the section.
- If the CheckCelerraOfflineAttribute key is omitted or commented out for any option, FSAUtility uses its default API call for that option.
Edit the value of the CheckCelerraOfflineAttribute key to the required setting:
A value of 0 sets the option to use the Windows API call.
A value of 1 sets the option to use the Celerra/VNX API call.
- Repeat steps 3 to 5 for each FSAUtility option for which you want to configure the API call.
- Save the changes to
FSAUtility.exe.configfile.