The following sections provide a comprehensive list of all possible data locations of relevant Relativity files (there may be other areas that relate to custom applications or ISV products). You should also consider these areas when creating a backup inventory.
Database files
A backup of a SQL 2012/2014/2016 database includes the Data file, the Log file, and any additional data files, such as the full-text index catalog. You should preserve and thoroughly document maintenance plans and other SQL configurations to help restore service after an outage. There are many configuration options available with the SQL backup command—understanding them is critical to properly maintaining backup continuity. Both Relativity workspace and processing databases should be backed up.
Relativity file repositories
Relativity file repositories are locations that Relativity “owns.” That is, Relativity creates and deletes files from these locations when requested. The locations of Relativity file repositories are stored as choices in the EDDS Database CodeArtifact table in MS SQL. You can find these locations by running the following query:
File stores
Natives and images loaded with pointers are treated differently. Relativity reads files from file store locations but never deletes the locations, even if the document is deleted from Relativity.
Locating all file store locations is complicated. File path locations are stored in the File table and must be parsed out from any Relativity file repository paths. If you need assistance identifying these locations, contact Relativity Support.
Analytics
The Analytics server contains critical information about some configurations and may also be the default location for Analytics indexes. Take care to ensure that this server can be completely restored.
Cache location
Cache location servers temporarily store natives, images, productions, and other file types the viewer uses. Backing up the cache location is optional but recommended as rebuilding the cache can take much time and planning.
Configurations
The following sections provide possible data locations for configuration information in Relativity.
Agents
Relativity retains agent configurations in the database. Backing up the EDDS database effectively preserves all agent configuration data.
Web
You can customize certain aspects of the Relativity web application. For this reason, you should back up the website files as needed. You can also customize certain configurations in IIS. IIS provides a way to export and save the IIS configuration.
Ancillary indexes (dtSearch, Analytics)
The configuration of the index specifies the locations of the dtSearch and Analytics indexes. Capture all folders and subfolders.
Full-text catalogs
The full-text catalog may reside within either the database .mdf file, a separate .ndf file, or a mixture of both. The distribution location of the full-text catalog may vary depending on the age of the instance as well as the original version of SQL.
