Product SiteDocumentation Site

Chapter 6. Hardware considerations

6.1. CPU
6.2. Memory
6.3. Storage
6.4. Virtual vs Physical
Sizing and implementing Zarafa Archiver requires careful planning to ensure that the product can perform to expectations and scaling as the customer requirements grow and fits in the existing infrastructure.

6.1. CPU

In most deployment scenarios the Zarafa Archiver will be installed on a dedicated server which doesn’t provide any other services. The most heavy actions performed on the archive server is the actual archive run, which is typically done once or twice a day. This archive run will in general do a lot of database transactions and is not running CPU intensive calculations.
The archiver run will archive the mailboxes one by one. For the right choice of the amount of CPU’s it’s recommended to use a multi-core system where one core is reserved for the Zarafa-server, one for the MySQL database server and one for the actual Archive controller.
The advised amount of CPU cores is 4 where the prefered archicture is 64bits, so more than 4Gb of memory can be allocated by processes.