Deployment considerations for GroupWise
System requirements
GroupWise messaging system
NetIQ eDirectory Services
SQL Server
Archive Manager Server operating system
Prerequisites for servers running GroupWise Services
Prerequisites for servers running Archive Manager services
Prerequisites for servers running Archive Manager websites
Attachment store types
Web browsers
Archive Manager rights and permissions
Hardware recommendations
Archive Manager Services server
Archive Manager SQL database server
Archive Manager hardware recommendations
Sizing the Microsoft SQL database and Archive Manager attachment store
Pre-installation preparations
Installing and configuring Archive Manager
Upgrading/Uninstalling Archive Manager
Post-installation tasks
Configuring Archive Manager
Configuring the GroupWise Directory Connector (GDC)
Backloading your data
Localizing Archive Manager website (optional)
Appendix A: Attachment store types
Attachment store types overview
NTFS/Windows File System
NetApp SnapLock
EMC Centera
Caringo CAStor/Dell DX
Hedvig Distributed Storage Platform
Common scenarios for editing the configuration
Appendix B: Process overview checklist
Archive Manager SQL database server
The Archive Manager SQL database server performs the following function listed below:
Archive Manager hardware recommendations
This following section shows the estimated hardware recommendations for Archive Manager Services server and SQL database server. This are minimum recommendations and are subject to change based upon your messaging environment. For operating systems and other software requirements, see System requirements.
SQL database server
|
• |
Memory*: The total amount of required operating memory may be lower during initial archiving. As more data is archived and indexed, the memory footprint will increase. |
|
• |
AM Database Data**: Database read/write speeds are key to Archive Manager performance. The faster the data can be read from the database, the faster a request is returned to the user. |
Services server
|
• |
CPU (Total Cores)*: The total amount of required CPU cores increases as the number of active threads increases. The store management service will export a single mailbox in a single thread. More active threads allow a faster ingestion rate. Full Text Index also has the ability to run multiple processing threads. The administrator needs to find the appropriate balance. |
|
• |
Memory**: The total amount of required operating memory may be lower during initial archiving. As more data is archived and indexed, the memory footprint will increase. |
|
• |
Index Disk(s)***: The performance of the index disk will greatly impact the general performance of the product. For best results, use dedicated attached storage. New indexing technology allows the ability to span the index across multiple disk for both performance and fault tolerance. |
|
• |
Attachment Disk****: The performance of the attachment disk has less impact on the general performance of the product, but for the fastest retrievals, a faster disk is recommended. |
