By default, indexed searching is enabled on all existing and newly created volumes. You can disable or enable indexed searching on a per volume basis in the individual volume’s Volume Properties dialog in Access Connect Administrator see View the Volumes Window. You can set this property at initial volume creation time or after the volume has been created. In order for changes to this setting to take effect, you must stop and restart the Access Connect File Services for Macintosh service.
This cache is set to a maximum size of 20 MB by default. We do not recommend changing this cache size. An index file containing 250,000 files is only about 8 MB in size. Leaving the cache limit at the default setting gives sufficient performance in almost all cases. If the index files on disk are larger than search index cache size, the file will be read from disk when the client does a search; however in many cases the file will be in the Windows file system cache so performance impact is minimal. When the server is running with limited physical memory, the cache size can be reduced to as little as 8 MB.
By default on a standalone server, Access Connect stores index files in the Access Connect Indexes directory in the Access Connect application folder. If you would like to locate the index files in a different location, click Browse to select a new folder.
Note: If you modify the default path while Access Connect is running, all index files for volumes without individual custom paths are created in the new location.
Administrators can also specify custom index file paths for individual volumes; this setting overrides the global default path setting.
Note: In a clustered environment we recommend that you set the Default Path to be a location on the shared disk.
By default, indexed searching uses any available system resource to keep its indexes current and cooperates with other system processes. It should not affect overall system performance adversely. However, when a server is under high load or is running many different services simultaneously, you can limit the system resources that search indexing consumes by enabling the Use lazy indexing checkbox. This setting takes effect immediately.
In order to optimize runtime performance, the Access Connect index file entries for files that have been deleted or moved from a volume are not physically removed from the index file at the time the actual file is deleted. The indexed search service ignores these deleted entries to keep search results accurate. However, the index file grows over time and, as the file gets larger, slows search performance to a small extent. The rate at which the index file grows is dependent on the number of files being added, moved, and deleted on the file server. In order to keep Access Connect search performing at optimal levels, volumes’ indexes are routinely re-indexed and compacted. The interval at which this occurs is determined by the ratio of deleted (stale) records to valid entries in the index. By default, the Access Connect search service re-indexes an individual volume when approximately one-third of that volume’s index file records are deleted, stale records.
Maintenance occurs on a per volume basis and only on volumes requiring re-indexing. While re-indexing, the volume’s existing search index is kept up to date and used to provide one hundred percent accurate search results. Re-indexing should not have any detrimental effect on other server processes while it is running. While Access Connect is re-indexing an individual volume, a status of “Reindexing” shows in the Volumes dialog of the Access Connect Administrator. If you prefer, you can schedule re-indexing on a set schedule during off-hours. You can use an EZIPUTIL command, described on the Appendices page used in a batch file or script and triggered by a scheduling service of your choice. If you choose this method of scheduled re-indexing, disable automatic re-indexing by removing the check in the Automatic rebuild of sparse indexes setting checkbox.