Relativity - System Requirements - v9 · Relativity|SystemRequirements-4...

System RequirementsMarch 23, 2017 - Version 9 & 9.1

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

For the most recent version of this document, visit our documentation website.

http://help.kcura.com/9.0/

Relativity | System Requirements - 2

Table of Contents

1 System requirements 3

2 Infrastructure overview 3

3 Scalability 5

3.1 Tier level definitions 5

4 Recommended configurations for new deployments 6

4.1 Tier 1 - Hardware requirements (25-50 named users) 6

4.2 Tier 1 - Hardware requirements (100 or more named users) 7

4.3 Tier 2 - Hardware requirements (300 or more named users) 7

4.4 Storage 8

5 Infrastructure configuration 9

5.1 Guides for infrastructure management 10

6 Software requirements 10

6.1 System (servers or virtual machines) 10

6.2 Workstations (end-user PCs) 12

6.3 Relativity Desktop Client 13

6.4 Licensing Microsoft products 13

7 Relativity compatibility matrix 13

7.1 Relativity system requirements matrix 13

7.2 Internet Explorer with Compatibility View 15

7.3 Chrome, Firefox, and Safari support 15

7.3.1 Browser support policy 15

7.4 Analytics release matrix 15

7.5 Invariant (worker manager server) release matrix 16

8 Processing system requirements 17

8.1 Processing worker hardware specifications 17


8.2 Tier hardware requirements 17

1 System requirementsThese system requirements contain detailed information about the software and hardware you useto host Relativity in your environment and in the cloud. These requirements also provide variousrecommendations for configuring a new deployment of Relativity, as well as scaling yourenvironment as the number of users and the amount of data continue to grow.

2 Infrastructure overviewRelativity is designed with a scalable infrastructure that you can tailor to the requirements of yourenvironment. It is developed on the .NET framework with a Microsoft SQL Server back-end. Asillustrated in the following diagram, all areas of the platform are scalable providing support for anyhardware vendor, hypervisor, and storage protocol.

Web Server


The Web Server is the gateway for all users to access Relativity. It authenticates the user with thesystem, contains APIs for searching and third-party applications, transfers documents to the enduser in the Relativity Viewer, and is responsible for communications during imports and exports inworkspaces. There are different methods of authentication into the system including forms, activedirectory, and RSA support. User sessions can be load balanced with the included Relativity UserLoad Balancer or via available hardware load balancing solutions.

Agent Server (Core)

Agents in Relativity are responsible for running all background processing tasks. When a usersubmits a job, such as a Production or OCR job, the associated agent(s) will pick up the job andcomplete the work. The agents run under a Windows Service and often require various levels ofCPU, RAM and I/O, depending on the job type. The agents can be scaled vertically and horizontallyto accommodate organizational needs.

Agent Server (dtSearch)

In Relativity 8 and above, the searches are multi-threaded and spawn as many threads as there aresub-indexes or cores — whichever number is lowest will be the constraint. One dtSearch searchagent may be able to utilize all available processor cores on a server. Therefore, each Relativityagent server that is designated to be a dtSearch search agent server should only have one dtSearchsearch agent and nothing else.

SQL Server (Workspaces)

This SQL server is where the structured text and metadata resides for the documents. EachRelativity workspace is represented by its own SQL Server database. Environments may have one ormore SQL Servers. In addition to workspace databases there are Relativity system databases presenton each server that contain tables for system configurations, agent job queues, user/groups, etc.

SQL Server (Invariant/worker manager server)

Relativity processing has individual store databases that correspond to each Relativity workspacedatabase with processing enabled. Total memory and processor requirements for this role are notas demanding as the SQL Servers that house workspace databases. This server is also used for nativeimaging and viewer conversion request management across various queue and configuration tables.One worker server should be dedicated to viewer conversion for every 100 concurrent users.

Worker

The ‘Worker’ role is responsible for handling enhanced native imaging, processing, and viewerconversion jobs. kCura has placed a hard cap on the amount of threads that each Worker server isallowed to spawn, the hard cap is 16 threads. Each processor core and 2GB RAM will create twothreads. Therefore, it is suggested that 8 logical cores and 16GB RAM be allocated to each workerserver to get the most throughput. One worker server should be dedicated to viewer conversion forevery 100 concurrent users.

Analytics


