

A resource pool is a set of servers and file repositories that you can associate with a workspace. Resource pools can be used to group resources based on litigation matter, location, or other categories. For example, you could create resource pools for the West Coast and East Coast to manage resources specific to these regions.
Use the following guidelines when associating resource pools with workspaces:
The following graphic depicts the connections between your resource pools, servers, Relativity environment, and workspaces. This is meant for reference purposes only.
(Click to expand)
To create a new resource pool:
After you create a resource pool, you should add the required servers and repositories to it. You can also edit the resources associated with an existing resource pool.
Use the following guidelines when configuring a resource pool:
Note: If you add a worker to one or more resource pools, it is unable to perform tasks for any other resource pool. If you don't add the worker to any resource pools, it can perform tasks that originate from any resource pool associated with the worker manager server.
Note: Every resource pool should have a worker manager server linked to it. If a resource pool does not have a worker manager server linked to it, any workspace linked to that resource pool is unable to perform imaging and processing.
To add servers to a resource pool:
Note: When you add a location to the Process Source Location object, that location is visible on the Processing application and on the processing set.
Note: You can also click Edit to update the properties of a server. See Servers for more information.
Note: You can't remove an SQL Server when a workspace associated with the resource pool is using it. Similarly, you can't remove an Analytics server when indexes are using it. See Resource pools.
You can remove an Analytics server from a resource pool only when no Analytics indexes are using it. When you want to remove a server, you can display a dependencies report that lists the indexes using it.
Note: If you delete all of the Analytics servers set up for structured data analytics, then users won't be able to run any structured data analytics jobs in the workspaces associated with the resource pool.
In order to make a processing source location available for selection on the data sources that you’ll add to a processing set, you need to add that location to the resource pool associated with the workspace in which you’re running processing.
Note: Depending on the case sensitivity of your network file system, the source location you add through the resource pool may be case sensitive and might have to match the actual source path exactly. For example, if the name of the file share folder is \\files\SambaShare\Samba, you must enter this exactly and not as “\\files\SambaShare\samba” or “\\files\sambashare\Samba”, or any other variation of the actual name. Doing so will result in a document-level processing error stating, “The system cannot find the file specified.”
To add a processing source location to a resource pool:
Note: A processing source location doesn’t have to be in the same location as Relativity, but the Relativity Service Account must have read access to that processing source location.
If you need to remove a source location from the resource pool because, for example, it’s no longer valid or applicable or because you’ve already published all of its data, you can select the location name on the resource pool and click Remove.
You can add or remove objects from client domains if you have the client domains feature activated.
Anyone with permissions to edit resource pools can add or remove them from a client domain.When you enable this for a client associated with a specific workspace, Relativity copies the resource pool for this workspace, and adds the copy to the resource pools used by the client. When you enable this feature for a client associated with a specific workspace, Relativity copies the resource pool if it isn't associated with the client for the workspace, and adds the copy to the resource pools used by the client.
Webservers added to resource pools can load balance and prioritize traffic on a client-by-client basis. You can monitor and manage spikes in resource pools across your environment by adding logging information for resource pool access and usage. Resource availability to Enterprise customers with client domains will vary according to subscription level.
Note: Migrating a workspace that contains published data to a resource pool associated with a different worker manager server results in the loss of all references to previously published data.
Use the following steps to add a resource pool to a client domain:
Use the following steps to remove a resource pool from a client domain:
Why was this not helpful?
Check one that applies.
Thank you for your feedback.
Want to tell us more?
Great!