Enterprise Vault.cloud Feature Briefing

Transcription

1 Enterprise Vault.cloud Feature Briefing Lotus Domino Archiving in May 2012 release This document is one of a set of Feature Briefings which detail major new or changed features in Enterprise Vault.cloud. This document covers the changes to Lotus Domino archiving to use the native Domino 8.x journaling ability to journal to an external mail-in server over SMTP. If you have any feedback or questions about this document please them to EV-TFE-Feedback@symantec.com stating the document title. This document is provided for informational purposes only. All warranties relating to the information in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice. Copyright 2012 Symantec Corporation. All rights reserved. Symantec, the Symantec logo and Enterprise Vault are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

2 Feature Description Enterprise Vault.cloud (EV.cloud) has improved its Domino Archiving process by now using the native journaling approach to forward s to EV.cloud for archiving. Similar to journaling with Microsoft Exchange Server, the native journaling approach built into Domino 8.x will not require any EV.cloud modules to run on-premise as messages will be journaled directly to the EV.cloud SMTP gateway. This journaling method will replace the previous EV.cloud Domino archiving solution, which was based on a Domino journaling template and running a Lotus script agent. This solution had several limitations such as scalability, complicated deployment and poor server performance. Business Value The Domino native journaling approach does not require a third-party on premise component running on the customer s production Domino server. As this is the most maintainable solution for customers, the customer will be able to save on resources such as additional journaling databases and servers that may be required for the previous configuration. Further, EV.cloud s Archive Administration console allows customers to add users individually and accepts standard SMTP address formats, as well as those formats native to Domino. This allows users addresses formatted in the native Domino format to be included as an alias, capturing all data sent to that address. Underlying Principles Once users have been provisioned in EV.cloud and journaling has been configured on the Domino 8.x server, messages will begin flowing to the archive. When an external message is received, it is received through the SMTP listener which determines who the message is being sent to and forwards the message to the mail-in box where the users databases are stored. At the same time, the message is pushed through the router on the Domino server, searching for any conditions that may be configured on the server such as journaling. The message is then journaled through the cloud to the EV.cloud server (see Figure 1). Page 1

3 Figure 1 - EV.cloud Domino Archiving Architecture Page 2

4 Similarly, when a user sends an , the message leaves a copy on the users database and forwards the message on to the mail-in database where it is routed and sent to its final destination and a copy is forwarded to EV.cloud. Once messages, both incoming and outgoing, are sent, they are captured in EV.cloud and parsed and indexed to be searched at a later time. Test Drive For EV.cloud to capture Domino mails in the archive, two things must happen: 1. The customer must export a list of their users from the Domino directory using a Lotus script provided for EV.cloud. The script, by default, will export the users in the format necessary for bulk upload into Customer Service Tool used by EV.cloud. The exported user list can be uploaded using the exported.txt file, or can be uploaded in zip format. The exported user format will look similar to that which is seen in Figure 2. Figure 2 - Example Exported User List 2. Upon uploading and processing the user list for provisioning, customers will be given a report containing and erroneous accounts that should be corrected and re-uploaded into the system as shown in Figure 3. Page 3

5 Figure 3 - Bulk Import Once the Domino directory user list is imported, an EV.cloud team member will provide the address used for journaling that will be added to the Domino server. Domino 8.x, when configured for native journaling, will require a journaling address which will be configured in the Customer Service Tool by an implementation or support specialist (see Figure 4). Figure 4 - Configuring Journal Addresses Page 4

6 Auto-provisioning The EV.cloud Customer Service Tool (CST) and Archive Administration (Manage) do support the Native Domino Format and the existing Domino format will remain to allow support of existing template-based customers. It is expected that Domino customers will have a large number of users; hence, the manual addition of an entire company s user base is unrealistic long-term, as CloudLink will not support user synchronization. This will be supported in future releases. Legacy Data Ingestion s stored on a Domino server are formatted in.nsf message format and can be ingested into the archive if necessary. These messages, when received by the EV.cloud data management team, will be converted from.nsf to.pst format so the messages can be stored in the archive recognizable in EV.cloud. Should it become necessary for customers to export data from EV.cloud, the customer will have a number of message formats available for export including:.pst.nsf.eml.eml with EDRM Licensing and support considerations Customers who journal users can expect to pay per user, plus fees for any additional add-on services they may require. At present, the native Domino method for journaling to EV.cloud is not supported by the following: CloudLink does not currently support Domino directories and will not at this point be able to push users to the archive from the directory. o Webfolder push is not supported. o Single Sign-on is not supported. FolderSync is not supported as the folder structure and synchronization is not available. Requirements: The only requirement for this journaling method is the Domino server must be version Domino 8.x. Page 5

7 About Symantec: Symantec is a global leader in providing storage, security and systems management solutions to help consumers and organizations secure and manage their information-driven world. Our software and services protect against more risks at more points, more completely and efficiently, enabling confidence wherever information is used or stored. For specific country offices and contact numbers, please visit our Web site: Symantec Corporation World Headquarters 350 Ellis Street Mountain View, CA USA +1 (650) (800) Copyright 2012 Symantec Corporation. All rights reserved. Symantec and the Symantec logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.