Overview

This article provides the guidelines to follow for storing the GFI Archiver database and indexes on a network share (UNC path).

Information

When creating a GFI Archiver archive store, some data can be stored on a network location, and certain data cannot. Please follow the guidelines below, which will differ depending on the database backend you have chosen:

Firebird Database

1. The Firebird database file (*.fdb file) must be stored on a local disk.
2. The binary files can be stored on either a network share (UNC path) or a local disk.
3. The index files can be stored on either a network share (UNC path) or a local disk.

Microsoft SQL Server Database with File Storage

1. The Microsoft SQL Server database files (*.mdf and *.ldf files), must be stored on a local disk of the Microsoft SQL Server.
2. The binary files can be stored on either a network share (UNC path) or a local disk.
3. The index files can be stored on either a network share (UNC path) or a local disk.

Microsoft SQL Server Database without File Storage

1. The Microsoft SQL Server database files (*.mdf and *.ldf files) must be stored on a local disk of the Microsoft SQL Server.
2. The index files can be stored on either a network share (UNC path) or a local disk.

Notes:

1. When you are specifying a network share, specify the UNC path, and avoid mapped drives.
2. Indexes must have been created or rebuilt by GFI MailArchiver 2011 or newer for them to be stored on a network share (UNC path).
3. Only GFI MailArchiver 2013 R2 or newer allows the specification of the username and password for indexes to be located on a network share (UNC path). Only one set of credentials (username and password) can be configured globally under Configuration > Archive Stores > Index Management to access the network share for indexes.