Storage locations

Storage locations in Evidence Local are represented by Universal Naming Convention (UNC) paths to network locations where evidence files are physically stored. These locations provide a scalable and distributed storage system that can be tailored to your organization's needs.

Storage locations are a powerful tool for distributing and organizing evidence files. Storage locations are incorporated into the association matrix as the physical location of files grouped into logical folders, helping automate evidence placement and retention policies.

Evidence Local automatically manages when to delete files from storage locations based on retention times set for their corresponding folders. If a new storage location is added, and folders are switched to that location, Evidence Local will migrate all data from the old location to the new one, ensuring data integrity through managed and verified transfers.

Evidence Local creates two default storage locations during installation:

  • Default storage location:
    • Used to store the initial Evidence Local archive.
    • UNC path: \\[Evidence Local Server]\videos\Archive\
  • Offline storage location:
    • Used to store files that are not recognized by Evidence Local, such as files with unlisted extensions or metadata issues.
    • UNC path: \\[Evidence Local Server]\videos\Offline\

For more information on supported file extensions, refer to File Extensions in Evidence Local.

Watch this video to learn how to add a storage location for evidence.

Add a location

  1. Sign in to your Evidence Local administrator account.
  2. Select Admin from the top menu.
  3. Under Storage Configuration, select Locations.
  4. Select Add Location.
  5. Enter a Name for the storage location.
  6. Select Add Path. The Location path details pane opens.
  7. Enter the Path in UNC Format, including the trailing slash.
  8. Enter the Min. Free Space (MB).
  9. Select Add. The storage location is created and appears in the list of storage locations. The Parser and Application services need access to the specified UNC paths. The user(s) assigned to the Application Service and Parser Service must have both local administrator rights and read/write access to those UNC paths.