The analytics server is responsible for building and storing the conceptual indexes in theenvironment. Once an index is built, the server is also used to run the conceptual features such ascategorization and clustering. In addition to conceptual indexing, structured analytics sets are run onthis server for textual analysis features such as email threading or language identification. Theindexes and structured analytics sets are stored on disk in a configurable location.

File Server

This server may not be required depending on the available storage. kCura doesn't install anysoftware on a file server for Relativity. Relativity just needs to know where the Files(Natives/Images) live and the web servers need to be able to access those locations. The sameapplies to dtSearch, Analytics index, and viewer cache location(s).

3 ScalabilityYou can scale Relativity installations to handle the performance, storage, and other environmentalfactors necessary to support the addition of new users, continual growth of data, and increaseddemands for searching capabilities.

3.1 Tier level definitionskCura has identified tier levels that support varying numbers of users and sizes of active data. Youcan use these tier level definitions to determine the cores, RAM, and other equipment required tosupport the rapid growth of your Relativity installation. Key terms used in the following tableinclude:

n Enabled User Accounts – amount of enabled Relativity User accounts.n Simultaneous Users - average amount of simultaneous users logged into Relativity.n Active SQL Data (TB) - total amount of disk space consumed by SQL databases (mdf) and full text (ndf)

indexes.n Active Record Count (MM) – total amount of records (documents) included across all active Relativity

workspaces.n 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 - Entry LevelEnvironment

Tier 2 - Mid LevelEnvironment

Tier 3 - Large ScaleEnvironment

Enabled UserAccounts

< 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 - EntryLevelEnvironment

Tier 2 - MidLevelEnvironment

Tier 3 - Large Scale Environment

Total Cores for Non-SQL < 48 48 - 192 192+Total Memory (GB) for Non-SQL < 96 96 - 384 384+Total Cores for SQL Server < 16 16 - 96 96+Total Memory (GB) for SQL Server < 128 128 - 1024 1024+Total SQL Storage I/O (Gbps) 4 - 8 8+ SQL Server Fast Track (http://www.-

microsoft.com/fasttrack)SQL Tempdb Storage Separate

spindlesSSD or flash SSD or flash

Note: Microsoft SQL Server Fast Track combines preconfigured servers, storage, and networking with SQLServer 2012 R2 Enterprise for a scalable enterprise data warehouse platform. You can choose industry-standard hardware from Dell, HP, Cisco, IBM, EMC, and other leading vendors.

4 Recommended configurations for new deploymentsContact kCura Client Services for assistance with designing your Relativity infrastructure.

4.1 Tier 1 - Hardware requirements (25-50 named users)kCura supports the installation of all Relativity components on a single device for 25-50 named useragreements. We also require that a hypervisor is installed to this device so each Relativity role hasits own virtual machine.

Hardware Minimum RequirementsMemory 144GB RAMProcessor 40 logical cores (2GHz)Storage This server can be attached to a storage device (SAN, DAS, NAS). See Storage.

The following table provides virtual machine specifications for the single server setup.

Tier 1 (25-50 named users) - Single Server Deployment Quantity Memory (GB) CPUWeb 2 4 4Agent 2 4 4Analytics 1 32 4Worker 1 16 8SQL (Workspace Databases) 1 64 8SQL (Invariant/worker manager server) 1 16 4


4.2 Tier 1 - Hardware requirements (100 or more named users)While Relativity supports the use of virtual machines, differing configurations are recommendeddepending on the tier level of your environment. The number of SQL Servers is influenced by HighAvailability and Disaster Recovery requirements as described in Infrastructure configuration. Youcan distribute Relativity workspace databases across multiple SQL instances.

This table lists the recommendations for environments at Tier 1.

Tier 1 (100+ named users) - Entry Level Environment Quantity Memory (GB) CPUWeb 2 8 8Agent 3 4 4Analytics 1 32 4Worker (Processing, Imaging) 2 16 8Worker (Conversion) 1 16 8SQL (Workspace Databases) 1 64 8SQL (Invariant/worker manager server) 1 16 4

4.3 Tier 2 - Hardware requirements (300 or more named users)For Tier 2 environments, additional virtual machines are recommended as well as increased RAMand CPUs as illustrated in the following table. Additionally, it is suggested that SQL (WorkspaceDatabases) instances are not virtualized when supporting larger datasets.

