Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
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
Example FSAUtility.exe.config file settings
The following examples show an FSAUtility.exe.config file that has been edited to produce various results.
The file sets the PHMigration option (for FSAUtility -pm) to use a Windows API call rather the default Celerra/VNX API call. No other values are defined, so FSAUtility uses the Windows API call for all of its placeholder-related options.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="PHMigration"
type="System.Configuration.DictionarySectionHandler"/>
<section name="BulkRecall"
type="System.Configuration.DictionarySectionHandler"/>
<section name="MovePlaceHolder"
type="System.Configuration.DictionarySectionHandler"/>
<section name="RecreatePlaceHolder"
type="System.Configuration.DictionarySectionHandler"/>
<section name="OrphanPlaceHolder"
type="System.Configuration.DictionarySectionHandler"/>
<configSections>
<PHMigration>
<add key="CheckCelerraOfflineAttribute" value = "0"/>
</PHMigration>
<MovePlaceHolder>
<!--><add key="CheckCelerraOfflineAttribute" value = "0"/>-->
</MovePlaceHolder>
<BulkRecall>
<!--><add key="CheckCelerraOfflineAttribute" value = "0"/>-->
</BulkRecall>
<RecreatePlaceHolder>
<!--><add key="CheckCelerraOfflineAttribute" value = "0"/>-->
</RecreatePlaceHolder>
<OrphanPlaceHolder>
<!--><add key="CheckCelerraOfflineAttribute" value = "0"/>-->
</OrphanPlaceHolder>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>This configuration produces the same result as Example 1. Each placeholder-related option is set to use the Windows API call.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="PHMigration"
type="System.Configuration.DictionarySectionHandler"/>
<section name="BulkRecall"
type="System.Configuration.DictionarySectionHandler"/>
<section name="MovePlaceHolder"
type="System.Configuration.DictionarySectionHandler"/>
<section name="RecreatePlaceHolder"
type="System.Configuration.DictionarySectionHandler"/>
<section name="OrphanPlaceHolder"
type="System.Configuration.DictionarySectionHandler"/>
<configSections>
<PHMigration>
<add key="CheckCelerraOfflineAttribute" value = "0"/>
</PHMigration>
<MovePlaceHolder>
<add key="CheckCelerraOfflineAttribute" value = "0"/>
</MovePlaceHolder>
<BulkRecall>
<add key="CheckCelerraOfflineAttribute" value = "0"/>
</BulkRecall>
<RecreatePlaceHolder>
<add key="CheckCelerraOfflineAttribute" value = "0"/>
</RecreatePlaceHolder>
<OrphanPlaceHolder>
<add key="CheckCelerraOfflineAttribute" value = "0"/>
</OrphanPlaceHolder>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>In this example, all of the placeholder-related options use the Celerra/VNX API call.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="PHMigration"
type="System.Configuration.DictionarySectionHandler"/>
<section name="BulkRecall"
type="System.Configuration.DictionarySectionHandler"/>
<section name="MovePlaceHolder"
type="System.Configuration.DictionarySectionHandler"/>
<section name="RecreatePlaceHolder"
type="System.Configuration.DictionarySectionHandler"/>
<section name="OrphanPlaceHolder"
type="System.Configuration.DictionarySectionHandler"/>
<configSections>
<PHMigration>
<add key="CheckCelerraOfflineAttribute" value = "1"/>
</PHMigration>
<MovePlaceHolder>
<add key="CheckCelerraOfflineAttribute" value = "1"/>
</MovePlaceHolder>
<BulkRecall>
<add key="CheckCelerraOfflineAttribute" value = "1"/>
</BulkRecall>
<RecreatePlaceHolder>
<add key="CheckCelerraOfflineAttribute" value = "1"/>
</RecreatePlaceHolder>
<OrphanPlaceHolder>
<add key="CheckCelerraOfflineAttribute" value = "1"/>
</OrphanPlaceHolder>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>