Creating and running a Restore job

Complete the following fields:

• Archive Directory—select the filepath to the archive directory from the drop-down list. This drop-down list includes all the archives from the ARM folder and displays them as [Workspace Name] (Case ID - Date Archived).
  • When you select an archive to be restored, a new section with Archive Settings appears. You can verify which options were selected for creating that archive.
  • If your archive folder is not displayed, verify the following:
    • Archive folder was added to ARM folder in the Staging area.
    • Archive folder is not zipped.

    • ARM Staging location is added as Location on ARM Configuration page in case you are using the old ARM UI.

    • Archive folder is in ARM folder or one level down if you are using the new ARM UI.

    • Archive folder has archiveinformation.xml. ARM application opens folder under ARM folder first and looks for archiveinformation.xml file to display it as available in restore. If this file is missing or is nested under another folder, ARM does not recognize that archive as a valid archive.
• Client—select the client that the restored workspace will use, or enter a client name in the search box that appears. You can also enter a few letters from a client name, and the list will filter based on your input. This field help ensure client domains in the target Relativity environment are respected.
  • If a matching client is not detected but the selected archive has client information, ARM adds a new option to the list of available clients reflecting the archived client. This option is displayed on the page with (New) at the end to distinguish it from existing objects. Creating the Restore job also creates this client object.
  • If you choose a client from Client Domain, ARM restores the workspace to the dedicated Client Domain Resource Pool.
    
• Matter—select the matter that the restored workspace will use, or enter a matter name in the search box that appears. You can also enter a few letters from a matter name, and the list will filter based on your input. This field helps ensure client domains in the target Relativity environment are respected.
  • If a matching matter is not detected but the selected archive has matter information, ARM adds a new option to the list of available matters reflecting the archived matter. This option is displayed on the page with (New) at the end to distinguish it from existing objects. Creating the Restore job also creates this matter object.
• Existing Target Database—this field only appears when you are restoring an archive for which Include Database Backup option was not checked. ARM needs a database file in order to restore the workspace so you need to provide that file separately.
• Job Priority—select High, Medium, or Low priority for the job from the drop-down list.
• Execution Type—select from the following options:
  • Manual—run the job manually from the Job List page.
  • Scheduled—run the job automatically at a specified date and time. When you select this option, the Scheduled Start Time field appears. Update the date and time information. You can schedule multiple jobs to run at the same time. You do not need to click Run Job. The system runs it automatically. Clicking Run Job before the specified date and time instantly starts the job.

Complete the following fields:

• Files First workflow—select this checkbox if you copied Repository Files folder separately from your archive folder.
  
  • You can use this flow only for archives with excluded Repository Files and Processed Files (Discovered Files). If one of these options has been included in the archive, you cannot run this workflow.
  • The Files First workflow does not support cross-domain restores. It requires that archive files are staged in the same Staging Area as the restore target.
    • The Files First workflow works normally when both the archive files and the target workspace are within the same Client Domain Staging Area, or when both are in the primary Staging Area.
    • You cannot be use the Files First workflow if archive files have been uploaded to a Client Domain file share and the restore target is the primary Staging Area. ARM renames a folder rather than copies it, and Client Domain file shares reside in separate Azure storage containers, making cross-domain renames impossible.
    • Before starting a Files First restore, confirm that your archive files are in the same Staging Area as your restore target. If files have been uploaded to a Client Domain file share but your target is the primary Staging Area, move them using RelativityOne Staging Explorer before initiating the restore.
• Additional Files Directory—when ‘Files First workflow’ is selected, ARM scans ARM location for EDDS###### folder and selects it automatically. The '######' is artifact ID of the originally archived workspace. If you want to learn more about the Files First workflow, refer to this Community article.

Complete the following fields:

• Notify Job Runner—select to send notifications to the user who created the job and to the user who runs it. When the creator and the executor are the same user, only one notification is sent.
• Notify Additional Recipients—select to send notifications to one or more additional email addresses that you specify on the job. If you select this option, Additional Recipients field appears for entering email addresses.
• Additional Recipients—appears when Notify Additional Recipients option is selected.