Tier 2 (300+ named users) - Mid Level Environment Quantity Memory (GB) CPUWeb 4 8 8Agent 4 8 8Analytics 2 64 8Worker (Processing, Imaging) 4 16 8Worker (Conversion) 3 16 8SQL (Workspace Databases) 2 256 16SQL (Invariant/worker manager server) 1 32 4

Please take the following into consideration for any sized environment:

Note: For the File (Document) role, the type of storage system used will determine if you need to install theWindows operating system.

File (Docu-ment)

n Processor: 4 cores (2GHz)n Memory: 4GB RAMn Network: Gigabit Ethernetn Storage: See Storage.

SMTP (Noti-fication)

Relativity requires an active SMTP server on your network. It interfaces with this server to sendnotifications and monthly billing statistics. The hardware requirements for this role aremin-


imal. You can leverage an existing SMTP server in the network or merge this server with theagent server role.

4.4 StorageFor each type of data, the amount of recommended space depends on the number of recordsimported, as well as the type and length of the expected reviews. Each server or VM needs spacefor the OS, page file and less than 1GB for Relativity installation files. For the Relativity ProcessingSQL 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 putthrough a regiment of rigorous random and sequential read/write IO testing before installation ofRelativity is completed.

Recommended space by data type:

Data Type 25-50 NamedUsers

100+ NamedUsers

Disk I/O

SQL Databases 500 GB 750 GB HighThe databases can live across multiple storagevolumes and SQL instances.

SQL Full Text Indexes 150 GB 250 GB ModerateIndex size depends on the number of fieldsand records indexed.

SQL Database Logs 150 GB 250 GB HighRegular transaction log backups keep these val-ues small and provide point in time recovery.

SQL Tempdb 80 GB 80 GB HighkCura recommends eight 10GB Tempdb datafiles for new deployments. SSDs recom-mended.

SQL Backups 500 GB 1000 GB Low-HighkCura recommends having a backup strategy.This volume is not required. Larger data sizesmay require higher I/O throughput.

dtSearch Indexes 150 GB 250 GB ModerateThe dtSearch index share is typically stored inthe same location as the files.

Analytics Indexes 150 GB 250 GB HighThe Analytics index volume is mounted to theAnalytics virtual machine with speed and con-nectivity similar to that of SQL Server.


Data Type 25-50 NamedUsers

100+ NamedUsers

Disk I/O

Files (Natives/Images) 1500 GB 3000 GB Low-HighThe files may not require a Windows install-ation depending on the storage. Multiple Pro-cessing Workers online will require more filestorage I/O.

Viewer Cache 500GB 1000GB HighTemporarily store natives, images, pro-ductions, and other file types the viewer uses.It is recommended that the cache be stored ontier-one storage (SSDs) in environments withhundreds of concurrent users. Recommended1TB viewer cache space available for every 100concurrent users.

Worker (NativeImaging/Processing)

250 GB 250 GB HighThis is theWindows temp directory used bynative applications during imaging and pro-cessing. This temp location never exceeds250GB for each Worker server.

5 Infrastructure configurationRelativity supports the following technologies as part of its infrastructure configuration:

n VirtualizationWe suggest virtualizing all Relativity roles with the exception of SQL (workspace databases). Any hyper-visor is supported.

Note: Virtualizing SQL may simplify meeting HA and DR requirements. However, it can introduce additionallayers of complexity when properly configuring and troubleshooting performance and stability related issues.

The worker servers are CPU intensive and do not store any critical data, consider not virtualizing thisrole to possibly reduce licensing costs, assuming there is more than one worker server available.

We're not opposed to virtualizing SQL (native imaging/processing). This server demands less hardwareresources, and any performance issues would impact only these Relativity features.

n High Availability (HA)Relativity supports SQL Server Failover and File Server Clustering along with available hypervisor solu-tions.

n Disaster Recovery (DR)Relativity supports Microsoft SQL Server mirroring, log shipping, and SAN replication technologies.These approaches typically require manual failover and increased downtime.


n Web Server Load BalancingRelativity supports only single affinity in Windows Network Load Balancing (NLB). The Relativity UserLoad Balancer (RULB) provides the ability to distribute the user load evenly.

n 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 Relativity Community. Note that youmust have a valid Relativity Community username and password to download this content.

Note: To download this file, visit the Files & Libraries page on our Community site. Search for thename of the file, and then select the Files tab in the search results.

5.1 Guides for infrastructure managementReview the following guides to become familiar with best practices for managing the Relativityinfrastructure:

