System Requirements. Version 8.1 March 2, For the most recent version of this document, visit our documentation website.

Transcription

1 System Requirements Version 8.1 March 2, 2016 For the most recent version of this document, visit our documentation website.

2 Table of Contents 1 System requirements 3 2 Scalable infrastructure example 3 3 Software requirements System (servers or virtual machines) Workstations (end-user PC) Relativity Desktop Client 6 4 Hardware requirements (25-50 named users) 6 5 Hardware requirements (100 or more named users) 7 6 Infrastructure configuration Guides for infrastructure management 9 7 Scalability Tier level definitions 9 8 Recommended configurations for new deployments Virtual machines SQL servers Storage 11 9 Obtaining applications for native imaging and processing Licensing Microsoft products 13 Relativity System Requirements - 2

3 1 System requirements The system requirements include detailed information about the software and hardware used for hosting Relativity in your environment. In addition, they provide various recommendations for configuring a new deployment of Relativity, as well as scaling your environment as the number of users and the amount of data continue to grow. 2 Scalable infrastructure example Relativity is designed with a scalable infrastructure that you can tailor to the requirements of your environment. It is developed on the.net framework with a Microsoft SQL Server back-end. As illustrated in the following diagram, all areas of the platform are scalable providing support for any hardware vendor, hypervisor, and storage protocol. Relativity System Requirements - 3

4 3 Software requirements Relativity has specific software requirements for servers or virtual machines, user workstations, and the Relativity Desktop Client. The requirements for servers differ by the role assigned to them in your system configuration. Note: Make sure that you install the latest service packs for Windows,.NET, and SQL Server on your machines. 3.1 System (servers or virtual machines) The general software requirements for servers and virtual machines include Microsoft Windows Server and.net technologies. Microsoft Office and other applications are required for Native Imaging and Processing servers. See Obtaining applications for native imaging and processing on page 12. Note: For the File (Document) role, the type of storage system used will determine if you need to install the Windows operating system. The following table provides software requirements by server role. Server Role Software Requirements Agent (Background Processes and dtsearch) Windows Server 2012 or Windows Server 2008 R2.NET Version 4.5.NET Version 3.5 for installation on agent server Analytics (Search) Windows Server 2012 or Windows Server 2008 R2.NET Version 4.5 File (Document) NAS (NFS or CIFS), DAS, or SAN SQL (Workspace Databases and Native Imaging/Processing) Windows Server 2012 or Windows Server 2008 R2.NET Version 4.5.NET Version 3.5 SQL Server 2012 or SQL Server 2008 R2 Web (Application) Windows Server 2012 or Windows Server 2008 R2.NET Version 4.5.NET Version 3.5 IIS 7.5 or IIS 8.0 IIS 6 Metabase Compatibility Worker (Native Imaging/Processing) Windows Server 2012, Windows Server 2012 Relativity System Requirements - 4

5 Server Role Software Requirements R2, or Windows Server 2008 R2.NET Version 3.5.NET Version 4.5 Desktop Experience (Windows Server feature) Microsoft Office 2010 Professional SP2 (32-bit) - this includes OneNote and Publisher, which are also required applications Microsoft Visio 2010 Professional or Standard SP2 (32-bit) Microsoft Project 2010 Professional or Standard SP2 (32-bit) Lotus Notes v8.5.2 with Fix Pack 4 or Lotus Notes v8.5.3 with Fix Pack 6 Adobe Reader - we don't require a specific version SolidWorks edrawings Viewer 2013 (32-bit) with the option to view 3D XML and PRO/E files JungUm Global Viewer v9.0 or higher Note: Worker servers performing document conversion only (not processing or native imaging) only require Windows Server 2012/2012 R2/2008 R2,.NET Version 3.5,.NET Version 4.5, and Desktop Experience. 3.2 Workstations (end-user PC) In Relativity, end users perform their reviews on workstations, which must be configured with supported versions of the Microsoft Windows operating system and Internet Explorer. Software Browsers Versions You can use Relativity 8.1 on the following browsers only: Microsoft Internet Explorer 11.x (32-bit) (Supported by Relativity 8.1) Microsoft Internet Explorer 10.x (32-bit) (Supported by Relativity and later) Microsoft Internet Explorer 9.x (32-bit) Microsoft Internet Explorer 8.x (32-bit) Beginning in version 9.0, Relativity supports additional browsers, such as Safari for Macs. For more information, see the Relativity 9.0 Documentation site. Operating Systems Windows 8 Desktop Mode (PC) Windows 8 Pro Desktop Mode (Surface Pro) Relativity System Requirements - 5

