When a file is added to a vault, the file and all of its file properties (file size, date created, and so on) are added to the vault. If all the associated properties are defined in the vault, the property values are updated. If the property definition is new to the vault, the vault adds the property definition to the vault before storing the value. Depending on the type of files stored, each vault may have a different collection of properties that it maintains.
Re-indexing scans the selected vault database and extracts and indexes properties from the files in the vault database. The extraction and indexing process uses the latest available iFilters/Content Source Property Providers for the files. Only properties currently set to Enabled and properties that have read-mappings are re-indexed. During re-indexing, existing property (e.g., user-defined property) values are updated.
Reasons for re-indexing:
Which Properties Get Indexed
When files are added to a vault, any file properties that are defined as Enabled in the Properties Management dialog in Vault are indexed. The following are some of the property definitions that are automatically created and set to Enabled when Autodesk Data Management Server is installed:
Additional property definitions can be created by the administrator.
Indexing and Server Performance
The re-indexing process is assigned "Below Normal" priority on the server, allowing users to continue accessing the Autodesk Data Management Server even while files are being re-indexed. If the vault is backed up during the re-indexing process, the re-indexing is paused for the duration of the backup and then automatically restarted once the backup has finished. If a vault is being re-indexed and the same vault is restored, the re-indexing operation stops and all properties re-indexed to that point are replaced by the properties from the restored version.
When migrating a vault, all property definitions that are set to Enabled remain Enabled. Once migrated, the administrator can disable those property definitions which are no longer needed. Any new property definition added to the vault following migration is set to Enabled by default. Re-indexing processes files from newest to oldest. In the event that the server is suddenly re-booted or loses power, re-indexing automatically starts on the last file processed when the server is brought back on line.
When re-indexing properties in a replicated environment, the re-index operation processes files located on the server from which it was started.
Re-index File Properties in a Vault
All versions can be re-indexed as an option.
Clients can access the vault while it is being re-indexed. Not all properties may be up-to-date until the re-indexing has finished.
Filters
You can use filters to limit the number of files that are re-indexed. Following is a list filters that can be used to refine the re-indexing process:
Usage: Input file extensions with or without leading dots. Separate each extension by a comma or a semi-colon (with or without spaces).
Usage: Select provider(s) from the pre-defined list of providers.
Usage: Select the start and end dates to define the date range. The reindexing process will only index files that were checked in during this time frame.
Force Re-Index
Vault maintains re-index status for every file. So even though certain criteria are selected for a re-index operation, it is not necessary that all files that fall under the criteria be re-indexed because some files may be up-to-date thus not needing a re-index. However, the Administrator may choose to force a re-index on all files that meet the selected criteria by selecting the Force Re-Index option that can be exposed by expanding the dialog.
Force Re-Index is especially useful when a new iFilter is added, and also after migration. Apart from that there is really no need to run a Force Re-Index.
Once the re-indexing operation has been initiated for a vault, you can check the progress using the Re-Index File Properties Status dialog. The Re-Index File Properties Status dialog indicates which vault is being re-indexed, what percent of the files have been re-indexed, as well as the total number of files that have been re-indexed and the number of files remaining. The re-indexing can also be stopped using the status dialog.
The Re-Index Status dialog summarizes the files that failed to be re-indexed.
Check the Property Re-Indexing Status
Stop Re-Indexing
View Re-Indexing Details
Possible reasons for a file failing to re-index include:
If any files fail to re-index, either correct the corrupted file or make sure the iFilter for the specified file type is registered and then run the re-indexing operation again.