n Pre-Installation Guiden Environment Optimization Guiden Infrastructure Planning Recommendationsn Performance baselines and recommendations

6 Software requirementsRelativity has specific software requirements for servers or virtual machines, user workstations, andthe Relativity Desktop Client. The requirements for servers differ by the role assigned to them inyour system configuration.

Note: Make sure that you install the latest service packs for Windows, .NET, and SQL Server on yourmachines.

6.1 System (servers or virtual machines)The general software requirements for servers and virtual machines include Microsoft WindowsServer and .NET technologies. Microsoft Office and other applications are required for workermanager servers.

The following table provides software requirements by server role.

Server Role Software RequirementsWeb n Windows Server 2012 R2 orWindows Server 2008 R2

n .NET Version 4.5.1n .NET Version 3.5n IIS 7.5, 8.0, or 8.5

Agent n Windows Server 2012 R2 orWindows Server 2008 R2

https://community.relativity.com/s/files


Server Role Software Requirements

n .NET Version 4.5.1n .NET Version 3.5

Analytics n Windows Server 2012 R2 orWindows Server 2008 R2SQL n Windows Server 2012 R2 orWindows Server 2008 R2

n SQL Server 2014, SQL Server 2012, or SQL Server 2008 R2n .NET Version 4.5.1n .NET Version 3.5

Note: SQL Server 2014 support was introduced in Relativity9.1.172.5.

Fix for Microsoft KB3138319, KB 3151109 and KB3120595:

n Cumulative Update 11 for SQL Server 2012 SP 2n Cumulative Update 2 for SQL Server 2012 SP 2n Cumulative Update 5 for SQL Server 2014 SP1n Cumulative Update 13 for SQL Server 2014


Server Role Software RequirementsWorker n Windows Server 2012, Windows Server 2012 R2, or Win-

dows Server 2008 R2n .NET Version 3.5 (for Relativity 9.0)n .NET Version 4.5.1 (for Relativity 9.1)n Desktop Experience (Windows Server feature)n Microsoft Office 2010 Professional SP2 (32-bit) -

o This includes OneNote and Publisher, which arealso required applications.

o The Courier New and Arial UnicodeMS fonts mustbe installed on your machine. These fonts areinstalled by default when you install MicrosoftOffice, in which case you must ensure that youdon't remove them.

n Microsoft Visio 2010 Professional or Standard SP2 (32-bit)n Microsoft Project 2010 Professional or Standard SP2 (32-

bit)n Lotus Notes v8.5.2 with Fix Pack 4 or Lotus Notes v8.5.3

with Fix Pack 6n Adobe Reader - we don't require a specific versionn SolidWorks eDrawings Viewer 2015 (64-bit) with the

option to view 3D XML and PRO/E files.n JungUm Global Viewer v9.0 or higher

Note: Worker servers performing document conversion only (notprocessing or native imaging) only require Windows Server2012/2012 R2/2008 R2, .NET Version 3.5, .NET Version 4.5 (4.5.1 forRelativity 9.1), and Desktop Experience. However, if you plan onusing the Save as PDF feature in the viewer to convert natives only,note that this feature requires all of the pre-requisite software andthat it utilizes whichever server has been designated for documentconversion.

6.2 Workstations (end-user PCs)In Relativity, end users perform their reviews on workstations. Each workstation should beconfigured with a browser in which to use the Relativity web application, an operating system onwhich to run the Relativity Desktop Client, and the currently supported version of .NET.


Supported browsers for Relativity Web applicationSupported operating systemsfor Relativity Desktop Client

Supported.NET ver-sion

n Microsoft Internet Explorer 11.x (32-bit)n Microsoft Internet Explorer 10.x (32-bit)n Google Chrome 35+ (on both PC and Mac)n Apple Safari 6+ (Mac only)n Firefox 32+ (on both PC and Mac) - Only supported by

Relativity 9.0.237.3, released on December 24, 2014,and above.

n Windows 8 DesktopMode (PC)

n Windows 8 Pro DesktopMode (Surface Pro)

n Windows 7n Windows Vistan Windows Server 2012 R2

n 4.5

6.3 Relativity Desktop ClientThe Relativity Desktop Client (RDC) is a utility used for importing and exporting documents, images,natives, and productions. This utility requires the following software:

n Microsoft .NET 4.5 (Full Framework)n Microsoft Visual C++ 2005 SP1 Redistributable x86 or x64

