Select an archive store on the Archive Store screen and click Edit to manage its settings in this dialog. This screen is also used when you choose to create an archive store manually rather than using the automatic creation options on the Configuration screen.
Archive Store
Enable queries to this archive store
Check this box if you wish to allow this archive store to be searched using the tools located on the Search Archived Messages screen. When disabled, no search queries will return any results from the messages in this archive store. This option is enabled by default.
Archive new messages for the domain here
This option determines whether or not the archive store is the Active archive store for the domain, meaning it is the archive store to which newly archived messages will be added for that domain. Any domain can have multiple archive stores associated with it, but only one at a time can be active. For example, you may choose to create a new archive store for a domain when the current store reaches a certain size, but keep the old archive store available in the Archive Stores list so that it can be searched. This option determines which store receives newly archived messages. If there is an active archive store for a domain and you edit an inactive archive store and turn on this option, then it will become the active archive store and the other store will have this option disabled.
If you are using Automatic Archive Store Creation for a domain and you disable this option for the domain's active archive store, SecurityGateway will automatically create a new archive store for the domain when necessary. If you do not use the automatic archive store features and you disable a domain's active archive store then archiving for that domain will cease. |
Domain
This is the domain associated with the archive store. Only one domain can be linked to an archive store. This option can only be selected when manually creating a new archive store. For existing archive stores, the domain cannot be changed.
Name
Use this option to give a name to the archive for your own reference.
Database
Use a local Firebird database file
By default, SecurityGateway uses a local Firebird Database file for Archiving.
Connect to a Firebird database server instance
Choose this option if you wish to connect to an external Firebird database server for archiving. Select this option if you are using Clustering.
Use the same server as the SecurityGateway database
This is the default setting when you choose to "Connect to a Firebird database server instance". For Archiving, SecurityGateway will connect to the same Firebird Database Server that you have set up to handle the SecurityGateway database, and it will use the same credentials. The only additional information you will need to provide is the Database Path/Alias Name (see below) for the database file used for this archive store.
Connect to this Firebird database server instance
Select this option if you wish to connect to a different Firebird database server to manage the database. You will need to provide the Server name or IP, Port, User name, and Password required to connect to that server. You will also need to enter the Database Path/Alias Name for the database file used for the archive store.
Database Path/Alias Name:
Enter the path to the database file used for the archive store. Note: this path is relative to the Firebird Database Server, not necessarily a network path. For example, C:\Databases\SecurityGateway\Archive\Example.com\ARCHIVE.FBD. Alternatively, you can use an Alias Name here instead of a file path by editing the Aliases.conf file to create the alias for the database. Aliases.conf is located in the root folder of your Firebird Server installation.
Use different directories for database, message content, and search index
By default an Archive Store's data is contained in the folder specified in the "Directory" option below, with two subfolders: \data\ and \index\. Click this checkbox if you wish to customize the location of all three folders.
When you have selected the option above to "Connect to a Firebird database server instance", this option only governs where the message content and search index is stored. The database location is specified in the Database Path/Alias Name option above. |
Directory:
This folder contains the ARCHIVE.FBD Firebird database, which contains meta data (domain, user, date, etc.) related to archived messages. Archived data cannot be restored without this file. The folder also has the "..\data" and "..\index" subfolders for storing archived content and indexing respectively.
When you are using Clustering and have selected the option above to "Connect to a Firebird database server instance," this option only governs the location of the "..\data" and "..\index" subfolders, not the database file's location. The database location is specified in the Database Path/Alias Name option above. Further, the Directory specified here must be in a network accessible location, and you must use UNC file paths. For example: \\share01\databases\Archive\$Domain$\ |
The following locations are used when you have enabled the "Use different directories..." option above:
Database Directory:
This is the location of the archive's database file. NOTE: this option is not available if you have selected the option above to "Connect to a Firebird database server instance." In that case the database location is specified in the Database Path/Alias Name option above.
The default location of the Database Directory is: "..\SecurityGateway\Archive\$DOMAIN$\"
Content Directory:
This folder contains the archive.sgd file, which contains the archived data in a compressed format. Archived data cannot be restored without this file. By default this folder is called "..\data" and is a subfolder of the Database Directory.
NOTE: If you are using Clustering or have selected the option above to "Connect to a Firebird database server instance," this folder must be in a network accessible location and you must use UNC file paths (e.g. \\share01\databases\Archive\$Domain$\data).
Index Directory:
By default, the index directory is called "..\index" and is a subfolder of the database directory. The index directory contains the full text index generated by the CLucene Full Text Indexing engine. The full text index can be regenerated if it somehow becomes corrupt. The Full Text Index can be rebuilt for an Archive Store using the Maintenance option on the Archive Store screen.
NOTE: If you are using Clustering or have selected the option above to "Connect to a Firebird database server instance," this folder must be in a network accessible location and you must use UNC file paths (e.g. \\share01\databases\Archive\$Domain$\index).