- Oh no! An error has occurred!
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
- You need to be logged in to do that.
-
Brian Schanen joined Autodesk in 2005 as a Product Designer and currently is a Customer Success Engineer for Autodesk’s Data Management products. Brian has taught at Autodesk University numerous times and has authored white papers on Vault and Productstream. He works with customers to implement a complete digital prototyping solution specializing in Autodesk Inventor, Autodesk Vault and Productstream. Brian lives near Detroit, Michigan.
-
When to perform a Re-Index Properties and Rebuild Search Indexes
August 14, 2008, 09:30 PM Brian SchanenRe-Index
The Re-Index command will scan an entire Vault – one at a time – to extract and index properties from the versions of files. After a re-index, the usage count in the Property Manager will be updated. It is only necessary to run the ‘Re-Index Properties…’ command if you make the following configuration changes:
- When adding a new property to ‘In Use’,
- When changing an existing property from ‘In Use’ to ‘Not in Use’
-
Add new iFilters to extract additional information from vaulted files.
To Re-index Properties in a vault you must first select the vault in the ADMS Console. The “Re-Index Properties…” command can then be found under the ‘Actions’ pull-down menu.
There are several options within this dialog box.
- Re-Index all files - all files for the specified vault are re-indexed
- Re-Index latest and released versions only - only the latest version, the released versions, and pending released versions are indexed
-
Calculate – returns the number of files that will be re-indexed based on the selection made above
By default this process will run as a “Below Normal” priority and will allow an administrator to re-index the server without loading the server. Additionally the re-indexing process runs without blocking access to the server and automatically pauses and continue for operations such as backup and server reboots. Although Clients can access the vault while it is being re-indexed, not all properties may be available until the re-indexing has finished.
To check on the progress of the re-indexing process, select the vault again in the ADMS Console then select the ‘Actions’ pull-down menu > Re-Index Properties… which will bring up the following Re-Index Properties Status dialog box.
It is possible to bump the process priority from “Below Normal” to “Normal” using the command line; in which case re-indexing will complete sooner; however, server performance will degrade due to the higher priority of the operation. Please refer to the ADMSConsole_2009 help for additional information: Chapter Server Console - ‘Command Line Server Console’, and Chapter Property Tuning - ‘Re-index Properties in a Vault’
Rebuild Search Indexes
For most properties in the vault, search indexing occurs automatically. When adding a new property to ‘In Use’, you will need to perform the ‘Re-Index Properties…’ and search indexing will occur automatically [without the need for the separate step of ‘Rebuild Search Indexes’]. One exception being if you change a User or Group Name [because this change can affect multiple vaults]. In that case, the user is messaged that they need to rebuilt the search index for the User or Group name change to be consumed.
NOTE: A ‘background’ process - Search Index Optimization (Index.Optimize) - updates Productstream’s and Vault’s indexing engine. This engine enables Productstream and Vault to return search results quickly. When the process is running the indexer is locked. This process runs during off hours to prevent user down time. This process should only take a couple of minutes at most, even in a really large environment. If this process does not run, the data management server would have to index on demand. This will cause slower performance for most users during peak times.Refer to the Vault Background Processes.pdf in the White Paper section, http://www.autodesk.com/vault-whitepapers to change the default time of the index optimization process.
Significant architectural changes were made by separating the search indexing from the main database in Vault/Productstream 2009. This change was made to provide enhanced capabilities in both flexibility and performance. This change impacts the administrator and end-user workflows in many ways. Tasks like search indexing used to be both automatic and immediate. Search indexing is still automatic but it is no longer immediate. After a file is added to the system it could be a couple of minutes before the file appears in a search. Hopefully this one time inconvenience is a fair trade for the performance gains.
Speical thanks to Pascal for the details in this post!
The Vault Knows All...
-Brian Schanen
You must be logged in to post a comment.