For more details, go to Configuring notifications for an ARM job.

During the Archive process, ARM creates a database backup of the workspace. All groups that existed in the original workspace at the time of archive are captured along with their permissions. The mapping groups functionality enables you to review all archived groups and assign them—together with their permissions—to corresponding groups in the target environment or to newly created groups.

The Map Groups page displays two panels:

• Archived Groups—groups stored in the archive.
• System Groups—groups currently existing in the target Relativity environment.

You can search for groups using the search box and sort the list alphabetically using the A–Z / Z–A controls. If you need to create a new system group at this stage, you must do so through the Relativity Groups tab. For details, see Groups tab.

Automatic group mapping

By default, ARM uses automatic group mapping based on the following logic:

• During restore, ARM attempts to match archived groups to existing system groups by name.
• If no matching group exists, ARM automatically creates a new system group and uses it for the restore.
• If a naming conflict occurs, ARM creates a new group and appends a numeric suffix. For example, Level 1 (0).
• When an archived group is mapped to an existing system group, the workspace permissions of the system group are overwritten with the archived permissions during the restore.

Custom mapping

You can modify mappings by manually repositioning entries or selecting different groups in the System Groups list.

You may also:

• Click Auto Map to reapply the default mapping logic, or
• Click Clear All to remove all current mapping selections.

The interface displays the Archived Groups on the left mapped to corresponding System Groups on the right.

Restore behavior and mapping requirements

During the restore process:

• Workspace permissions from the archived group are applied to the mapped system group.
• At least one group must be mapped to allow access to the restored workspace due to Customer Lockbox.

If a group is not mapped or there are more archived groups than system groups, ARM automatically creates additional groups as needed and maps them accordingly. For example, a New Group may be created to map to an unmapped archived group.

Naming behavior for newly created groups

If a newly created group shares a name with an existing one, ARM appends a numeric suffix, for example, Level 1 (0), Level 1 (1), etc. This ensures all automatically created groups have unique names in the environment. Ensure that all group names are positioned correctly before proceeding. Click Save to continue to the next section, where you map users from the archive to users in the system.

Restoring to Client Domains (Tenancy‑Enabled Clients)

When you restore a workspace to a Client Domain—determined by the selected Client, a notification appears on the Map Groups page. It informs you that the tenant admin account associated with that client automatically gains access to the restored workspace.

The Map Users page displays:

• Archived Users—users stored in the archive.
• System Users—users present in the target workspace.

Considerations

Consider the following before mapping users in ARM:

• During a restore, ARM automatically maps archived users to existing system users using their email address.
• Users must already exist in the target environment to be available for mapping.
• If an archived user has no corresponding account, you must create or sync that account before running the restore. For details, see Users.
• Once created or synced, the user becomes available in the Users tab.
• You need to manually map any users not automatically matched before the restore can proceed.
• To speed up manual mapping, use the Auto Map button to have ARM suggest matches based on first and last name. Review the suggestions and make any changes necessary before proceeding.
• ARM does not create user accounts.
• User mapping is used only to preserve audit history and private saved searches.
• User mapping does not assign users to groups or grant workspace access. Group membership and workspace access must be managed outside of ARM, and can be assigned after the restore if needed.

Automatic user mapping

By default, ARM uses the following mapping logic:

• It first attempts to match users by email address.
• If no email match is found, ARM attempts to match based on first name + last name.
• It does not create user accounts; all required users must exist before restore.
• It does not grant access or modify group membership.
• Automatic mapping preserves audit history and private saved searches.

Automatically mapped users hidden from UI

Users whose email addresses match 1:1 between the archive and target environment are:

• automatically mapped,
• hidden from both mapping panels, and
• cannot be manually edited.

These mappings appear only in the Restore job summary after the job is created.

Custom user mapping

You may manually select alternative target users in the following way:

1. Click Clear All to reset the mapping selections.
2. Ensure all users are mapped correctly.
3. Click Save to proceed to the Restore Job Details page.