The RelativityOne Staging Explorer option enables you to rapidly transfer large amounts of data to jump-start and sustain the data pipeline for critical projects. Use this option to upload files to a staging area for RelativityOne or to download files from your RelativityOne storage location to a local computer.
The RelativityOne Staging Explorer uses Aspera to facilitate transfer speeds that can be ten times faster than a traditional FTP. Combined with proprietary software, all transfers are fast, secure, and defensible.
You can see data for a new matter, quickly load newly discovered data, or quickly download produced documents. This makes accessing data in the cloud as quick and as seamless as if it was contained within your own environment.
|12/6/2022||Added TLS to requirements table.|
|12/5/2022||Reorganized help topics to move them out of one help topic into multiple ones.|
|11/22/2022||Change .NET version to 4.7.2 from 4.6.2|
|11/9/2022||Removed "Performance considerations" section.|
|6/22/2022||Removed reference to cloud disk I/O in the "Avoid compressing datasets (with ZIP, 7z, etc.)..." bullet.|
|5/23/2022||Deleted "The maximum value is 300 Mbps." sentence from step 6 of the "Throttling setting" section.|
|3/15/2022||RelativityOne Staging Explorer will open to the last Staging fileshare you visited.|
|10/21/2021||Warning window displays indicating limited space to complete transfers.|
|8/17/2021||Connection status icon update.|
|7/23/2021||Automatic updating steps added.|
|6/21/2021||Updating RelativityOne Staging Explorer steps added.|
|3/16/2021||Datagram Size setting steps added.|
This page contains the following information:
Using the RelativityOne Staging Explorer
You set up a new case and need to begin review quickly. Opposing counsel gives you a hard disk drive with 10GB of files you need to add to RelativityOne. You decide to use the RelativityOne Staging Explorer to upload files from the hard disk drive to RelativityOne. After you finish review of the case, you need to create productions for opposing counsel. When you produce these files to your RelativityOne storage location, you use the RelativityOne Staging Explorer to download the production to your local drive. You then ship the productions to opposing counsel.
The following minimum system requirements are required to use the RelativityOne Staging Explorer.
||Windows 8.1 or above
|Windows Server operating system||Windows Server 2012 R2, Windows Server 2016, or Windows Server 2019|
|System memory||4 GB RAM|
|Software||.NET version 4.7.2|
|Transport Layer Security||TLS 1.2|
Recommended Internet Explorer settings
Ensure the Relativity instance is considered as a trusted site and the following settings are enabled in Internet Explorer on the machine running RelativityOne Staging Explorer.
- Open Internet Explorer.
- Go to Tools, and then select Internet Options.
- Click the Security tab.
- Set Custom Level > Downloads > File download > Enable
- Set Custom Level > Scripting > Active scripting > Enable
- Set Trusted Sites > Sites > add *.relativity.com
- Click the Privacy tab.
Set Cookies > First party Cookies > Allow
Set Cookies > Third party Cookies > Allow
Windows does not support multiple active connections on the same UDP port. Therefore, your firewall must allow a range of UDP ports to reach the Aspera server. Incoming client connections automatically increment to use the next available port in the range. Open these ports on any user machine that stages any data to RelativityOne. This includes ports on your network, as well as local machine firewalls.
To ensure that concurrent transfers can occur, you must make firewall changes to allow outbound connections to the server on the following ports:
- TCP port 443—required to be opened to the [customerinstance].relativity.one endpoint for login.
- TCP port 33001—required to connect the local machine to the Aspera server (asp-[region].relativity.one).
UDP ports 33001 - 33050—required to send and receive data from local machine to the Aspera server (asp-[region].relativity.one).
RelativityOne Staging Explorer does not support proxy servers.
Note: You can use the nslookup command in a Command Prompt to find the IP addresses associated with the endpoints listed above.
The opening of the required ports for the Windows firewall are typically handled on the end-user's machine. However, if you use any third party firewalls, you must manually open the ports referenced above. Improperly configured ports and/or a lack of UDP port ranges result in transfer failures.
For more information, contact Relativity Support.
You can test the TCP port connection by running the following commands in Windows Powershell:
- Test-NetConnection -ComputerName [FQDN] -Port 33001
Refer to RelativityOne network access in the RelativityOne technical overview for detailed information about all of the network considerations for data transfer in RelativityOne (including firewall privacy considerations and a list of FQDN).
The following minimum security permissions are required to use the RelativityOne Staging Explorer.
|Object security||Tab visibility||Admin operations|
- All permissions are set in
- The * indicates permissions needed for non-admin users only.
The ** indicates permission is not required to run RelativityOne Staging Explorer, but is required to send/receive an email notification when a transfer finishes or fails. For more information, see Transfer Email Notification Recipients.
- To view the fileshares, the user must be in a group, other than the System Administrator group, that is added to at least one workspace built on the Resource Pool with the associated fileshares.
The following are some good practices and limitations to consider when using RelativityOne Staging Explorer.
Use a stable internet connection. Wifi is not recommended.
Due to bandwidth sharing, avoid performing large and highly fragmented transfers in parallel.
Relativity does not store any information about file paths due to privacy concerns.
The following are some limitations to consider when using RelativityOne Staging Explorer:
- Only one Windows user can run an instance of RelativityOne Staging Explorer on a machine at a time.
By default, System Admins are able to view all files and folder.
- The Client Domain Admin group does not have RelativityOne Staging Explorer access by default, a System Admin needs to add the correct permissions.
- The Client Domain Admin group will only be able to view files and folders in fileshares that are linked to the resource pool associated with their own client domain, if:
- Given the correct permission.
- Instance setting StagingPaneOnlyPerClientDomain is set to TRUE.
Note: Set the Section to Relativity.DataTransfer.
- Only the same type of user can see mapped disks which have mapped them. For example, if a regular user mapped a disk a regular user needs to be logged into RelativityOne Staging Explorer to view them. And if an admin user mapped a disk an admin user needs to be logged into RelativityOne Staging Explorer to view them.
- RelativityOne Staging Explorer does not support transferring files with the .aspx extension, as this is an Aspera extension being used for temporary files.
- RelativityOne Staging Explorer does not support file paths longer than 470 characters.
- Both the Local and Staging panes display only 1000 items. When a directory consists of more than 1000 items the Top 1000 items displayed message appears in the bottom right corner of the Local or Staging panes. In such a case do not use CTRL+A to select all of the items, as only 1000 items will be selected. To select all the items within the folder, select the main folder instead of sub-folders or files within the main folder.
- The maximum number of active transfers for one instance of the RelativityOne Staging Explorer is 3.
- Enforced FIPS Policy may block some encryption algorithms which may cause errors in applications. We recommend using validated cryptographic algorithms approved by Windows Platform FIPS.
- Transfers from mounted disk images are not supported.
Aspera has a limit on byte size of the path:
- the whole path cannot be bigger than 515 bytes, and
- the file name cannot be bigger than 255 bytes.