

The steps below assist with Analytics index and structured analytics set moves, where the Analytics installation remains on its original server. These instructions differ depending on whether the Analytics server is using Single Data Directory mode.
Note: Please note that there can only be one index and structured analytics set location per Analytics server. Indexes and structured analytics sets must use the same location. Moving indexes requires downtime of all Analytics functionality in Relativity, such as clustering, categorization, index creation, etc. This doesn't impact any functionality in Relativity other than Analytics functions. For this reason, we recommend performing the move during off-hours.
Single Data Directory mode is only available on new Analytics installations; you can't enable it on upgrades. To determine whether or not the server is using Single Data Directory, take the following steps:
https://<servername.FQDN>:8443/nexus/r1/system/devices
If the server is in Single Data Directory mode, the device appears with a special name of single-data-directory and the file path.
Note: If you have a server on Non-single data directory mode, contactRelativity Support.
Note: You must copy all subfolders, even if they are empty. The Analytics software needs this folder structure in order to access the index or set. Be sure to copy all indexes and structured analytics sets to the same folder location.
To verify that the new directory is working properly, perform the following steps:
https://<servername.FQDN>:8443/nexus/r1/
If you need to migrate the Analytics server to a new server, use these instructions. For this procedure, you need to move the Analytics installation as well as the indexes and structured analytics sets.
Note: This requires downtime of all Analytics functionality in Relativity, such as clustering, categorization, index creation, etc. This doesn't impact any functionality in Relativity other than Analytics functions. For this reason, we recommend performing the move during off-hours.
You must copy all indexes from the old Analytics server to the new Analytics server. If the index directory is stored in another path, you will copy this directory to the desired location on the new server in Step 4 - Restoring the Analytics indexes.
Note: This causes an outage of all Analytics functionality on this server.
AnalyticsEngineIndexID
Note: Do not rename any of these folders.
You must migrate all structured analytics sets from the old Analytics server to the new Analytics server via the Analytics Backup/Restore script and the following instructions:
To install Analytics on the new server:
To restore your Analytics indexes on the new server:
After installation, restore the structured analytics sets from the old Analytics server to the new Analytics server via the Analytics Backup/Restore script and these instructions:
Analytics is now configured on the new server. You now need to add this server to Relativity.
To add the Analytics server to Relativity, use the following steps:
To verify that the new installation is working properly, follow these steps:
Now that Analytics is installed on the new server, perform the following steps:
Use these instructions for backing up or archiving Analytics data.
Copy all needed indexes from the Analytics server using these instructions:
Note: This causes an outage of all Analytics functionality on this server.
AnalyticsEngineIndexID
Note: Do not rename any of these folders.
To back up only select structured analytics sets, use these instructions:
cd C:\CAAT\bin
staging-backup 1016636_1111253 C:\migration\1016636_1111253backup
If you need to back up all structured analytics sets on the server, use the Analytics Backup/Restore script script, which sequentially backs up every structured analytics set.
Note: This script differs based on the directory mode that the server is using. If Single Data Directory is enabled, the structured analytics sets are commonly stored in C:\CAAT\.ufx\work. If the server is not on Single Data Directory, the structured analytics sets are commonly stored in C:\CAAT\device-links\caat\.ufx\caat. See Identifying the directory mode above.
This file is stored in the C:\CAAT\bin location. Depending on your folder structure, you may need to rename the CAAT portion to point to the bin folder correctly.
Note: To verify that the backup is running, navigate to the location of the backup folder. You should see staging area files being written to the backup folder specified in step 4 and the size of the files growing. If you run into any issues during backup, please contact Relativity Support.
Use these instructions for restoring Analytics data.
Restore the needed indexes to the Analytics server using these instructions:
Perform the following steps to restore a structured analytics set.
cd C:\CAAT\bin
staging-restore <new structured analytics set name> <path to backup file>
For example, to restore a structured analytics set called 1015041_1111253 from a backup file called 1015041_1111253backup in the Backups directory on the C: drive, the following statement would be used:
staging-restore 1015041_1111253 C:\Backups\1015041_1111253backup
http://localhost:8443/nexus/r1/staging/1015041_1111253
If you would like to restore all structured analytics sets to the server, use the Analytics Backup/Restore script, which sequentially restores every structured analytics set.
Note: This script differs based on the Directory mode that the server is using. If Single Data Directory is enabled, the structured analytics sets are commonly stored in C:\CAAT\.ufx\work. If the server is not on Singe Data Directory, the structured analytics sets are commonly stored in C:\CAAT\device-links\caat\.ufx\caat. See Identifying the directory mode above.
Note: To verify that the process is running, navigate to the location where your current structured analytics sets are stored. The sets are commonly restored to the C:\CAAT\.ufx\work location. Depending on your configuration, you may be able to restore the sets to a different location.
On this page
Why was this not helpful?
Check one that applies.
Thank you for your feedback.
Want to tell us more?
Great!