Answer
This article describes how to move a Firebird based Archive Store to another disk on the same server.
This may be required when you are running out of disk space on the partition where the database is currently stored. The procedure below may also be used to move either the Firebird database, the email binary source or the index to another disk on the same server to increase GFI Archiver performance by reducing the disk I/O (reads and writes) on the same disk.
Note that a Firebird Archive Store consists of 3 seperate parts:
- The Firebird database (this is a single FDB file and is stored by default in ..\GFI\Archiver\Databases\..
- The binary folder (is stored by default in ..\GFI\Archiver\Databases\..\binary\)
- The index folder (is stored by default in ..\GFI\Archiver\Indexes\..)
- Ensure that the new disk is initialized and partitioned correctly on the GFI Archiver Server
- Temporarily disable archiving of emails. This can be done from the the web page: Configuration > Mail Servers to Archive > Disable each entry
- Note: Wait for 5 to 10 minutes to ensure that all items within the GFI Archiver Queue are processed. It is recommended to check the following folders and ensure they are empty before proceeding:
- ..\GFI\Archiver\Core\Pickup
- ..\GFI\Archiver\Core\Queue
- ..\GFI\Archiver\MAIS\Pickup
- ..\GFI\Archiver\MAIS\Queue
- Note the location of the database(s) to be moved from the GFI Archiver Configuration > Archive Stores > Summary (take a screenshot)
- Stop all GFI Archiver services
- Copy the desired component (database, binary folder, index folder) to the new disk
- Start all GFI Archiver services
- Open GFI Archiver Configuration > Archive Stores
- Click on the Edit Settings icon to run the archive store wizard for the moved Archive Store
- During the wizard, ensure that you specify the new location of the Firebird database file (*.FDB), the binary folder and the index folder
- Re-enable archiving of emails from the GFI Archiver Configuration > Mail Servers to Archive > Enable each entry
- You can now safely remove the database from the previous location