6 Software Versions Windows 7 Windows Vista Windows XP Windows Server 2012 or Windows Server 2008 R2.NET 4.5 required before release compatible after release Note: Relativity 8.1 supports Internet Explorer 10 and 11 with Compatibility View. See the Workstation Configuration Guide for more information. If you're using Internet Explorer 10 with Windows 7, you may encounter certain JavaScript errors. See the Workstation Configuration guide for more information. 3.3 Relativity Desktop Client The Relativity Desktop Client (RDC) is a utility used for importing and exporting documents, images, natives, and productions. This utility requires the following software: Microsoft.NET 4.5 (Full Framework) Microsoft Visual C SP1 Redistributable x86 or x64 Note: Visual C SP1 Redistributable x86 is supported on 32-bit and 64-bit OS, but x64 is supported on 64-bit OS only. 4 Hardware requirements (25-50 named users) kcura supports the installation of all Relativity components on a single device for named user agreements. We also require that a hypervisor is installed to this device so each Relativity role has its own virtual machine. Hardware Minimum Requirements Memory 144GB RAM Processor 32 logical cores (2GHz) Storage This server can be attached to a storage device (SAN, DAS, NAS). See Storage on page 11. The following table provides information on hardware requirements for each virtual machine role. Virtual Machine Role Quantity Memory (GB) vcpu Web Agent Relativity System Requirements - 6

7 Virtual Machine Role Quantity Memory (GB) vcpu Analytics Worker SQL (Relativity) SQL (Processing/Native Imaging) Hardware requirements (100 or more named users) Relativity installations must use the required hardware to ensure high platform performance based on the number of users, workspaces, and other considerations. The following table lists the minimum hardware requirements for a Relativity installation. Note: Depending on the type of file storage system, the File server role may not require a physical server or VM. Server Role Minimum Hardware Requirements Agent (Background Processes) Processor: 4 cores (2GHz) Memory: 4GB RAM Network: Gigabit Ethernet Agent (dtsearch) Processor: 4 cores (2GHz) Memory: 4GB RAM Network: Gigabit Ethernet Analytics (Search) Processor: 4 cores (2GHz) Memory: 32GB RAM Network: Gigabit Ethernet File (Document) Processor: 4 cores (2GHz) Memory: 4GB RAM Network: Gigabit Ethernet SMTP (Notification) Relativity requires an active SMTP server on your network. It interfaces with this server to send notifications and monthly billing statistics. The hardware requirements for this role are minimal. You can leverage an existing SMTP server in the network or merge this server with the agent server role. SQL (Native Imaging/Processing) Processor: 4 cores (2GHz)* Memory: 16GB RAM Network: 4 Gbps to storage Relativity System Requirements - 7

8 Server Role Minimum Hardware Requirements SQL (Workspace Databases) Processor: 8 cores (2GHz) Memory: 64GB RAM Network: 4 Gbps to storage Web (Application) Processor: 4 cores (2GHz) Memory: 4GB RAM Network: Gigabit Ethernet Worker (Native Imaging/Processing) Processor: 4 cores (2GHz) Memory: 8GB RAM Network: Gigabit Ethernet Note: Based on a hard cap placed by kcura, each Worker server is allowed to spawn 16 threads. Each processor core and 2GB RAM will create two threads. Therefore, we suggest allocating 8 logical cores and 16GB RAM to each Worker server for the most throughput. * Processing uses only up to 8 cores, in which case there is no benefit to allotting more than 8 cores for processing. Any additional core will be used by another part of the system. 6 Infrastructure configuration Relativity supports the following technologies as part of its infrastructure configuration: Virtualization We suggest virtualizing all Relativity roles with the exception of SQL (workspace databases). Any hypervisor is supported. Note: Virtualizing SQL may simplify meeting HA and DR requirements. However, it can introduce additional layers of complexity when properly configuring and troubleshooting performance and stability related issues. We're not opposed to virtualizing SQL (native imaging/processing). This server demands less hardware resources, and any performance issues would impact only these Relativity features. High Availability (HA) Relativity supports SQL Server Failover and File Server Clustering along with available hypervisor solutions. Disaster Recovery (DR) Relativity supports Microsoft SQL Server mirroring, log shipping, and SAN replication technologies. These approaches typically require manual failover and increased downtime. Web Server Load Balancing Relativity supports only single affinity in Windows Network Load Balancing (NLB). The Relativity User Load Balancer (RULB) provides the ability to distribute the user load evenly. Relativity System Requirements - 8

