System Requirements v7.5 May 10, 2013 For the most recent version of this document, visit kcura's Documentation Site.
Table of Contents 1 System requirements overview 3 1.1 Scalable infrastructure example 3 2 Software requirements 3 2.1 System (servers or virtual machines) 4 2.2 Workstations (end-user PC) 5 2.3 Relativity Desktop Client 5 3 Hardware requirements (single server 25-50 named users) 5 4 Hardware requirements (multi server 100 or more named users) 6 4.1 Native Imaging and Processing considerations 7 4.1.1 Relativity Native Imaging 7 4.1.2 Relativity Processing 7 5 Infrastructure configuration 8 5.1 Guides for infrastructure management 8 6 Scalability 8 6.1 Tier level definitions 9 7 Recommended configurations for new deployments 10 7.1 Virtual machines 10 7.2 SQL Servers 10 7.3 Storage 11 8 Obtaining applications for native imaging and processing 11 Relativity System Requirements - 2
1 System requirements overview 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. 1.1 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. 2 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. Relativity System Requirements - 3
Note: Make sure that you install the latest service packs for Windows,.NET, and SQL Server on your machines. 2.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. Note: For the File (Document) role, the type of storage system used will determine if you need to install the Windows operating system. Server Role Software Requirements Web (Application) Windows Server 2008 R2.NET Version 3.5.NET Version 4.0 (Full Framework) IIS 7.5 Agent (Background Processes) Windows Server 2008 R2.NET Version 3.5.NET Version 4.0 (Full Framework) SQL (Databases) Windows Server 2008 R2.NET Version 3.5.NET Version 4.0 (Full Framework) SQL Server 2008 R2 Standard or Enterprise Analytics (Search) Windows Server 2008 R2 Worker (Native Imaging/Processing) Windows Server 2008 R2.NET Version 3.5.NET Version 4.0 (Full Framework) Desktop Experience (Windows Server feature) Microsoft Office 2010 Professional (32-bit) - this includes OneNote and Publisher, which are also required applications Microsoft Visio Professional or Standard 2010 (32-bit) Microsoft Project Professional or Standard 2010 (32-bit) Lotus Notes v8.0 or higher Adobe Reader 4.0 or higher SolidWorks edrawings 2012 Viewer (32-bit) JungUm Global Viewer v9.0 or higher File (Document) NAS (NFS or CIFS), DAS, or SAN Relativity System Requirements - 4
2.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 Operating Systems Browsers Versions Windows 8 Desktop Mode (PC) Windows 8 Pro Desktop Mode (Surface) Windows 7 Windows Vista Windows XP Windows Server 2008 R2 Microsoft Internet Explorer 10.x (32-bit) Windows 8 only; supported by Relativity 7.5.630.50 and later Microsoft Internet Explorer 9.x (32-bit) Microsoft Internet Explorer 8.x (32-bit) Microsoft Internet Explorer 7.x (32-bit) Note: Internet Explorer 10 on Windows 7 Preview is not supported. If you are using SSL and running Internet Explorer 10.x in Windows 8, you must enable Compatibility View for Relativity. See Enabling Compatibility View for details. 2.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.0 (Full Framework) Microsoft Visual C++ 2010 Redistributable x86 or x64 Note: Visual C++ 2010 Redistributable x86 is supported on 32-bit and 64-bit OS, but x64 is supported on 64-bit OS only. 3 Hardware requirements (single server 25-50 named users) With the exception of Native Imaging and Processing, kcura supports the installation of all Relativity components on a single device for 25-50 named user agreements. However, we recommend a two-server setup for most 25-50 named user agreements to improve performance, stability, and scalability. This configuration includes a physical SQL Server that meets or exceeds the following specifications, and a virtual Relativity System Requirements - 5
host for all other Relativity components. The two-server setup can also support Native Imaging and Processing. Hardware Minimum Requirements Processor 8 physical cores (2GHz) Memory 64GB RAM Storage This server can be attached to a storage device (SAN, DAS, NAS). See Storage. 4 Hardware requirements (multi server 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. If you deploy Native Imaging and Processing in your environment, your Relativity installation requires a Worker and SQL Server. In addition to the minimum hardware requirements, the following guidelines also apply to these servers: Worker (Native Imaging/Processing) - This server has a hard cap of 16 threads per worker machine, and each processor core will spawn two threads. We suggest allocating 8 cores and 16 GB RAM to each worker role if using Relativity Processing. SQL (Native Imaging/Processing) - This SQL instance may not be required. See Native Imaging and Processing 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 Web (Application) Processor: 4 cores (2GHz) Memory: 4GB RAM Network: Gigabit Ethernet Agent (Background Processes) Processor: 4 cores (2GHz) Memory: 4GB RAM Network: Gigabit Ethernet SQL (Workspace Databases) Processor: 8 cores (2GHz) Memory: 32GB RAM Network: 4 Gbps to storage Analytics (Search) Processor: 4 cores (2GHz) Memory: 32GB RAM Network: Gigabit Ethernet Relativity System Requirements - 6
Server Role Minimum Hardware Requirements 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. Worker (Native Imaging/Processing) Processor: 4 cores (2GHz) Memory: 8GB RAM Network: Gigabit Ethernet SQL (Native Imaging/Processing) Processor: 4 cores (2GHz) Memory: 16GB RAM Network: 4 Gbps to storage 4.1 Native Imaging and Processing considerations The enhanced Native Imaging capabilities introduced in Relativity 7 are included in all Relativity license agreements. Please contact kcura for assistance with Relativity Processing. 4.1.1 Relativity Native Imaging Relativity Native Imaging uses a queue database. When you have more than 20 worker machines online (approximately 80 processor cores or more than 150 200 total threads), the SQL Server hosting this database may reach I/O and CPU performance thresholds during heavy usage. When this many worker threads are active, the Native Imaging queue database may warrant its own SQL instance, which is separate from the workspace databases. 4.1.2 Relativity Processing An individual store database corresponds to each Relativity workspace database where Relativity Processing is enabled. For scaling considerations, store databases should be treated in the same manner as Relativity workspaces. You are required to deploy a separate SQL instance before installing and using Relativity Processing. This SQL instance must have four processor cores and 16GB of memory. In addition, the Native Imaging queue database and the Relativity Processing store databases must live on the same SQL instance. Consequently, one SQL Server will accommodate both Native Imaging and Processing. Relativity System Requirements - 7
5 Infrastructure configuration Relativity supports the following technologies as part of its infrastructure configuration: Virtualization kcura suggests virtualizing all Relativity roles with the exception of SQL. 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. 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. Perimeter Networking (DMZ) Relativity requires certain ports to remain open for proper server communication. NIC Teaming and Multipath I/O Relativity supports the aggregation of network or storage connections for performance and redundancy. 5.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 Very Large Workspace Support o Infrastructure o Workflow Infrastructure Planning Performance metrics and recommendations overview 6 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. Relativity System Requirements - 8
6.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: 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 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. Tier 1 Tier 2 Tier 3 Entry Level Environment Mid-Level Environment Large Scale Environment Enabled User Accounts < 300 300-1000 1000+ Simultaneous Users < 100 100-500 500+ Active SQL Data (TB) < 1 1-10 10+ Active Record Count (MM) < 20 20-100 100+ Active File Size (TB) < 5 5-30 30+ The equipment used to support environments at each tier is described in the following table. Tier 1 Tier 2 Tier 3 Entry Level Environment Mid-Level Environment Large Scale Environment Total Cores for Non-SQL < 32 32-96 96+ Total RAM for Non-SQL (GB) < 64 64-256 256+ Total Cores for SQL Server < 16 16-96 96+ Total RAM for SQL Server (GB) < 128 128-1024 1024+ Total SQL Storage I/O (Gbps) 4-8 8+ SQL Server Fast Track SQL Tempdb Storage Separate spindles SSD or PCIe flash SSD or PCIe flash SQL Server Edition Standard Standard or Enterprise Enterprise 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. Relativity System Requirements - 9
7 Recommended configurations for new deployments Please contact kcura Client Services or Sales and Marketing for assistance with designing your Relativity infrastructure. 7.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. Tier 1 Quantity RAM (GB) vcpu Entry Level Environment Web 2 8 4 N/A Agent 2 4 4 Analytics 1 32 4 Worker 1 16 8 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 RAM (GB) vcpu Mid-Level Environment Web 3 8 4 Web (dtsearch, Loading) 2 8 4 Agent 2 8 8 Analytics 2 64 4 Worker 4 16 8 7.2 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 RAM (GB) CPU Entry Level Environment SQL (Workspace Databases) 1 64 8 SQL (Native Imaging/Processing) 1 16 4 For Tier 2 environments, the number of SQL Servers as well as RAM and CPU is twice that recommended for Tier 1, while the Native Imaging and Processing recommendations remain the same. Relativity System Requirements - 10
Tier 2 Quantity RAM (GB) CPU Mid-Level Environment SQL (Workspace Databases) 2 256 16 SQL (Native Imaging/Processing) 1 16 4 7.3 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 and less than 1GB for Relativity installation files. Data Type 25-50 Named 100+ Named Disk I/O RAID Type Users Users SQL Databases 500 GB 750 GB High 5 5+0 1+0 The databases can live across multiple storage volumes and SQL instances. SQL Full Text Indexes 150 GB 250 GB Moderate 5 5+0 1+0 Index size depends on the number of fields and records indexed. SQL Database Logs 150 GB 250 GB High 1 1+0 Transaction log backups or a simple recovery models keep these values small. SQL Tempdb 80 GB 80 GB High 1 1+0 kcura recommends eight 10GB Tempdb data files for new deployments. SQL Backups 500 GB 1000 GB Low 5 5+0 1+0 kcura recommends having a backup strategy. This volume is not required. dtsearch Indexes 150 GB 250 GB Moderate 5 5+0 The dtsearch index share is typically stored in the same location as the files. Analytics Indexes 150 GB 250 GB Moderate 5 5+0 The Analytics index share is typically stored in the same location as the files. Files (Natives/Images) 1500 GB 3000 GB Low 5 5+0 The files may not require a Windows installation depending on the storage. Multiple Processing Workers online will require more file storage I/O. Worker (Native 100 GB 250 GB High 1 1+0 Imaging/Processing) This houses temp files created by the native applications during imaging. 8 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 2010 - this includes OneNote and Publisher, which are also required applications. Microsoft Visio Professional or Standard 2010 Microsoft Project Professional or Standard 2010 Relativity System Requirements - 11
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. Adobe Reader 4.0 or higher SolidWorks edrawings 2012 (32-bit) (with the option to view 3D XML and PRO/E files) JungUm Global Viewer v9.0 or higher Relativity System Requirements - 12
Proprietary Rights This documentation ( Documentation ) and the software to which it relates ( Software ) belongs to kcura Corporation 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. 2013. kcura Corporation. All rights reserved. Relativity and kcura are registered trademarks of kcura Corporation. Relativity System Requirements - 13