Virtual Machine Recommendations for LAW PreDiscovery and Early Data Analyzer

Transcription

1 Virtual Machine Recommendations for LAW PreDiscovery and Early Data Analyzer Operating System and Software Requirements Virtual Machines Recommendations Early Data Analyzer Web Requirements Software Licensing Considerations

2 Virtual Machine Recommendations for LAW PreDiscovery and Early Data Analyzer No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without permission. While the information contained herein is believed to be accurate, this work is provided "as is," without warranty of any kind. The information contained in this work does not constitute, and is not intended as, legal advice. LexisNexis and the Knowledge Burst are registered trademarks of Reed Elsevier Properties Inc., used under license. LAW PreDiscovery is a registered trademark of LexisNexis, a division of RELX Inc. Other products or services may be trademarks or registered trademarks of their respective companies. LAW PreDiscovery Concordance CaseMap LexisNexis Early Data Analyzer LexisNexis Early Data Analyzer Web Version: / / Release Date: February 5, 2018

3 Contents 3 Table of Contents Chapter Virtual Machine Environments for LAW and EDA Operating System and Software requirements 6 Virtual... Machine and SQL Server Setups... 8 Early Data Analyzer Web Configurations... 8 Licensing for Virtual Machines 3

4 4 LexisNexis Early Data Analyzer Virtual Machine Environments for LAW and EDA Operating System and Software requirements LAW and Early Data Analyzer's System Requirements Below is the current list of supported operating systems and software required for LAW PreDiscovery (LAW) and/or Early Data Analyzer (EDA). For a detailed listing of system requirements please refer to the System Requirements in the Online Answer Center under the corresponding software's Installation Instructions. Support Version Details Operating System Win 7 64-bit Win 7 32-bit Win 7 64-bit Sp1 Win 7 32-bit Sp1 Windows 8.1 Windows Server 2012 Windows Server 2012 R2 Win 10 Both EDA and LAW support these Microsoft Windows Operating systems. SQL Server SQL 2008 R2 64-bit SQL bit SQL bit SQL bit SQL Express editions may be used; however, SQL Express has limited capacity and should only be used for lighter workloads. Microsoft Office Office 365 (Desktop Installed) The following list matches the operating system with the compatible Microsoft Office version: Windows 7 32-bit Sp 1 Windows 7 64 Sp 1 Windows Server 2008 R2 Sp 1 Windows 8.1 Windows Server 2012

5 Virtual Machine Environments for LAW and EDA Support Version 5 Details Windows Server 2012 R2 Office 365 (Desktop Installed) Windows 10 Office 365 (Desktop Installed) LAW requires Office for ED Loader and Native file Conversion to paper, Tiff, or PDF. For ED Loader in LAW Office needs to be 32-bit version. Internet Explorer IE Version 9 IE Version 10 IE Version 11 LAW requires Internet Explorer for HTML native file conversion to paper, Tiff, or PDF. Adobe Adobe Acrobat Professional: 8.0, X ( ) LAW only requires this source application for Native file conversion to paper, Tiff, or PDF. Adobe Acrobat: 9 (9.4.4), 9 (9.5.5), Mail Store Microsoft Visio Adobe Reader: 8 (8.0.12), 9 (9.0), 10 (10.0), 11 ( /11.0.X) (Lotus) IBM Notes: LAW and EDA require a version of 8.02, 8.5.2, (Lotus) IBM Notes for processing these types of mail stores Visio 2007, 2016 LAW only requires this source application for Native file conversion to paper, Tiff, or PDF. Microsoft Project Microsoft Project: 2003 ( ), 2007 ( ), 2016 LAW only requires this source application for Native file conversion to paper, Tiff, or PDF. Edrawings Edrawings: 2011 ( ), 2013 ( ) Version 19c2 LAW only requires this source application for Auto Cad Native file conversion to paper, Tiff, or PDF. LAW can use this as an alternative (not required) source application for Native file conversion to paper, Tiff, or PDF. Autovue

6 6 LexisNexis Early Data Analyzer Support Version Details Quick View Professional Quick View Professional: 11, 13 LAW can use this as an alternative (not required) source application for Native file conversion to paper, Tiff, or PDF. Irfanview IrvanView Version 4.44 LAW can use this as an alternative (not required) source application for Native file conversion to paper, Tiff, or PDF. Virtual M achine and SQL Server Setups Virtual Workstation and SQL Server Setups for LAW and EDA There are two setup categories: Standard: Minimal/default recommendations for environments with limited resources Optimal: Best performance recommendations LAW VM Workstations The number of VMs for LAW workstations should reflect the number of licenses available for use. Please consult with your LAW users to determine the number of licenses available or needed. Category CPU Cores Standard LAW PreDiscovery VM 2 Optimal LAW PreDiscovery VM 4 RAM 4 GB 8 GB EDA VM Workstations VMs for EDA are specified differently than LAW because EDA utilizes workstation cores for processing while LAW does not. Please consult with your EDA users to determine the best approach. The three examples below illustrate the worker/agent concept with regard to resource planning: 1 EDA worker/agent = 1 CPU core of a VM workstation. Example 1 If 4 CPU Cores are available When using EDA on the same workstation as LAW, we encourage configuring the VM workstation according to the Optimal recommendation for LAW VM workstations. In this configuration, EDA will use all 4 cores of the workstation to allocate workers/agents.