9 Perimeter Networking (DMZ) Relativity requires certain ports to remain open for proper server communication. For more details, download the Relativity Infrastructure Ports Diagram from the Customer Portal. Note that you must have a valid portal username and password to download this content. NIC Teaming and Multipath I/O Relativity supports the aggregation of network or storage connections for performance and redundancy. 6.1 Guides for infrastructure management Review the following guides to become familiar with best practices for managing the Relativity infrastructure: Pre-Installation Guide Environment Optimization Guide Solutions for Very Large Workspaces o Infrastructure o Workflow Infrastructure Planning Recommendations Performance metrics and recommendations 7 Scalability You can scale Relativity installations to handle the performance, storage, and other environmental factors necessary to support the addition of new users, continual growth of data, and increased demands for searching capabilities. 7.1 Tier level definitions kcura has identified tier levels that support varying numbers of users and sizes of active data. You can use these tier level definitions to determine the cores, RAM, and other equipment required to support the rapid growth of your Relativity installation. Key terms used in the following table include: Enabled User Accounts amount of enabled Relativity User accounts. Simultaneous Users - average amount of simultaneous users logged into Relativity. Active SQL Data (TB) - total amount of disk space consumed by SQL databases (mdf) and full text (ndf) indexes. Active Record Count (MM) total amount of records (documents) included across all active Relativity workspaces. Active File Size (TB) - total amount of disk space consumed by native and image files. This table identifies the combination of users, data, and file sizes associated with each tier. Relativity System Requirements - 9

