Change Archive Location

 Only Global Admins or Restricted Admins with elevated View and Manage privileges can take this action.

Change the Archive Location

The LogRhythm Archives are stored by default in the C:\LogRhythm Archives\Active and C:\LogRhythmArchives\Inactive directories. The Archive paths can be modified in the Data Processor Advanced Properties.

1. On the main toolbar, click Deployment Manager.
2. Click the Data Processors tab.
3. Double-click the Data Processor you want to configure.
   The Data Processor Properties dialog box appears.

4. In the lower left corner of the dialog box, click Advanced.
   The Archive paths are set in the ActiveArchivePath and InactiveArchivePath fields.

   

   Note the following important points about setting the a valid path:

   • If you specify a non-local path, the Mediator (scmedsvr) service must be set to run as a user account with rights to access the specified path. The service account can be set using the service Properties in the Windows Services control panel.
   • When using an external path for inactive archives, the account under which the Mediator service is running must have delete permissions on that path. If the Mediator does not have delete permissions, you may see "path is not writable" errors in the Mediator log.
   • High Availability Network Area Storage (NAS) is required for writing inactive archives to remote UNC paths.

     Set the Value to any valid path (local or UNC). 
     If the directory that you specify does not exist, it is created automatically.

Best Practices for Entity Naming

Naming Structure

To prevent issues with archive paths and folder structures, it is considered a best practice to avoid special characters when creating names. Use only alphanumeric characters, hyphens (-), and underscores (_) in entity names. Do not use forward slashes (/), backslashes (\), or other special characters. Characters like forward slashes are interpreted as path separators by the system. Entity names with forward slashes (for example, "Department/Section") will create unexpected subdirectories. See the two examples below:

Good Entity Name Examples

The following entity names are examples of "good" entity names containing characters that can be used:

1. Department_Section
2. Region-East
3. Finance2025

Problematic Entity Name Examples

The following entity names are examples of "bad" entity names containing problematic characters/structure:

1. Department/Section
2. Region:East
3. Finance&2025