Note: Visual C++ 2005 SP1 Redistributable x86 is supported on 32-bit and 64-bit OS, but x64 is supported on64-bit OS only.

For detailed installation instructions, see the Desktop Client Guide.

6.4 Licensing Microsoft productsRelativity requires Microsoft Windows and Microsoft SQL Server, both of which you need to licensethrough Microsoft or one of their resellers. If using Relativity Processing or Native Imaging, you alsoneed 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 throughMicrosoft’s SPLA (Service Provider License Agreement). You can find more information aboutMicrosoft’s SPLA program on Microsoft’s Hosting site.

kCura recommends contacting Microsoft, or one of their resellers, for guidance on the licensingoptions available.

7 Relativity compatibility matrix

7.1 Relativity system requirements matrixThe following table breaks down the supported operating systems, framework, IIS versions,browsers, and versions of SQL Server per Relativity version. For additional Chrome, Firefox, andSafari supported version details, see Chrome, Firefox, and Safari support on page 15.

http://www.microsoft.com/hosting/en/us/licensing/default.aspx


Software 8.1 8.2 9.0 9.1Operating systems - Relativity Desktop ClientWindows Server 2008 R2 (64-bit) ✓ ✓ ✓ ✓Windows Server 2012 R2 (64-bit) ✓ ✓ ✓Windows XP ✓ ✓Windows 7 ✓ ✓ ✓ ✓Windows 8 (Desktop Mode only) ✓ ✓ ✓ ✓Operating systems - serversWindows Server 2008 R2 (64-bit) ✓ ✓ ✓ ✓Windows Server 2012 ✓ ✓ ✓ ** ✓ **

Windows Server 2012 R2 ✓ ✓ ✓FrameworkMicrosoft .NET Version 3.5 w Service Pack 1 ✓ ✓ ✓ ✓Microsoft .NET Version 4.5 ✓ ✓ ✓ ✓Microsoft .NET Version 4.5.1 ✓ *** ✓ ***

IIS versionsIIS 7.5 ✓ ✓ ✓ ✓IIS 8.0 ✓ ✓ ✓ ✓IIS 8.5 ✓ ✓ ✓BrowsersIE 8 (32-bit) ✓ * ✓ *

IE 9 (32-bit) ✓ ✓IE 10 (32-bit) ✓ ✓ ✓ ✓IE 11 (32-bit) ✓ ✓ ✓ ✓Chrome ✓ ✓Firefox ✓ ✓Safari ✓ ✓SQL versionsSQL Server 2008 R2 (64-bit), Standard or Enterprise ✓ ✓ ✓ ✓SQL Server 2012 ✓ ✓ ✓ ✓SQL Server 2014 ✓ ****

* IE 8 doesn't support Collection, Inventory (in Processing) or the Workspace Security, AdminSecurity, and Item Security dialogs. However, IE 9, 10, and 11 support these features.

** We strongly recommend running Windows Server 2012 R2 over Windows Server 2012.

*** Web, agent, and SQL servers require .NET 4.5.1.


**** SQL Server 2014 support was introduced in Relativity 9.1.172.5.

7.2 Internet Explorer with Compatibility ViewRelativity doesn't support using Internet Explorer with Compatibility View enabled. DisableCompatibility View in Internet Explorer using the following steps:

1. Press the Alt key.2. Click Tools > Compatibility View settings.3. Remove your URL for Relativity from the list ofWebsites you've added to Compatibility View.4. Uncheck the checkbox labeled Display intranet sites in Compatibility View.5. Click Close.

7.3 Chrome, Firefox, and Safari supportWe recommend using the latest version of Chrome, Firefox, and Safari with Relativity. See Browsersupport policy below for additional browser compatibility details regarding Chrome, Firefox, andSafari.

The following table provides historical browser support information by Relativity release.

Browser 9.0 9.1Chrome 35+ 37+Firefox 30+ 33+Safari on Mac OS X 10.9 7.1+ 7.1+Safari on Mac OS X 10.10 8.0+ 8.0+

Note: Relativity supports Firefox in Relativity 9.0.237.3 and higher.

7.3.1 Browser support policyFor the Chrome, Firefox, and Safari web browsers, Relativity supports:

n Chrome and Firefox on Microsoft Windows and Mac OS Xn Safari on Mac OS Xn The threemost recent versions of Chrome and Firefox at the time of a given Relativity releasen The two most recent versions of Safari included with Mac OS X at the time of a given Relativity release

7.4 Analytics release matrixViewAnalytics release history for Relativity 9

The following table lists the version of CAAT released with each Relativity 9 release.

Relativity 9 release CAAT release Release date9.0.198.5 3.16.1 November 14, 2014


7.5 Invariant (worker manager server) release matrixView Invariant release history for Relativity 9

The following table lists the version of Invariant (worker manager server) released with eachRelativity 9 release.

Relativity 9 release Invariant release Release dateVersion 4.1.600.48 April 27, 20169.1.246.3 4.1.434.3 July 10, 20159.1.220.2 4.1.407.1 June 12, 20159.1.172.5 4.1.359.2 April 29, 20159.1.170.3 4.1.356.4 April 23, 20159.1.137.12 4.1.324.4 March 25, 20159.1.112.9 4.1.300.1 February 25, 20159.0.268.4 4.0.260.8 January 28, 20159.0.237.3 4.0.236.2 December 24, 20149.0.204.6 4.0.201.2 November 26, 20149.0.198.5 4.0.196.1 November 14, 2014


8 Processing system requirementsThe following information displays the system requirements for the Processing infrastructure.

8.1 Processing worker hardware specificationsThe following table displays the hardware specifications for Processing workers. These requirementsare determined by the number of workers needed to achieve a specified range of throughput (# ofGB/day).

Worker SpecificationsCPU 8 core (physical)RAM 16 GBNetwork 1 GbpsStorage Windows Temp SSD recommendedServer Physical recommended *Expected throughput 100-150 GB/day **

* The primary reason for using physical workers is for performance. The overhead fromvirtualization can cause degradation in performance, particularly during text extraction and otherCPU-intensive operations. If you do choose to virtualize your workers, beware of over-committingresources on the host. If you have hyper-threading enabled on the host, you may need to allocate 16vCPUs to each worker to achieve results similar to those in the See the Processing performancesection in the Performance Baselines and Recommendations guide.

** Processing source data and system load may impact performance. See the Processingperformance section in the Performance Metrics guide.

8.2 Tier hardware requirementsThe following table displays the supporting infrastructure per number of workers you want todeploy. Refer to an applicable tier to locate the necessary hardware components to complete yourprocessing infrastructure.

Tier 1Entry Level Environment

Tier 2Mid Level Environment

Tier 3Large Scale Environment

# of Workers 1 - 2 2-8 8+GB/day (source data) 100 - 300 300 - 1050 800+Invariant (workermanager server) SQLServer

n Processor: 4 coresn Memory: 16 GBn Storage I/O (Gbps): 4

n Processor: 4 - 8 coresn Memory: 32 GBn Storage I/O (Gbps): 4

- 8

n Processor: 4 - 8cores

n Memory: 64 GBn Storage I/O (Gbps):

4 - 8+


Tier 1Entry Level Environment

Tier 2Mid Level Environment

Tier 3Large Scale Environment

File Server n Commodity NASn 1+ Gbps network

n Dedicated NAS(write-back cacheavailable)

n 4+ Gbps network

n Enterprise classNAS (SSD tier avail-able)

n 10+ Gbps network

Note: By default, when you install Relativity, each worker in your environment is designated to do allavailable work (conversion, processing, and imaging). It's recommended that you change this designationso that, for every one hundred simultaneous users in your environment, you have one worker dedicatedto conversion only and another worker dedicated to processing and/or imaging (but not conversion).


Proprietary Rights

This documentation (“Documentation”) and the software to which it relates (“Software”) belongsto kCura LLC and/or kCura’s third party software vendors. kCura grants written license agreementswhich contain restrictions. All parties accessing the Documentation or Software must: respectproprietary 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 orSoftware in whole or in part. The Software and Documentation is protected by the Copyright Act of1976, as amended, and the Software code is protected by the Illinois Trade Secrets Act. Violationscan involve substantial civil liabilities, exemplary damages, and criminal penalties, including finesand possible imprisonment.

©2017. kCura LLC. All rights reserved. Relativity® and kCura® are registered trademarks of kCuraLLC.

Date post:	25-Aug-2020
Category:	Documents
Upload:	others
View:	4 times
Download:	1 times

Relativity - System Requirements - v9 · Relativity|SystemRequirements-4...

Documents