10 Tier 1 Tier 2 Tier 3 Entry Level Environment Mid-Level Environment Enabled User Accounts < Simultaneous Users < Active SQL Data (TB) < Active Record Count (MM) < Active File Size (TB) < Large Scale Environment The equipment used to support environments at each tier is described in the following table. Tier 1 Tier 2 Tier 3 Total Cores for Non- SQL Total Memory (GB) for Non-SQL Total Cores for SQL Server Total Memory (GB) for SQL Server Total SQL Storage I/O (Gbps) Entry Level Environment Mid-Level Environment < < < < Large Scale Environment SQL Server Fast Track ( SQL Tempdb Storage Separate spindles SSD or PCIe flash SSD or PCIe flash Note: Microsoft SQL Server Fast Track combines preconfigured servers, storage, and networking with SQL Server 2008 R2 Enterprise for a scalable enterprise data warehouse platform. You can choose industrystandard hardware from Dell, HP, Cisco, IBM, EMC, and other leading vendors. 8 Recommended configurations for new deployments Contact kcura Client Services for assistance with designing your Relativity infrastructure. 8.1 Virtual machines While Relativity supports the use of virtual machines, differing configurations are recommended depending on the tier level of your environment. This table lists the recommendations for environments at Tier 1. Relativity System Requirements - 10

11 Tier 1 Quantity Memory (GB) vcpu Entry Level Environment Web Agent Analytics Worker For Tier 2 environments, additional virtual machines are recommended as well as increased RAM and vcpus as illustrated in the following table. Tier 2 Quantity Memory (GB) vcpu Mid-Level Environment Web Agent Analytics Worker SQL servers The number of SQL Servers is influenced by HA and DR requirements as described in Infrastructure configuration. You can distribute Relativity workspace databases across multiple SQL instances. The recommendations for Tier 1 environments are listed in the following table. Tier 1 Quantity Memory (GB) CPU Entry Level Environment SQL (Workspace Databases) SQL (Native Imaging/Processing) For workspace databases, the number of SQL Servers as well as RAM and CPU is increased for Tier 2 environments. For native imaging and processing, the SQL Server requirements are the same for both Tier 1 and Tier 2 environments. Tier 2 Quantity Memory (GB) CPU Mid-Level Environment SQL (Workspace Databases) SQL (Native Imaging/Processing) Storage For each type of data, the amount of recommended space depends on the number of records imported, as well as the type and length of the expected reviews. Each server or VM needs space for the OS, page file and less than 1GB for Relativity installation files. For the Relativity Processing SQL Server, all the same SQL data is required with the exception of SQL Full Text Indexes. Throughput, especially when multiple SQL Servers are virtualized on a single host, should be put Relativity System Requirements - 11

12 through a regiment of rigorous random and sequential read/write IO testing before installation of Relativity is completed. Recommended space by data type: Data Type Named Users 100+ Named Users Disk I/O Example RAID Type SQL Databases 500 GB 750 GB High The databases can live across multiple storage volumes and SQL instances. SQL Full Text Indexes 150 GB 250 GB Moderate Index size depends on the number of fields and records indexed. SQL Database Logs 150 GB 250 GB High Transaction log backups or a simple recovery models keep these values small. SQL Tempdb 80 GB 80 GB High kcura recommends eight 10GB Tempdb data files for new deployments. SSDs recommended.. SQL Backups 500 GB 1000 GB Low kcura recommends having a backup strategy. This volume is not required. Larger data sizes may require higher I/O throughput. dtsearch Indexes 150 GB 250 GB Moderate The dtsearch index share is typically stored in the same location as the files. Analytics Indexes 150 GB 250 GB Moderate The Analytics index share is typically stored in the same location as the files. Files (Natives/Images) 1500 GB 3000 GB Low The files may not require a Windows installation depending on the storage. Multiple Processing Workers online will require more file storage I/O. Native Imaging Processing Worker (Native Imaging/Processing) 250 GB 250 GB High This houses temp files created by the native applications during imaging. This temp location never exceeds 250GB for each Worker server. 9 Obtaining applications for native imaging and processing On the Relativity Native Imaging/Processing worker, you must install additional software to support imaging/processing. This section includes the software that requires licensing or downloading software that is free: Microsoft Office Professional this includes OneNote and Publisher, which are also required applications. Relativity System Requirements - 12

13 Microsoft Visio Professional or Standard 2010 Microsoft Project Professional or Standard 2010 Note: For the Microsoft products listed above, the 32-bit version is required for installation. See Software requirements. Lotus Notes v8.0 or higher Note: For Lotus Notes v8.0, Domino servers are not required. You can install Lotus Notes Express Edition with the Notes Client component. - we don't require a specific version SolidWorks edrawings 2012 or 2013 (32-bit) (with the option to view 3D XML and PRO/E files) download.cnet.com/edrawings-2012/ _ html Note: This link is to a prior version of edrawings that may no longer be supported by its creator, Dassault Systems SolidWorks Corp. The software may not work as expected, and kcura is not responsible for any warranties, support, errors, problems, loss, or damage caused by this software or its use. JungUm Global Viewer v Licensing Microsoft products Relativity requires Microsoft Windows and Microsoft SQL Server, both of which you need to license through Microsoft or one of their resellers. If using Relativity Processing or Native Imaging, you also need to license Microsoft Office, Visio, and Project through Microsoft or one of their resellers. If Relativity is hosted for external customers, you may need to license Microsoft products through Microsoft s SPLA (Service Provider License Agreement). You can find more information about Microsoft s SPLA program on Microsoft s Hosting site. kcura recommends contacting Microsoft, or one of their resellers, for guidance on the licensing options available. Relativity System Requirements - 13

14 Proprietary Rights This documentation ( Documentation ) and the software to which it relates ( Software ) belongs to kcura LLC and/or kcura s third party software vendors. kcura grants written license agreements which contain restrictions. All parties accessing the Documentation or Software must: respect proprietary rights of kcura and third parties; comply with your organization s license agreement, including but not limited to license restrictions on use, copying, modifications, reverse engineering, and derivative products; and refrain from any misuse or misappropriation of this Documentation or Software in whole or in part. The Software and Documentation is protected by the Copyright Act of 1976, as amended, and the Software code is protected by the Illinois Trade Secrets Act. Violations can involve substantial civil liabilities, exemplary damages, and criminal penalties, including fines and possible imprisonment kcura LLC. All rights reserved. Relativity and kcura are registered trademarks of kcura LLC. Relativity System Requirements - 14