7 Virtual Machine Environments for LAW and EDA 7 Example 2 If 8 CPU Cores are available 2 separate workstations A: If 2 workstations configured to the Optimal LAW VM workstations recommendations are available, EDA will distribute work across these 2 VMs so long as 8 worker/agent licenses are also available. Example 3 EDA can also utilize 8 cores and 16 GB of RAM if available on the same VM workstation to allocate all 8 worker/agents so long as 8 worker/agents licenses are also available. We recommend that such a VM be dedicated for EDA processing only. LAW and EDA SQL Server Recommendations To avoid competition for resources, we recommend using separate SQL servers for EDA and LAW as follows: EDA or LAW SQL Server RAM is recommended to be 4 times the number of cores available on the Server OS. For example, a 4 core SQL Server requires 16GB of RAM. Number of LAW VM workstations per LAW SQL Server The number of LAW workstations that can be comfortably served by SQL Server is determined by the number of cores on the SQL Server. We recommend no more than 16 LAW workstations per SQL Server core as a standard configuration. An optimal configuration would be fewer LAW workstations per SQL Server core. The chart below shows the server to workstation standard and optimal recommendations: Standard LAW SQL Server Up to 16 LAW workstations Optimal LAW SQL Up to 8-10 LAW workstations Server Number of EDA worker/agents per EDA SQL server The number of EDA worker/agents that can be comfortably server by SQL server is determined by the number of cores on the SQL server. We recommend no more than 4 worker/agents per SQL server core as a standard configuration. Standard EDA SQL Server 2 EDA agents/workers per SQL core (up to 8 agents/workers) Optimal EDA SQL Server 1 EDA agent/worker per SQL core (up to 4 agents/workers) Overhead Sizes for LAW and EDA For LAW, the overhead is in the file server more than the LAW SQL database itself. Most of the

8 8 LexisNexis Early Data Analyzer data stored in a LAW database is metadata and image information LAW points to or references the files located on file server for activities such as native file conversion or export. For EDA, the overhead is in the SQL Server database. Since EDA relies heavily on SQL Server, the majority of data, like content and metadata, is stored in the SQL Server database. There is a case creation option in EDA for copying the content to separate text files on the file server. This will decrease the size of the EDA SQL Server database. However, taking this approach could decrease the speed in indexing and searching in EDA. The reason for this note is to let you know an alternative option if the level of storage space is limited for your SQL Server databases. Early Data Analyzer Web Configurations EDA Web Setup and Configuration (Optional) Early Data Analyzer Web requires a Web server for hosting the Early Data Analyzer Web Application s Web site. The Web site uses the WISA stack. The required operating systems, applications, and framework for the web server are listed below. Installation documentation is provided by our LAW/EDA Technical Support team. Server OS Server 2008 R2 X64 Server 2012 X64 Server 2012 R2 X64 (Express Editions are supported as well) Applications and Framework IIS 7.5 or Higher A ASP.Net (.net4, MVC 3) Browsers supported Internet Explorer - IE 9, IE 10, IE 11 Microsoft Edge Firefox Chrome Safari Licensing for Virtual M achines Software Licensing (Versions 6.8/1.8 and higher) As of version 6.8/1.8 of LAW/EDA, we offer software based licensing. For those who are using our older style hardware USB dongle key, this can be an alternative in going 100% virtual. Some things to note are listed below. A: The installation can be provided by our LAW/EDA technical support team for installation instructions B: Contact your LexisNexis Account Manager to request transfer from the USB hardware dongle key to software based licensing. C: Installation of the new licensing system is in the existing version of 6.8 and higher

9 Virtual Machine Environments for LAW and EDA 9 D: Existing LAW/EDA SQL server can be used to host the licensing server or alternative server can be used. Please note that machine specifics of the computer/server hosting the license is used in generating the authorization for licensing. If you are planning to make changes to your license server that would affect the machine s unique identifiers, then please contact LAW PreDiscovery Support to assist with the license transfer prior to making the changes to avoid any disruption of service. Currently, virtual machines set to auto migration in cluster environments are not supported because it will change the machine unique identifiers; this will invalidate the license server. For cluster environments, it s recommended that you turn off auto migration on the VM that is the license server to avoid any disruption of service.