System Requirements
Version 8.0 | July 25, 2013
Table of Contents
1 System requirements 3
2 Scalable infrastructure example 3
3 Software requirements 3
3.1 System (servers or virtual machines) 4
3.2 Workstations (end-user PC) 5
3.3 Relativity Desktop Client 5
4 Hardware requirements (single server—25-50 named users) 6
5 Hardware requirements (multi server—100 or more named users) 6
6 Infrastructure configuration 7
6.1 Guides for infrastructure management 8
7 Scalability 8
7.1 Tier level definitions 8
8 Recommended configurations for new deployments 9
8.1 Virtual machines 9
8.2 SQL servers 10
8.3 Storage 10
9 Obtaining applications for native imaging and processing 11
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.
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 11.
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
Agent (Background Processes and dtSearch)
nWindows Server 2008 R2
n
.NET Version 3.5 with Service Pack 1
n
.NET Version 4.0 (Full Framework)
Analytics (Search)
nWindows Server 2008 R2
File (Document)
nNAS (NFS or CIFS), DAS, or SAN
SQL (Workspace Databases and Native Ima- ging/Processing)
n
Windows Server 2008 R2
n
.NET Version 3.5 with Service Pack 1
n
.NET Version 4.0 (Full Framework)
n
SQL Server 2008 R2 Standard or Enterprise
Web (Application)
nWindows Server 2008 R2
n
.NET Version 3.5 with Service Pack 1
n
.NET Version 4.0 (Full Framework)
n
IIS 7.5
n
IIS 6 Metabase Compatibility Worker (Native Imaging/Processing)
nWindows Server 2008 R2
n
.NET Version 3.5 with Service Pack 1
n
.NET Version 4.0 (Full Framework)
n
Desktop Experience (Windows Server feature)
n
Microsoft Office 2010 Professional (32-bit) - this includes OneNote and Publisher, which are also required applications
n
Microsoft Visio Professional or Standard 2010 (32-bit)
n
Microsoft Project Professional or Standard 2010 (32-bit)
n
Lotus Notes v8.0 or higher
n
Adobe Reader 4.0 or higher
n
SolidWorks eDrawings Viewer 2012 or 2013 (32-
bit) with the option to view 3D XML and PRO/E
Server Role Software Requirements files
n
JungUm Global Viewer v9.0 or higher
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 Versions
Browsers
nMicrosoft Internet Explorer 10.x (32-bit) (Sup-
ported by Relativity 7.5.630.50 and later)
n
Microsoft Internet Explorer 9.x (32-bit)
n
Microsoft Internet Explorer 8.x (32-bit)
Operating Systems
nWindows 8 Desktop Mode (PC)
n
Windows 8 Pro Desktop Mode (Surface)
n
Windows 7
n
Windows Vista
n
Windows XP
n
Windows Server 2008 R2
Note: Internet Explorer 10 is supported for Windows 8 and Windows 7. If you are using Internet Explorer 10, you must enable Compatibility View for Relativity. 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:
n
Microsoft .NET 4.0 (Full Framework)
n
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.4 Hardware requirements (single server—25-50 named users)
kCura supports the installation of all Relativity components on a single device for 25-50 named user agreements. We also recommend that a hypervisor is installed to this device so each Relativity role has its own virtual machine.
Hardware Minimum Requirements
Memory 128GB RAM
Processor 16 logical cores (2GHz)
Storage
nThis server can be attached to a storage device
(SAN, DAS, NAS).
n
See Storage on page 10.
5 Hardware requirements (multi server—100 or more named users)
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)
nProcessor: 4 cores (2GHz)
n
Memory: 4GB RAM
n
Network: Gigabit Ethernet
n
Storage: See Storage on page 10.
Agent (dtSearch)
nProcessor: 4 cores (2GHz)
n
Memory: 4GB RAM
n
Network: Gigabit Ethernet
n
Storage: See Storage on page 10.
Analytics (Search)
nProcessor: 4 cores (2GHz)
n
Memory: 32GB RAM
n
Network: Gigabit Ethernet
n
Storage: See Storage on page 10.
File (Document)
nProcessor: 4 cores (2GHz)
n
Memory: 4GB RAM
n
Network: Gigabit Ethernet
n
Storage: See Storage on page 10.
Server Role Minimum Hardware Requirements
SMTP (Notification) Relativity requires an active SMTP server on your net- work. It interfaces with this server to send noti- fications and monthly billing statistics. The hardware requirements for this role are minimal. You can lever- age an existing SMTP server in the network or merge this server with the agent server role.
SQL (Native Imaging/Processing)
nProcessor: 4 cores (2GHz)
n
Memory: 16GB RAM
n
Network: 4 Gbps to storage
n
Storage: See Storage on page 10.
SQL (Workspace Databases)
nProcessor: 8 cores (2GHz)
n
Memory: 64GB RAM
n
Network: 4 Gbps to storage
n
Storage: See Storage on page 10.
Web (Application)
nProcessor: 4 cores (2GHz)
n
Memory: 4GB RAM
n
Network: Gigabit Ethernet
n
Storage: See Storage on page 10.
Worker (Native Imaging/Processing)
nProcessor: 4 cores (2GHz)
n
Memory: 8GB RAM
n
Network: Gigabit Ethernet
n
Storage: See Storage on page 10.
6 Infrastructure configuration
Relativity supports the following technologies as part of its infrastructure configuration:
n
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.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 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.
n
Perimeter Networking (DMZ)
Relativity requires certain ports to remain open for proper server communication. See the Relativity Infrastructure Ports Diagram for details.
n
NIC Teaming and Multipath I/O
Relativity supports the aggregation of network or storage connections for performance and redund- ancy.
6.1 Guides for infrastructure management
Review the following guides to become familiar with best practices for managing the Relativity infrastructure:
n
Pre-Installation Guide
n
Environment Optimization Guide
n
Solutions for Very Large Workspaces
o
Infrastructure
o
Workflow
n
Infrastructure Planning Recommendations
n
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:
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 Level Environment
Tier 2 Mid-Level Environment
Tier 3 Large Scale Environment
Enabled User Accounts < 300 300 - 1000 1000+
Simultaneous Users < 100 100 - 500 500+
Tier 1 Entry Level Environment
Tier 2 Mid-Level Environment
Tier 3 Large Scale Environment
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 Entry Level Environment
Tier 2 Mid-Level Environment
Tier 3 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
(http://www.microsoft.com/fasttrac k)
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 industry- standard 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.
Tier 1
Entry Level Environment
Quantity RAM (GB) vCPU
Web 2 8 4
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
Mid-Level Environment
Quantity RAM (GB) vCPU
Web 4 8 4
Agent 4 8 8
Analytics 2 64 4
Worker 4 16 8
8.2 SQL servers
The number of SQL Servers is influenced by HA and DR requirements as described in Infrastructure configuration on page 7. You can distribute Relativity workspace databases across multiple SQL instances.
The recommendations for Tier 1 environments are listed in the following table.
Tier 1
Entry Level Environment
Quantity RAM (GB) CPU
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.
Tier 2
Mid-Level Environment
Quantity RAM (GB) CPU
SQL (Workspace Databases) 2 256 16
SQL (Native Imaging/Processing) 1 16 4
8.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, 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.
Data Type 25-50 Named
Users
100+ Named Users
Disk I/O Example RAID Type
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.
Data Type 25-50 Named Users
100+ Named Users
Disk I/O Example RAID Type
SQL Backups 500 GB 1000 GB Low 5 | 5+0 | 1+0
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 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 Imaging/Processing)
100 GB 250 GB High 1 | 1+0
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:
n
Microsoft Office Professional 2010 - this includes OneNote and Publisher, which are also required applic- ations.
n
Microsoft Visio Professional or Standard 2010
n
Microsoft Project Professional or Standard 2010
n
Note: For the Microsoft products listed above, the 32-bit version is required for installation. See
Software requirements on page 3.n
Lotus Notes v8.0 or higher http://www-01.ibm.com/software/lotus/products/notes/
Note: For Lotus Notes v8.0, Domino servers are not required. You can install Lotus Notes Express Edition with
the Notes Client component.n
Adobe Reader 4.0 or higher http://get.adobe.com/reader/otherversions/
n
SolidWorks eDrawings 2012 or 2013 (32-bit) (with the option to view 3D XML and PRO/E files) http://www.solidworks.com/sw/support/eDrawings/e2_downloadcheck.htm
n
