Chat now with support
Chat with Support

Archive Manager 5.4 - Installation and Configuration Guide for GroupWise

Deployment considerations for GroupWise System requirements Hardware recommendations Pre-installation preparations Installing and configuring Archive Manager Upgrading/Uninstalling Archive Manager Post-installation tasks Appendix A: Attachment store types Appendix B: Process overview checklist

EMC Centera

The EMC Centera is supported for the storage of attachments and compliance messages. The native Centera API is used to store attachments in the Centera cluster. Archive Manager considers the Centera to be an "always-online blind storage system." Archive Manager presents an attachment, and then receives a “ticket”. To get the attachment back, Archive Manager presents the ticket and gets the attachment.

Archive Manager does not set any retention policies on the Centera. This is left to the Centera administrator.

Archive Manager supports any centera settings which can be set on the Centera connection string or in a PEA file.

Using a PEA File

When utilizing a PEA file with a Centera Configuration, it is important that the PEA file is accessible by each component that requires access to it. The Archive Manager components that will access the Centera, and therefore require access to the PEA file, are:

•
Archive Data Load Service
•
Archive Full-Text Index Service
•
Website

As a result, the group ArchiveManagerServiceUsers should have permissions to access the PEA file location. The PEA file should also be present on all servers with the above Archive Manager components. (This is important if you have NLB WebServers, and/or a clustered Archive Manager installation).

If the machines are separate, then the PEA file must be either configured with a UNC path, or placed in the same local path as all machines that use the PEA file.

Caringo CAStor/Dell DX

The Caringo CAStor/Dell DX storage cluster is supported for the storage of attachments and compliance messages. The Caringo HTTP interface is used to store and retrieve items. Archive Manager considers the storage cluster to be an online blind storage system; we present an item, and receive a "ticket". To get the item back, we present the ticket and get the item. Note that performing a full text index reindex can overload the storage cluster with restore requests. Please consult Quest before doing this.

Bridgehead HDR

The Bridgehead HDR system is supported for the storage of attachments and compliance messages. The native HDR API’s are used to store attachments in a HDR system. Archive Manager considers the HDR to be a "usually-online blind storage system." Archive Manager presents an attachment, and then receives a “ticket”. To get the attachment back, Archive Manager presents the ticket and gets the attachment. If the HDR tells Archive Manager that the attachment is to be retrieved from slow storage (tape, DVD etc.), Archive Manager presents this to the user or handles it in the appropriate way.

Note that performing a full text index or reindex can cause the Bridgehead system to become overloaded with restore requests. Please consult with Quest before performing this action.

* 
NOTE: Using BridgeHead configured with transform methods is not supported. It causes Dataloader exceptions when processing messages.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating