Product Overview

Archive One resolves the major email archiving needs through a modular approach:

• Policy Enforces company e-mail control, retention and retrieval. Intuitive GUI-driven creation of multi-criteria policies keeps administration easy. Improves Exchange Server performance, archiving PSTs and mailboxes.
• Capacity Simple rules-driven archiving for Capacity Management and load balancing in Exchange.
• Compliance Copies email to secure, indexed archive to assist meeting regulations such as SARBANES-OXLEY, SEC, NASD, HIPAA.

Archive One provides ease of installation and management as well as low Total Cost of Ownership (TCO) through industry standard interfaces with your existing email and storage investment.

Email archiving no longer requires complex integration and long-term projects; Archive One is a modular solution that meets your needs with scalable and robust applications.

Drivers to archive

Three basic requirements are commonly expressed when email administrators are asked about their needs for archiving. These being:

• To aid the organization meet legal requirements (compliance).
• To improve system performance (capacity).
• To manage the retention of corporate information (ePolicy).

When we discuss archival with email administrators for their key requirements within each of these areas, their answers generally cover the following. Your organization is probably no exception.

• Compliance Assist compliance with legal requirements.
• Reduce the legal risks associated with emails.
• Improve the awareness to the organization of legal exposure.
• Ability to store, search and retrieve emails.
• Capacity To improve the email system performance.
• Fast implementation without need for complex infrastructure.
• To help improve Service Level Agreements (SLA’s).
• Reduce back-up/restore times.
• Enforce company e-Policy.
• Provide retention of emails (corporate information).
• Reduce legal exposure.
• improve system performance.

Unfortunately, in practice, the solution to one requirement may be in direct conflict to the aims of another. This is because the business requirements often differ hugely from the IT drivers; even the IT infrastructure requirements can conflict with each other.