EMC Centera PEA file placement and connection string examples

To configure archiving with EMC Centera, it is important to understand where to place the Pool Entry Authorization (PEA) file, and the connection string formatting.

PEA file placement

The system on which you place the PEA file depends on whether you are using the Local Archive or the Central Archive approach.

  • Local Archive - Place a copy of the PEA file on each recorder that archives to the associated Centera pool.

  • Central Archive - Place a copy of the PEA file on each Central Archive server.

If there are multiple pools, only the PEA file for the pool to which the system archives must be present.

The PEA file can reside in any directory on a system. However, use no spaces in the path to the PEA file or in the PEA file name itself.

EMC Centera Connection String examples

The format for the Connection String is defined in the EMC Centera documentation and is opaque to Archive. The format is flexible, so the examples provided in the following table are for the more common deployment scenarios. The quotation marks in the examples delineate the complete string; do not include them when you enter the connection string.

Use Format To

Connection String Example

Specify single IP address

“10.1.1.1”

Specify multiple IP addresses to the same cluster

“10.1.1.1,10.1.1.2”

Specify main/backup addresses for failover

“primary=10.6.7.8, secondary=10.11.12.13”

Use a PEA profile with any connection string. (Requires adding the path to the end of the string)

Do not include spaces in the path to the PEA file, or the PEA file name.

“10.1.1.1?c:\centera\rwe.pea”

For more specialized cases In Risk Management, use cases to group interactionss according to the needs of the enterprise. Interactions can reside in multiple cases simultaneously. or for more detailed explanation of the format, see the EMC Centera documentation (available from the EMC Corporation).

Edit a fixed media definition

Delete a fixed media definition

Archive drives

Stop the deletion of archived interactions